[NO/URSA-CORE] Payors
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[NO/URSA-CORE] Payors
- 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 payor organization.
Metadata
- Table Name: ursa.no_ursa_core_struct_004
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Entity
- Case ID: Payor ID
- Primary Key: Payor ID
Published Fields
Data Model Keys
- Payor ID -- The identifier for the health insurance organization associated with the current record.
- Source ID -- The identifier for the original source data system from which the current record originated.
Source Local Keys
- Source Local Payor ID -- The identifier for the payor organization in the original source data system.
Operations Support Fields
- Payor Operational ID
Insurance Fields
- Payor Description
- Payor Legal Name
- Payor Address Line 1
- Payor Address Line 2
- Payor City
- Payor State Abbreviation
- Payor ZIP Code
- Payor Telephone Number
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] Payors, Precursor 1 (All Source Records): One record per payor organization.
Was this article helpful?