[NO/URSA-CORE] Patients
- 28 Jun 2025
- 3 Minutes to read
- Print
- DarkLight
[NO/URSA-CORE] Patients
- Updated on 28 Jun 2025
- 3 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback!
Object Description
One record per patient.
Metadata
- Table Name: ursa.no_ursa_core_pat_001
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Entity
- Case ID: Patient ID
- Primary Key: Patient ID
Published Fields
Data Model Keys
- Patient ID -- The internal database identifier (used, e.g., for joins and primary keys) for the patient. This value is typically mastered, i.e., all records for the same patient, regardless of the source data system from which that record originated, should have the same Patient ID value. (Note that while the mastered Patient ID value might resemble a local identifier used in one of the upstream data sources, this does not indicate any special priority of that source system in determining the characteristics of the patient.) (See also [URSA-CORE] Patient)
- Document ID
- 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 -- An identifier used to uniquely identify the patient in the original source data system; typically derived through a data mastering process that identifies duplicate Source Local Patient ID values for the same (real-life) patient.
Operations Support Fields
- Patient Operational ID
Patient Fields
- Patient SSN
- Patient MBI
- Patient First Name
- Patient Middle Name
- Patient Middle Initial
- Patient Last Name
- Patient Date of Birth
- Patient Year of Birth
- Patient Date of Death
- Is Patient Deceased
- 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 County FIPS Code
- Patient County Description
- UW HIP Area Deprivation Index National Percentile
- UW HIP ADI Quintile Category
- UW HIP ADI Decile Category
- CDC SVI Overall National Percentile
- CDC SVI Overall Quintile Category
- CDC SVI Socioeconomic Theme National Percentile
- CDC SVI Socioeconomic Quintile Category
- CDC SVI Household / Disability Theme National Percentile
- CDC SVI Household / Disability Quintile Category
- CDC SVI Minority / Language Theme National Percentile
- CDC SVI Minority / Language Quintile Category
- CDC SVI Housing / Transportation Theme National Percentile
- CDC SVI Housing / Transportation Quintile Category
- Census ACS Percentage Below Poverty
- Census ACS Unemployment Rate
- Census ACS Per Capita Income
- Census ACS Percentage Without HS Diploma
- Census ACS Percentage 65 and Older
- Census ACS Percentage Aged 17 and Younger
- Census ACS Percentage with Disability
- Census ACS Percentage Single-Parent Households
- Census ACS Percentage Minority
- Census ACS Percentage Speak English Less Than Well
- Census ACS Percentage Households Without Vehicle
- Census ACS Percentage Uninsured
- Patient Phone
- Patient Email
- Is Patient Sex Female
- Is Patient Sex Male
- Is Patient Race American Indian or Alaska Native
- Is Patient Race Asian
- Is Patient Race Black or African American
- Is Patient Race Native Hawaiian or Other Pacific Islander
- Is Patient Race White
- Is Patient Race Other
- Is Patient Ethnicity Hispanic or Latino
- Employer Description
- Patient Employee 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)
- Random Integer 1 to 1000
Terms
- Patient: A past, current, or potential future individual consumer of health care services.
Dedicated Precursors
- [NO/URSA-CORE] Patients, Precursor 1 (All Source Records): One record per patient record in a data source
Was this article helpful?