[MI/URSA-CORE] Source Local Patient ID Crosswalk to Data Model Patient ID
- 28 Jun 2025
- 2 Minutes to read
- Print
- DarkLight
[MI/URSA-CORE] Source Local Patient ID Crosswalk to Data Model Patient ID
- 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 Source Local Patient ID value, with the matched Patient ID data model key; implements matching logic to find records for the same patient in source data and consolidate them under a single Patient ID value.
Metadata
- Table Name: ursa.mi_ursa_021
- Layer: METADATA_AND_INTEGRATION
- Object Type: Integrator
- Temporal Class: Entity
- Case ID: Source ID, Source Local Patient ID
- Primary Key: Source ID, Source Local Patient 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 Patient ID -- The internal database identifier for the patient in the source data system this record originated from. (See also [URSA-CORE] Patient)
- Source Local Patient Master Identity ID
Operations Support Fields
- Patient Operational ID
Patient Fields
- Patient SSN
- Patient First Name
- Patient Middle Name
- Patient Middle Initial
- Patient Last Name
- Patient Date of Birth
- Patient Date of Death
- Patient Address Line 1
- Patient Address Line 2
- Patient City
- Patient State Abbreviation
- Patient ZIP Code 5-Digit
- Patient ZIP Code 9-Digit
- Patient ZIP Code 3-Digit
- Patient Phone
- Patient Email
- Is Patient Sex Female
- Is Patient Sex Male
- Employer Description
- Patient Employee Number
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
- Patient Operational ID Original
- Source Local Patient Master Identity ID Original
- Patient SSN Original
- Patient First Name Original
- Patient Middle Name Original
- Patient Middle Initial Original
- Patient Last Name Original
- Patient Date of Birth Original
- Patient Date of Death Original
- Patient Address Line 1 Original
- Patient Address Line 2 Original
- Patient City Original
- Patient State Abbreviation Original
- Patient ZIP Code 5-Digit Original
- Patient ZIP Code 9-Digit Original
- Patient ZIP Code 3-Digit Original
- Patient Phone Original
- Patient Email Original
- Is Patient Sex Female Original
- Is Patient Sex Male Original
- Employer Description Original
- Patient Employee Number Original
- Earliest Source Data Effective Datetime
- Earliest Documentation Datetime
Was this article helpful?