[NO/URSA-CORE] Appointments

Object Description

One record per non-deleted appointment record.

Metadata

• Table Name: ursa.no_ursa_core_enc_003
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Appointment ID
• Event Date: Appointment Created Date
• Primary Key: Appointment ID

Published Fields

• Data Model Keys

  • Appointment ID -- The internal database identifier (used, e.g., for joins and primary keys) for the appointment. (See also [URSA-CORE] Appointment)
  • 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)
  • Service Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service provider. (See also [URSA-CORE] Service Provider)
  • Provider Group Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the provider group. (See also [URSA-CORE] Provider Group)
  • Facility Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the facility provider. (See also [URSA-CORE] Facility Provider)
  • Referring Provider ID
  • Location ID -- The internal database identifier (used, e.g., for joins and primary keys) for the location. (See also [URSA-CORE] Location)
  • 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)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Appointment 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)
  • Source Local Service Provider ID -- The internal database identifier for the service provider in the source data system this record originated from. (See also [URSA-CORE] Service Provider)
  • Source Local Provider Group Provider ID
  • Source Local Facility Provider ID -- The internal database identifier for the facility provider in the source data system this record originated from. (See also [URSA-CORE] Facility Provider)
  • Source Local Referring Provider ID

• Operations Support Fields

  • Appointment Operational ID

• Date Fields

  • Appointment Created Date -- The date the appointment record was created. (See also [URSA-CORE] Appointment)
  • Encounter Scheduled Start Date
  • Encounter Scheduled Start Datetime
  • Encounter Scheduled End Date
  • Encounter Scheduled End Datetime
  • Encounter Scheduled Duration Minutes

• Encounter Fields

  • Encounter Type Description
  • Encounter Type Operational ID
  • Is Encounter Type Clinician Office Visit
  • Is Encounter Type Hospital Inpatient Admission
  • Is Encounter Type SNF Admission
  • Is Encounter Type Home Health Care Visit
  • Is Encounter Type Telehealth Encounter
  • Is Encounter Type ASC Encounter
  • Is Encounter Type Dialysis Facility Encounter
  • Is Encounter Type Other
  • Appointment Status Description
  • Appointment Status Operational ID
  • Is Appointment Status Confirmed
  • Is Appointment Status Cancelled
  • Is Appointment Status Patient Arrived
  • Is Appointment Status Patient No Show
  • Reason Description

• Provider Fields

  • Service Provider NPI
  • Service Provider Description
  • Service Provider Specialty Description
  • Service Provider Specialty Operational ID
  • Provider Group NPI
  • Provider Group Description

• Metadata Fields

  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • Is Record Deleted -- Indicator for whether the current record should be considered deleted; useful for certain incremental data loading scenarios.
  • 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

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• service_prov_id → ursa.no_ursa_core_prov_001.prov_id
• prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
• facility_prov_id → ursa.no_ursa_core_prov_001.prov_id
• referring_prov_id → ursa.no_ursa_core_prov_001.prov_id
• location_id → ursa.no_ursa_core_struct_010.location_id
• resulting_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

Dedicated Precursors

• [NO/URSA-CORE] Appointments, Precursor 1 (All Source Records): One record per appointment from all sources