[NO/URSA-CORE] Provider Contracts
- 28 Jun 2025
- 2 Minutes to read
- Print
- DarkLight
[NO/URSA-CORE] Provider Contracts
- Updated on 28 Jun 2025
- 2 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback!
Object Description
One record per provider contract record.
Metadata
- Table Name: ursa.no_ursa_core_fin_008
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Interval
- Case ID: Provider Contract ID
- Interval Start Date: Covered Period Start Date
- Interval End Date: Covered Period End Date
- Primary Key: Provider Contract ID
Published Fields
Data Model Keys
- Provider Contract ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Provider Contract. (See also [URSA-CORE] Provider Contract)
- Payor ID -- The identifier for the health insurance organization associated with the current record.
- Plan ID -- The identifier for a particular health insurance plan product offered by a payor.
- Provider ID -- The database identifier for a individual or organization provider. (See also [URSA-CORE] Provider)
- Source ID -- The identifier for the original source data system from which the current record originated.
Source Local Keys
- Source Local Provider Contract ID
- Source Local Provider ID -- The original value in the source system for the current record's Provider ID. (See also [URSA-CORE] Provider ID)
Operations Support Fields
- Provider Contract Operational ID -- The user-facing value used by staff used to uniquely identify the Provider Contract in their administrative systems and/or day-to-day operations. (See also [URSA-CORE] Provider Contract)
Date Fields
- Covered Period Start Date
- Covered Period End Date
- Contract Effective Date
Provider Fields
- Provider Description in Contract -- The name or description of the provider as given in the contract.
- Provider NPI in Contract
- Provider TIN in Contract -- The TIN identified for the contract provider as given in the contract; note that this may not be a dedicated TIN for the provider, nor must it be the provider's current primary billing TIN.
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)
Terms
- Provider Contract: An agreement between a provider (either an individual or organization) and a counterparty (typically a payor organization or subsidiary), often allowing the provider to bill for certain qualifying services and/or defining a risk-sharing or other financial relationship between the provider and the counterparty. Key information describing a Provider Contract includes one or more provider identifiers, such as a TIN or NPI, a payor identifier, and a time period during which the contract is active.
Foreign Keys
- billing_prov_id → ursa.no_ursa_core_prov_001.prov_id
- trx_payor_id → ursa.no_ursa_core_struct_004.payor_id
- trx_plan_id → ursa.no_ursa_core_struct_005.plan_id
- bill_id → ursa.no_ursa_core_fin_011.bill_id
- bill_service_line_item_id → ursa.no_ursa_core_fin_012.bill_service_line_item_id
- pat_id → ursa.no_ursa_core_pat_001.pat_id
- payor_id → ursa.no_ursa_core_struct_004.payor_id
- plan_id → ursa.no_ursa_core_struct_005.plan_id
- plan_attributee_prov_id → ursa.no_ursa_core_prov_001.prov_id
- plan_attributee_individual_prov_id → ursa.no_ursa_core_prov_001.prov_id
- plan_attributee_prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
- prov_id → ursa.no_ursa_core_prov_001.prov_id
Dedicated Precursors
- [NO/URSA-CORE] Provider Contracts, Precursor 1 (All Source Records): One record per provider contract record.
Was this article helpful?