--- updatedAt: 2026-06-30T13:07:35.000Z agentTools: projectIndex: https://cloud.docs.tamr.com/llms.txt --- # Steps Completed by Patients When you create a <> using the patients template, <> creates a mastering flow with steps specific to patient mastering. The following table describes each step in the patients flow, and explains which steps usually need to be edited for your data. If you need to make changes to the mastering flow beyond those described in this documentation, contact Support at for assistance. [block:html] { "html": "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n\n \n \n \n \n\n \n \n \n\n \n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n

Usually Requires Changes\n	Step\n	Description\n
✅\n	Add Data\n	You verify that source data meets both general requirements \n and template-specific \n requirements. Then, you \n add source data.\n
✅\n	Align to Patients Mastering Data Model\n	You map input columns \n to attributes in the supplied schema. If you add attributes to the unified schema, you will need to update the following steps, as described in the rows below, to ensure that these attributes appear in your final mastered entities:\n \n Consolidate Records \n Configure Attributes \n \n
❌\n	Create `tamr_record_id`\n	This transformation step ensures that each source record has a unique primary key across all \nsource datasets by adding a new primary key field: `tamr_record_id`. The `tamr_record_id`\n is a 128-bit hash value of the source dataset name and the source primary \nkey. See the\n Tamr Core \n documentation for a description of the function used to generate the hash value. \n \n Important: If records within the same source dataset have duplicate primary key values, the `tamr_record_id` value for those records will also be duplicates.\n If you mapped an empty placeholder column to the `trusted_id` attribute, add the following transformation: `SELECT *, '' as trusted_id;`.\n
❌\n	Prepare Data for Address Enrichment\n	This step transforms the data in the unified dataset to match the expected inputs for the address enrichment service.\n
❌\n	Enrich Address\n	This step standardizes and validates address information, and enriches addresses with latitude, longitude, and detailed address information.\n See \n\nAddress Standardization, Validation, and Geocoding.\n
❌\n	Prepare Address Fields\n	This step transforms the data in address fields in the unified dataset to prepare for clustering.\n
❌\n	Prepare Data for Phone Enrichment\n	This step transforms the data in the unified dataset to match the expected inputs to the phone number \ndata quality service included in the mastering flow. This step replaces empty country values in source\n records with the country returned by the Enrich Address step.\n\n
❌\n	Enrich Phone\n	This step standardizes and validates phone number information.\n See \n\nPhone Number Enrichment.\n
❌\n	Prepare for Clustering\n	This step transforms the data in the unified dataset to create the fields used by the \ntrained clustering model to identify similar and matching records. \n \nThe fields created as input to \n the model are prefixed with `ml_`. Many of these `ml_` fields are created as arrays of unified source \nfields and fields added by the enrichment services. The model identifies \nthe most similar values across the arrays and assigns weights based on these similarities.\n
❌\n	Apply Clustering Model\n	This step groups records that refer to the same entity into a cluster, using the trained model.\nSee Features of Patients.\n
✅\n	Consolidate Records\n	This step applies rules to produce a single record, called the mastered entity record, that best represents a cluster. For most fields, these rules select the most common value from the clustered records.\n \n Additionally, this step adds a Tamr ID (`tamr_id`) to each mastered entity record. The Tamr ID \nis a unique, persistent id.\n \nIf you added new attributes in the Schema Mapping step, add lines in the transformations to \ntell Tamr Cloud what value to set for each attribute when creating the mastered entity. See \nModifying Record Consolidation Transformations.\n
✅\n	Configure Attributes\n	You configure how mastered entity attributes appear in Tamr Cloud and published datasets See \nConfiguring Data Display.\n

\n" } [/block]