In the Reltio model, a simple attribute with a set of values can be defined by a lookup collection.

Lookups can be changed dynamically by updating additional lookup values. Example: attribute Country for Address. Lookups provide human-readable strings for attributes that store code values. Reltio recommends using the string data type for lookup type attributes, as it is the only supported data type. For example, an Individual entity has an attribute for the person's education: Area of Study with values Computer Science, Engineering, Logistics, and so on. These values are arranged as lookups where the attribute stores the Area of Study code and the lookup table resolves that code to a human-readable description .

To use lookups for a list of values:

• Provide lookup values
• Specify the lookup in your attribute configuration

To support business cases when data is driven by other data (for example, the list of states depends on the country), Reltio Context Intelligence Platform provides dependent lookups when one attribute value drives the values of another attribute.

Special features of dependent lookups:

• One dependent lookup value can belong to multiple dependent values - for example, MD (specialty, Medical Doctor) exists in multiple countries. Some specialties can be in multiple countries, while other specialties can belong only to one country.

• There can be multiple level dependent lookups over a sequence of dependent lookups when one lookup drives another one, then another - for example, Continent > Country > State > County > City.

Lookups in Reltio platform have the following tree-like structure:

{
   "SPECIALTY_GROUPS":{
      "OTHER":{
         "displayName":"OTHER"
      },
      "PEDIATRICS":{
         "displayName":"PEDIATRICS"
      },
      "PSYCHIATRY":{
         "displayName":"PSYCHIATRY"
      }
   },
   "SPECIALTIES":{
      "AS":{
         "displayName":"ABDOMINAL SURGERY",
         "parent":"SPECIALTY_GROUPS.OTHER"
      },
      "ADM":{
         "displayName":"ADDICTION MEDICINE",
         "parent":"SPECIALTY_GROUPS.PSYCHIATRY"
      },
      "ADP":{
         "displayName":"ADDICTION PSYCHIATRY",
         "parent":"SPECIALTY_GROUPS.PSYCHIATRY"
      },
      "ADL":{
         "displayName":"ADOLESCENT MEDICINE",
         "parent":"SPECIALTY_GROUPS.OTHER"
      }
   }
}

Per-tenant lookups structure looks like a JSON object where each attribute is a lookup code, for example: SPECIALTY_GROUPS and SPECIALTIES. For each lookup code, there is a JSON object with possible code values and resolutions. In the above example, the ADL attribute values would resolve to ADOLESCENT MEDICINE.

To configure an attribute type to obtain a value through a lookup, an additional field lookupCode needs to be added to the attribute configuration. You can configure the attributes within: Entity Types, Group Types, Relation Types, Graph Types, and Interaction Types.

{
   "URI":"configuration/entityTypes/HCP/attributes/Specialty",
   "label":"Specialty",
   "name":"Specialty",
   "lookupCode":"SPECIALTY"
}