[NO/URSA-CORE] Appointment Slots

Object Description

One record per period of time that is, was, or has some future potential to be available for booking an appointment for an encounter. Multiple appointment slots can be assigned to a single appointment; but the converse is not true (i.e., a single appointment slot cannot be associated with multiple appointments).

Metadata

• Table Name: ursa.no_ursa_core_enc_004
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Interval
• Case ID: Appointment Slot ID
• Interval Start Date: Slot Start Datetime
• Interval End Date: Slot End Datetime
• Primary Key: Appointment Slot ID

Published Fields

• Data Model Keys

  • Appointment Slot ID -- The internal database identifier (used, e.g., for joins and primary keys) for the appointment slot. (See also [URSA-CORE] Appointment Slot)
  • Location ID -- The internal database identifier (used, e.g., for joins and primary keys) for the location. (See also [URSA-CORE] Location)
  • Slot Service Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the slot service provider. (See also [URSA-CORE] Slot Service Provider)
  • Slot Provider Group Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the slot provider group. (See also [URSA-CORE] Slot Provider Group)
  • Patient ID -- The internal database identifier (used, e.g., for joins and primary keys) for the patient. This value is typically mastered, i.e., all records for the same patient, regardless of the source data system from which that record originated, should have the same Patient ID value. (Note that while the mastered Patient ID value might resemble a local identifier used in one of the upstream data sources, this does not indicate any special priority of that source system in determining the characteristics of the patient.) (See also [URSA-CORE] Patient)
  • Appointment ID -- The internal database identifier (used, e.g., for joins and primary keys) for the appointment. (See also [URSA-CORE] Appointment)
  • Resulting EMR Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the EMR encounter that ultimately occurred associated with the referenced appointment, referral, or other scheduling event. (See also [URSA-CORE] EMR Encounter)
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Appointment Slot ID
  • Source Local Slot Service Provider ID
  • Source Local Slot Provider Group Provider ID
  • Source Local Patient ID -- The internal database identifier for the patient in the source data system this record originated from. (See also [URSA-CORE] Patient)

• Operations Support Fields

  • Slot Provider Type Description -- The natural language description of the slot provider type. (See also [URSA-CORE] Slot Provider Type)
  • Slot Provider Type Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the slot provider type. (See also [URSA-CORE] Slot Provider Type)
  • Slot Service Type Description -- The natural language description of the slot service type. (See also [URSA-CORE] Slot Service Type)
  • Slot Service Type Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the slot service type. (See also [URSA-CORE] Slot Service Type)
  • Slot Availability Status Description -- The natural language description of the slot availability status. (See also [URSA-CORE] Slot Availability Status)
  • Slot Availability Status Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the slot availability status. (See also [URSA-CORE] Slot Availability Status)
  • Is Slot Availability Status Open -- Indicates a Slot Availability Status of Open, meaning the time is available to be booked for an appointment. (See also [URSA-CORE] Slot Availability Status)
  • Is Slot Availability Status Booked -- Indicates a Slot Availability Status of Booked, meaning the time has been booked for an appointment (and is therefore no longer available). (See also [URSA-CORE] Slot Availability Status)
  • Is Slot Availability Status Closed -- Indicates a Slot Availability Status of Closed, meaning the time is unavailable for reasons other than being already booked for an appointment. (See also [URSA-CORE] Slot Availability Status)

• Date Fields

  • Slot Start Datetime -- The date and time that the referenced appointment slot starts. (See also [URSA-CORE] Appointment Slot)
  • Slot End Datetime -- The date and time that the referenced appointment slot end. (Appointment slots are considered intervals, and so the end datetime is considered exclusive.) (See also [URSA-CORE] Appointment Slot)
  • Appointment Created Date -- The date the appointment record was created. (See also [URSA-CORE] Appointment)

• Metadata Fields

  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • Record Created Datetime -- The date and time that the current record was created in the original data source.
  • Record Last Updated Datetime -- The date and time the current record was last updated in the original data source.
  • Source Data Effective Datetime -- The "as of" date and time of the original source data system at the moment the current record was extracted. For example, if a snapshot of the data in a production system is taken at 12:05 AM on the first of each month and used to generate a package of flat files that are eventually loaded into the Ursa Studio client database later that month, the Source Data Effective Datetime of all records in that month's package will be 12:05 AM on the first. Not to be confused with Record Last Updated Datetime. (See also [URSA-CORE] Record Last Updated Datetime)

Foreign Keys

• location_id → ursa.no_ursa_core_struct_010.location_id
• slot_service_prov_id → ursa.no_ursa_core_prov_001.prov_id
• slot_prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
• pat_id → ursa.no_ursa_core_pat_001.pat_id
• appointment_id → ursa.no_ursa_core_enc_003.appointment_id
• appointment_service_prov_id → ursa.no_ursa_core_prov_001.prov_id
• appointment_prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
• resulting_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

Dedicated Precursors

• [NO/URSA-CORE] Appointment Slots, Precursor 1 (All Source Records): One record per source system record for a time slot that is or was at some prior point available for booking an appointment for an encounter.