[MI/URSA-CORE] Source Local Provider ID Crosswalk to Data Model Provider ID
- 28 Jun 2025
- 1 Minute to read
- Print
- DarkLight
[MI/URSA-CORE] Source Local Provider ID Crosswalk to Data Model Provider ID
- 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 source local provider ID value, with the matched Provider ID data model key; implements matching logic to find records for the same provider in source data and consolidate them under a single Provider ID value.
Metadata
- Table Name: ursa.mi_ursa_022
- Layer: METADATA_AND_INTEGRATION
- Object Type: Integrator
- Temporal Class: Entity
- Case ID: Source ID, Source Local Provider ID
- Primary Key: Source ID, Source Local Provider ID
Published Fields
Data Model Keys
- 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)
Operations Support Fields
- Provider Operational ID
Provider Fields
- Provider NPI
- Provider TIN
- Provider CCN
- Provider Description
- Provider First Name
- Provider Middle Name
- Provider Middle Initial
- Provider Last Name
- Provider Date of Birth
- Is Provider Sex Female
- Is Provider Sex Male
- Practice Address Line 1
- Practice Address Line 2
- Practice Address City
- Practice Address State Abbreviation
- Practice Address ZIP Code 5-Digit
- Provider Phone
Metadata Fields
- Documentation Datetime
- 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)
Validation Only Fields
- Provider Operational ID Original
- Provider NPI Original
- Provider TIN Original
- Provider CCN Original
- Provider Description Original
- Provider First Name Original
- Provider Middle Name Original
- Provider Middle Initial Original
- Provider Last Name Original
- Provider Date of Birth Original
- Is Provider Sex Female Original
- Is Provider Sex Male Original
- Practice Address Line 1 Original
- Practice Address Line 2 Original
- Practice Address City Original
- Practice Address State Abbreviation Original
- Practice Address ZIP Code 5-Digit Original
- Provider Phone Original
Was this article helpful?