[NO/URSA-CORE] Locations

Object Description

One record per location.

Metadata

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

Published Fields

• Data Model Keys

  • Location ID -- The internal database identifier (used, e.g., for joins and primary keys) for the location. (See also [URSA-CORE] Location)
  • Parent Location ID
  • Affiliated Provider ID
  • Health System ID -- The internal database identifier (used, e.g., for joins and primary keys) for the health system. (See also [URSA-CORE] Health System)
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Location ID

• Operations Support Fields

  • Location Operational ID
  • Is Active Location -- Indicates the location is in active use as of the current source data effective date. (See also [URSA-CORE] Location)

• Location Fields

  • Location Description
  • Setting Description
  • Is Hospital Inpatient Setting
  • Is Hospital Outpatient Setting
  • Is Emergency Department Setting
  • Is Observation Setting
  • Is Clinic Setting
  • Is Urgent Care Setting
  • Is SNF Setting
  • Is Home Setting
  • Is Ambulatory Surgical Center Setting
  • Is Long-Term Residential Setting
  • Is Dialysis Facility Setting
  • Is Hospice 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)
  • Location Address Line 1
  • Location Address Line 2
  • Location City
  • Location State Abbreviation
  • Location ZIP Code 5-Digit
  • Location Latitude
  • Location Longitude

• 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

• affiliated_prov_id → ursa.no_ursa_core_prov_001.prov_id
• health_system_id → ursa.no_ursa_core_struct_002.health_system_id

Dedicated Precursors

• [NO/URSA-CORE] Locations, Precursor 1 (All Source Records): One record per service location; locations may be nested within larger locations