[NO/URSA-CORE] Services

Object Description

One record per service.

Metadata

• Table Name: ursa.no_ursa_core_proc_003
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Entity
• Case ID: Service ID
• Primary Key: Service ID

Published Fields

• Data Model Keys

  • Service ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service. (See also [URSA-CORE] Service)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Service ID

• Clinical Services Fields

  • 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)
  • LOINC Code
  • Service Type Description
  • Service Type Operational ID
  • Is Service Type Anesthesia
  • Is Service Type Chiropractic and Physical Therapy
  • Is Service Type DME
  • Is Service Type Evaluation and Management
  • Is Service Type General Facility-Based Care
  • Is Service Type Imaging
  • Is Service Type Labs and Other Tests
  • Is Service Type Medication
  • Is Service Type Non-Surgical Procedures
  • Is Service Type Surgical Procedures
  • Is Service Type Transport
  • Is Service Type Other

• Medication Fields

  • 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.

• 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)

Dedicated Precursors

• [NO/URSA-CORE] Services, Precursor 1 (All Source Records): One record per service