[NO/URSA-CORE] EMR Encounters

Object Description

One record per EMR encounter from a clinical (non-claims) data source; includes lookups.

Metadata

• Table Name: ursa.no_ursa_core_enc_001
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: EMR Encounter ID
• Event Date: Encounter Start Date
• Primary Key: EMR Encounter ID

Published Fields

• Data Model Keys

  • EMR Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the EMR encounter. (See also [URSA-CORE] EMR Encounter)
  • Parent EMR Encounter ID -- The database identifier for the EMR Encounter during or within which the event associated with the current record occurred.
  • 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)
  • Attending Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the attending provider. (See also [URSA-CORE] Attending 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
  • Admitting Provider ID
  • Discharging Provider ID
  • Location ID -- The internal database identifier (used, e.g., for joins and primary keys) for the location. (See also [URSA-CORE] Location)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local EMR Encounter ID
  • Source Local Encounter Type 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

  • Encounter Operational ID
  • Encounter Type Operational ID

• Date Fields

  • Encounter Start Date
  • Encounter End Date
  • Encounter Start Datetime
  • Encounter End Datetime

• Encounter Fields

  • Encounter Type Description
  • Is Encounter Type Clinician Office Visit
  • Is Encounter Type ED Visit
  • Is Encounter Type Hospital Observation Encounter
  • 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
  • Setting Description
  • Is Outpatient Setting
  • Is Urgent Care Setting
  • Is ED Setting
  • Is Hospital Observation Setting
  • Is Inpatient Setting
  • Is Acute Care Inpatient Setting
  • Is SNF Setting
  • Is Residential Facility Setting
  • Is Home Setting
  • CMS Place of Service Code -- The standard CMS 2-digit Place of Service code; e.g., 01 = Pharmacy, 02 = Telehealth, etc.
  • CMS Place of Service Description -- The natural language description of a standard CMS Place of Service code (See also [URSA-CORE] CMS Place of Service Code)
  • CMS Admission Type Code -- The standard CMS 1-digit Admission Type code; 1 = Emergency, 2 = Urgent, etc.
  • CMS Admission Type Description -- The natural language description of a CMS Admission Type code (See also [URSA-CORE] CMS Admission Type Code)
  • CMS Admit Source Code -- The standard 1-character CMS Admit Source code; e.g., 1 = Physician Referral, 2 = Clinic Referral, etc.
  • CMS Admit Source Description -- The natural language description of a standard CMS Admit Source code. (See also [URSA-CORE] CMS Admit Source Code)
  • CMS Patient Discharge Status Code -- The standard 2-digit CMS Patient Discharge Status code; 01 = Discharged to Home or Self Care, etc. Patient Discharge Status codes should include leading zeros.
  • CMS Patient Discharge Status Description -- The natural language description of a standard CMS Patient Discharge Status code. (See also [URSA-CORE] CMS Patient Discharge Status Code)
  • Reason Description

• Provider Fields

  • Service Provider NPI
  • Service Provider Description
  • Attending Provider NPI
  • Attending Provider Description
  • Provider Group NPI
  • Provider Group Description
  • Facility Provider NPI
  • Facility Provider Description
  • Referring Provider NPI
  • Referring Provider Description
  • Admitting Provider NPI
  • Admitting Provider Description
  • Discharging Provider NPI
  • Discharging Provider 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)

Terms

• EMR Encounter: An encounter as represented in an EMR or equivalent clinical or administrative system acting as a data source. (We make a distinction between an "encounter" and an "EMR encounter" because the definition of an encounter in an EMR might not match that used in the data model.)

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• service_prov_id → ursa.no_ursa_core_prov_001.prov_id
• attending_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
• admitting_prov_id → ursa.no_ursa_core_prov_001.prov_id
• discharging_prov_id → ursa.no_ursa_core_prov_001.prov_id
• location_id → ursa.no_ursa_core_struct_010.location_id

Dedicated Precursors

• [NO/URSA-CORE] EMR Encounters, Precursor 1 (All Source Records): One record per EMR encounter from a clinical data source; not based on claims data