Reltio Enrichment with MedPro prerequisites
Learn about the prerequisites for using Reltio Enrichment with MedPro.
Before you use the Reltio Enrichment with MedPro, understand MedPro file formats and Reltio roles and data model considerations. You must have the licenses to MedPro Data Enrichment from Reltio to be able to access these RIH recipes in your RIH account.
STD10 file format
Reltio MDM exports customer data to Reltio Enrichment with MedPro in a defined fixed STD10 file format. The MedProID BulkID module accepts an input format of practitioner and organization licensing and demographic attributes and matches them to a licensing data source in the MedProID® database. After the automated and optional manual matching, an output dataset will be generated from BulkID containing all records submitted in the data structure of MedPro's Standard 80 (STD80) return layout.
The following table lists the Secure File Transfer Protocol (SFTP) folder structure for the STD10 when customer data is exported from Reltio MDM to MedPro.
| HCP | HCO |
|---|---|
|
|
TD80 file format
- HCP
- Healthcare Practitioner extracts:
- Standard BulkId Extract - Returns all records submitted inbound to the BulkID and appends licensing details for records that have a match in the MedProID database. If the inbound record matches the record in Reltio Enrichment with MedPro, the licensing details are added to the customer's MedPro database for tracking purposes.
- Sample Updates Extract - Provides updates to the state license sample eligibility for records that are stored in the customer's MedPro database.
- Proactive Updates Extract - Provides any updates to the state licensing information for records that are stored in the customer's MedPro database.
- HCO
- Healthcare Organization extracts:
- Standard BulkId Extract - Returns all records submitted inbound to the BulkID and appends licensing details for records that are match to the MedProID database. If the inbound record matches to the record in MedPro, the licensing details are added tgo the customer's MedPro "universe" for tracking purposes.
- Eligibility Updates Extract - Provides any updates to the state license sample eligibility for records that are stored in the customer's MedPro "universe".
| HCP | HCO |
|---|---|
|
|
Roles
You need to have a role with the appropriate access permissions (rights and privileges) for the Reltio Integration Hub to use the Reltio Enrichment with MedPro: ROLE_INTEGRATION_SPECIALIST or ROLE_INTEGRATION_CUSTOMER_ADMIN.
Reltio data model
Understand how the organization of data in your Reltio data model impacts the integration with MedPro records:
-
Reference address- Addresses are stored as reference attributes. Ensure that the surrogate key configuration is configured in your data model and available for all enrichment sources. For more information, see topic Configuring surrogate keys. -
Address Line- Address line 1 is linked to or dependent on Address line 2 and Address line 3. If you leave the Address Line 1 blank, then the address in the Address Line 2 is considered as Address Line 1. -
Type attribute of a nested attribute- Ensure that all 'types' e.g. Address Type, Phone Type etc. of nested attributes have RDM mappings. You can find default RDM mappings in the Reltio for Life Sciences. For more information, see topic Preconfigured User Interface for B2B. -
Special characters- Revise or remove attributes that contain only special characters as Reltio Enrichment with MedPro filters these out. . -
Enrichment- The enriched source records that we receive from MedPro is associated with the customer record in Reltio based on the following fields in the STD80 file:- Customer Comment Field 1 (Source Type)
-
Customer Comment Field 2 (Source ID)
-
Customer Comment Field 3 (Source table)Note: If this Customer Comment Field 3 is blank, it will not be imported from the STD80 file during integration..