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:
|Line 1 of the patient’s address.
|Line 2 of the patient's address.
|City of the patient’s address.
|Country of the patient’s address.
|The patient's date of birth.
|The patient's email address.
|The patient’s fax number.
|The patient's first name.
|The patient's gender.
|The patient's last name.
|The person's middle name.
|The patient's prefix, such as Dr. or Ms.
|The patient's suffix, such as Jr. or Senior.
|The patient's national identification number, such as Social Security Number.
|The patient's phone number.
|The patient's alternate phone number.
|Postal (zip) code of the patient’s address
|The primary key used in the source dataset to uniquely identify each record. See About Primary Keys for more information.
|The region of the patient’s address, such as the state or territory.
|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
If your data does not include identifiers that represent a definite match, do not map any columns to
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.
Updated about 1 month ago