[NO/URSA-CORE] Provider-Provider Group Affiliation Timelines
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[NO/URSA-CORE] Provider-Provider Group 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 - provider group affiliation timeline period during which the provider was an active provider in the provider group. Providers may have multiple concurrent affiliations with different provider groups.
Metadata
- Table Name: ursa.no_ursa_core_prov_005
- Layer: NATURAL_OBJECT
- Object Type: Simple Timeline
- Temporal Class: Interval (Timeline)
- Case ID: Provider ID, Affiliated Provider Group Provider ID
- Interval Start Date: Period Start Date
- Interval End Date: Period End Date
- Primary Key: Provider ID, Affiliated Provider Group Provider 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 Provider Group Provider ID -- The provider group the individual provider is employed by or otherwise affiliated with. (See also [URSA-CORE] Provider Group)
- 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 Provider Group Provider 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_prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
Dedicated Precursors
- [NO/URSA-CORE] Provider-Provider Group Affiliation Timelines, Precursor 1 (All Source Records): One record per provider-provider group affiliation timeline period
Was this article helpful?