[NO/URSA-CORE] Provider-Health System Affiliation Timelines
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[NO/URSA-CORE] Provider-Health System Affiliation Timelines
- 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 provider - health system affiliation timeline period during which the provider was affiliated with the health system. Providers may have multiple concurrent affiliations with different health systems.
Metadata
- Table Name: ursa.no_ursa_core_prov_006
- Layer: NATURAL_OBJECT
- Object Type: Simple Timeline
- Temporal Class: Interval (Timeline)
- Case ID: Provider ID, Affiliated Health System ID
- Interval Start Date: Period Start Date
- Interval End Date: Period End Date
- Primary Key: Provider ID, Affiliated Health System ID, Period Start Date, Period End Date
Published Fields
Data Model Keys
- Provider ID -- The database identifier for a individual or organization provider. (See also [URSA-CORE] Provider)
- 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 Provider ID -- The original value in the source system for the current record's Provider ID. (See also [URSA-CORE] Provider ID)
- Source Local Affiliated Health System ID
Date Fields
- Period Start Date
- Period End Date
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
- 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] Provider-Health System Affiliation Timelines, Precursor 1 (All Source Records): One record per provider-health system affiliation timeline period
Was this article helpful?