Reltio NPI HCO Attributes Mapping Rules

Learn about how the NPI HCO attributes are mapped with the HCO headers specified in the source file as per the mapping rules.

Each Reltio NPI HCO attribute is mapped with the HCO headers specified in the source file based on mapping rules. Before understanding the mapping rules, you need to know the following exceptional information about Reltio NPI HCO attributes:

There are some Reltio NPI HCO attributes for which HCO headers are not available in the NPI source file. These attributes are not even hard-coded. Such attributes are created by referring to the Healthcare_Provider_Taxonomy_Code value specified in the NPI source file. For each taxonomy code value (1 to 15), the following attributes are created:
- Taxonomy.Group
- Taxonomy.ProviderType
- Taxonomy.Classification
- Taxonomy.Specialization
The hard-coded Reltio attributes are:
- Address.AddressType= Mailing
- Address.Country=United States
- Phone.Type="Business"
- Phone.Type="Fax"
- Address.AddressType = Business
- Address.Country=United States
- Phone.Type="Business"
- Phone.Type="Fax"
The NPI HCO headers in source file for which Reltio attributes are not applicable or defined; the Reltio attribute’s value is N/A.
The cleanse functions (hcoNameCleanser and phoneCleanser) to clean the HCO attributes values are Reltio defined.

Table 1. Reltio NPI HCO Attributes Mapping Rules
Attributes Mapping Rules	Indicates that...
Direct	The Reltio attribute is directly mapped with the headers specified in the NPI source file.
`If Provider_Other_Organization_Name_Type_Code = 3 then create "DoingBusinessAsName" attribute else create "Name" attribute`	If the value of the `Provider_Other_Organization_Name_Type_Code` header in the NPI source file is 3, then the Reltio attribute `DoingBusinessAsName` is mapped with the header. If not, then the Reltio attribute `Name` is mapped.
`If Length=9, zip5= First 5 digits & zip4=Last 4 digits If Length=5, zip5= All 5 digits`	If the length of the postal address specified in the NPI source file is nine digits, then the first five digits are mapped as zip5 and the last four digits are mapped as zip4. If the length of the postal address is only five digits, then all the five digits are mapped as zip5.
Load from `Healthcare_Provider_Taxonomy_Group_XX` (XX represents the taxonomy group value for the respective taxonomy code value.)	The Reltio attribute `Healthcare_Provider_Taxonomy_Group` that has the same value of the `Healthcare_Provider_Taxonomy_Code` specified in the NPI source file; is mapped with the header.
Lookup from Taxonomy Provider Type	The Reltio attribute `Taxonomy.ProviderType` is mapped based on the lookup that appears for the taxonomy provider type, for the selected taxonomy code.
Lookup from Taxonomy Classification	The Reltio attribute `Taxonomy.Classification`is mapped based on the lookup that appears for the taxonomy classification, for the selected taxonomy code.
Lookup from Taxonomy Specialization	The Reltio attribute `Taxonomy.Specialization` is mapped based on the lookup that appears for the taxonomy specialization, for the selected taxonomy code.

Accelerate the Value of Data

Reltio NPI HCO Attributes Mapping Rules

Footer