[NO/URSA-CORE] Health Systems
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[NO/URSA-CORE] Health Systems
- Updated on 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback!
Object Description
One record per health system.
Metadata
- Table Name: ursa.no_ursa_core_struct_002
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Entity
- Case ID: Health System ID
- Primary Key: Health System ID
Published Fields
Data Model Keys
- 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 Health System ID
Operations Support Fields
- Health System Operational ID
Provider Fields
- Health System Description
Metadata Fields
- 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] Health Systems, Precursor 1 (All Source Records): One record per health system
Was this article helpful?