[NO/URSA-CORE] Program Entities
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[NO/URSA-CORE] Program Entities
- 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 program entity.
Metadata
- Table Name: ursa.no_ursa_core_struct_003
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Entity
- Case ID: Program Entity ID
- Primary Key: Program Entity ID
Published Fields
Data Model Keys
- Program Entity ID -- A collection of individuals or organizations, particularly providers, participating as a single entity in a program of some sort (e.g., an accountable care organization).
- Program Entity Provider ID -- The provider ID for the program entity, if the program entity is itself a provider. (See also [URSA-CORE] Program Entity, [URSA-CORE] Provider ID)
- Affiliated Health System ID -- The health system ID for the parent health system the reference entity is affiliated with. (See also [URSA-CORE] Health System ID)
- Source ID -- The identifier for the original source data system from which the current record originated.
Source Local Keys
- Source Local Program Entity ID
- Source Local Program Entity Provider ID
Operations Support Fields
- Program Entity Operational ID
- Program Operational ID
Date Fields
- Entity Participation Start Date -- The date the program entity started participating in the program. (See also [URSA-CORE] Program Entity)
- Entity Participation End Date -- The date the program entity stopped participating in the program. (Uses the interval convention for end dates.) (See also [URSA-CORE] Program Entity)
Provider Fields
- Program Entity Description
- Program 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)
Foreign Keys
- program_entity_prov_id → ursa.no_ursa_core_prov_001.prov_id
- affiliated_health_system_id → ursa.no_ursa_core_struct_002.health_system_id
Dedicated Precursors
- **[NO/URSA-CORE] Program Entities, Precursor 1 (All Source Records) **: One record per program entity
Was this article helpful?