Configure HCP STD10 recipes
Learn more about the HCP STD10 recipes configuration.
To export HCP data, you must configure details in the following recipes:
-
MedPro | TRG | STD10 – HCP Main Recipe- Configure the custom schedule to trigger jobs. -
MedPro | PROC | STD10 - Reltio Export HCP & load STD10 file to SFTP- Specify the HCP attributes that must be exported. -
MedPro | PROC | STD10 - HCP File conversion - Python Code- Any changes to the attribute name must be configured here.
All the recipes are available under the STD10 folder.
Configure jobs for main recipe
Trigger STD10 jobs by scheduling the cron expressions via the Custom schedule in MedPro | TRG | STD10 – HCP Main Recipe available in the STD10 folder. You can also specify the schedule you want in the Time Unit dropdown, which can be Daily, Weekly, or Monthly.
Configure attributes for export
Open the MedPro | PROC | STD10 - Reltio Export HCP & load STD10 file to SFTP recipe and in step 3, based on the Reltio Data model, update the varExportAttributes field with the attributes that you want to export. Ensure you add only those attributes that are required for the STD10HCP export. A sample is given below:
The following table lists the fields that can be exported, and their corresponding Reltio attributes that you need to include in the varExportAttributes field.
| Export fields | Reltio attributes |
|---|---|
| Last Name | attributes.LastName |
| First Name | attributes.FirstName |
| Middle Initial | attributes.MiddleInitial or attributes.MiddleName |
| Title | attributes.Title |
| Suffix Name | attributes.SuffixName |
| Address Type | attributes.Address.AddressType |
| Address Line 1 | attributes.Address.AddressLine1 |
| Address Line 2 | attributes.Address.AddressLine2 |
| City | attributes.Address.City |
| State | attributes.Address.SateProvince |
| Zip Code | attributes.Address.Zip.Zip5 |
| Zip Code Extension | attributes.Address.Zip.Zip4 |
| Country | attributes.Address.Country |
| License | attributes.License |
| DEA Number | attributes.DEA |
| Customer Provided Number | Uri |
| Phone | attributes.Phone |
| Professional Designation | attributes.ProfessionalDesignation |
| Specialty | attributes.Specialties |
| NPI Number | attributes.Identifiers |
| Crosswalk | crosswalks |
Convert HCP file
The MedPro | PROC | STD10 - HCP File conversion - Python Code recipe requires a change in step 15 (as shown in the image below) if there are any change in the Reltio Attributes Name, update the JSON structure in this step under Sample Document section. The sample JSON structure is required to parse the JSON and generate the datapills.
You must then map the datapills under the respective Attribute fields in step 19. For example, if you have changed the Last Name attribute, then pick value datapills under Last Name from step 17 and add the datapills value to the lastName field. Follow the same steps for the attributes in Identifier List, Phone List, License List, Address List (Step - 20, 21, 22 ,23) as well.
Add the RDM Canonical value of NPI Identifier Type under npiNumber.
Add the RDM Canonical value of Phone Type under phoneTypeValue. Based on the provided value, the Phone Number value will be picked.
Add the RDM Canonical value of Address Type under addressTypeValue . Based on the provided value, Address will be picked.