[NO/URSA-CORE] EMR Encounter Service Line Items

Object Description

One record per instance of a service rendered to a patient during an EMR encounter.

Metadata

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

Published Fields

• Data Model Keys

  • EMR Encounter Service Line Item ID -- The identifier for the instance of a performed service during an EMR Encounter.
  • 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)
  • Service Line Number -- The integer-valued ordinal representing the position of a service line item in a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
  • Service ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service. (See also [URSA-CORE] Service)
  • 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)
  • Service Location ID
  • 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 Service Line Item 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)

• Date Fields

  • Service Start Date
  • Service End Date
  • Service Start Datetime
  • Service End Datetime

• Provider Fields

  • Service Provider Description
  • Service Provider NPI

• Clinical Services Fields

  • Service Type Description
  • Service Type Operational ID
  • Service Description
  • Service Operational ID
  • HCPCS Code -- The Healthcare Common Procedure Coding System (HCPCS) code associated with a service. Includes both HCPCS Level I codes (commonly called CPT codes) and Level II codes (which includes products, supplies, and services not included in CPT). Level II codes consist of a letter followed by four numeric digits. Current Dental Terminology codes are included in the Level II codes as HCDT. (See also [URSA-CORE] HCPCS Description)
  • HCPCS Description
  • HCPCS Modifier 1 Code -- The 2-character code modifying a HCPCS code.
  • HCPCS Modifier 1 Description -- The natural language description of a HCPCS code modifier. (See also [URSA-CORE] HCPCS Modifier Code)
  • HCPCS Modifier 2 Code
  • HCPCS Modifier 2 Description
  • HCPCS Modifier 3 Code
  • HCPCS Modifier 3 Description
  • HCPCS Modifier 4 Code
  • HCPCS Modifier 4 Description
  • HCPCS Modifier 5 Code
  • HCPCS Modifier 5 Description
  • CMS Revenue Center Code -- The standard CMS 4-digit Revenue Center code; e.g., 0001 = Total charge, etc. CMS Revenue Center codes should include leading zeros.
  • CMS Revenue Center Description
  • HIPPS Code -- The standard CMS 5-digit Health Insurance Prospective Payment System (HIPPS) code; e.g., AAA00 = Default Code.
  • HIPPS Description -- The natural language description of a HIPPS code. (See also [URSA-CORE] HIPPS Code)
  • SNOMED CT Code -- The standard Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) code for the referenced concept; e.g., 284196006 = burn of skin. SNOMED CT codes can be used to identify conditions, medications, services, labs, and other clinical concepts.
  • SNOMED CT Description
  • LOINC Code
  • LOINC Description
  • ICD-9-CM Procedure Code
  • ICD-9-CM Procedure Description
  • ICD-10-PCS Code
  • ICD-10-PCS Description
  • Service Unit Count -- The number of units of a service delivered to the patient; includes non-integer values, if appropriate.

• Metadata Fields

  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • 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

• service_id → ursa.no_ursa_core_proc_003.service_id
• pat_id → ursa.no_ursa_core_pat_001.pat_id
• service_prov_id → ursa.no_ursa_core_prov_001.prov_id
• emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

Dedicated Precursors

• [NO/URSA-CORE] EMR Encounter Service Line Items, Precursor 1 (All Source Records): One record per instance of a service rendered to a patient during an EMR encounter