Lookups

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

Important: Reltio recommends using Reference Data Management for this objective.

Lookups can be changed dynamically by updating additional lookup values. Example: attribute Country for Address.

Lookups provide a meaningful string for attributes that use code values. For example, Individual can have an attribute for the person's education: Area of Study with values Computer Science, Engineering, Logistics, and so on. These values can be arranged as lookups. The attribute value will contain the Area of Study code, and the description will be resolved from the lookup table.

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 Connected Cloud 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.

Note: Users can work with dependent and non-dependent lookups in Edit mode (for information about Read, Edit, and Common modes refer to Profiles View). Users cannot edit a dependent lookup value that does not have an attribute value for the attribute on which it depends.

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.

Note: The Parent field is optional.

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.

Lookup Structure

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