Configure HCO STD10 recipes
Learn more about the configuration for HCO STD10 recipes.
Configure jobs for main recipe
You can now learn more about configuration required for recipes to export data in the STD10 format. All the recipes are available under STD10 folder.
Trigger STD10 jobs by scheduling the cron
expressions via the Custom schedule in MedPro | TRG | STD10 – HCO 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 HCO & 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 STD10HCO 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 |
---|---|
Organization Name | attributes.Name |
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 |
NPI Number and NCPDP Number | attributes.Identifiers |
Crosswalk | crosswalks |
HCO File conversion
The MedPro | PROC | STD10 - HCO File conversion - Python Code recipe requires a change in step 15 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. For example, if you have changed the Organization Name attribute, then pickup value datapills under organizationName
from step 17add the datapills value to the organizationName
field.
Add the RDM Canonical value of NPI Identifier Type under npiNumber
and NCPDP Identifier Type under ncpdpNumber
.
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
in this step. Based on the provided value, the Address will be picked.