Source Dataset Requirements for Patients

You align your source data with the industry-standard schema for patient data that is supplied by this template.

The patients template includes a predefined, standardized schema for patient data. The mastering flow for data products produced by this template includes a schema mapping step in which you identify how columns in your source datasets correspond to the attributes in the supplied schema.

To prepare, review the general Requirements for Source Datasets. Then, identify the column or columns in each of your source datasets that you will map to the patient schema:

Unified Attribute Description
address_line_1 Line 1 of the patient’s address.
address_line_2 Line 2 of the patient's address.
city City of the patient’s address.
country Country of the patient’s address.
dob The patient's date of birth.
email The patient's email address.
fax_number The patient’s fax number.
first_name The patient's first name.
gender The patient's gender.
last_name The patient's last name.
middle_name The person's middle name.
name_prefix The patient's prefix, such as Dr. or Ms.
name_suffix The patient's suffix, such as Jr. or Senior.
patient_national_identification_number The patient's national identification number, such as Social Security Number.
phone_number The patient's phone number.
phone_number_alt The patient's alternate phone number.
postal_code Postal (zip) code of the patient’s address
primaryKey The primary key used in the source dataset to uniquely identify each record. See About Primary Keys for more information.
region The region of the patient’s address, such as the state or territory.
trusted_id A non-unique key, such as a patient identification number used by your internal systems. The clustering model always clusters together records that have the same trusted_id. If your data does not include identifiers that represent a definite match, do not map any columns to trusted_id.

After you map your source data fields to these attributes, Tamr Cloud can enrich your data and consolidate similar records into entities.

Tip: You can also add attributes to the unified schema and map columns that you want to include in the mastered data product to them. The template does not use these additional attributes as part of the mastering process.