Configure and enable Reltio Enrichment with 340B

Learn how to configure and enable Reltio Enrichment with 340B for your tenant.

Enabling Reltio Enrichment with 340B adds the 340B program as a new data source in your tenant. Treat it as a new source and assess the impact on your existing implementation before you begin. Depending on how your tenant is configured, enabling this enrichment results in matching, merging, and data enrichment activity. The resulting profiles can cause further consolidation based on your tenant's match rules.

Prerequisites

Before you begin, make sure you meet the following requirements:

You must have reviewed the Reltio Enrichment with 340B data model and mapping and identified the attributes you want to synchronize.
Provisioning must be complete for Reltio Enrichment with 340B. This means that:
1. Your tenant is registered for DTSS.
2. Your customer administrator is assigned the ROLE_DTSS_DEPLOYER role.
You must have reviewed your existing RDM, cleanser, survivorship, and match rule configurations and applied any required changes before enabling the enrichment.

Important:

If you plan to use REALTIME mode, enable both streaming and streamingAPI in your tenant before you begin. You can confirm the streamingEnabled and streamingAPIEnabled in your tenant configuration before you begin.

Submit a support request if you need help.

To configure and enable Reltio Enrichment with 340B:

Review the attributes available from the 340B data tenant.

For more information, see Reltio Enrichment with 340B data model and mapping.
If your customer tenant is missing attributes you want to synchronize, add them using the JSON in Reltio Enrichment with 340B data model and mapping before continuing.

Copy the 340B DTSS subscription template.

It applies to both the Healthcare and Life Sciences velocity packs.

Show the template

{
  "dataTenantId": {
    "id": "{{dataTenantId340b}}"
  },
  "customerTenantId": {
    "id": "{{tenantId}}"
  },
  "bringGoldenRecord": true,
  "mappings": [
    {
      "copyFromDT": "configuration/entityTypes/HCO",
      "copyToCT": "configuration/entityTypes/HCO",
      "attributes": [
        {
          "copyFromDT": "configuration/entityTypes/HCO/attributes/Name",
          "copyToCT": [
            "configuration/entityTypes/HCO/attributes/Name"
          ]
        },
        {
          "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers",
          "copyToCT": [
            "configuration/entityTypes/HCO/attributes/Identifiers"
          ],
          "attributes": [
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ID",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ID"
              ]
            },
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/Type",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/Type"
              ]
            },
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/Status",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/Status"
              ]
            },
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ActivationDate",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ActivationDate"
              ]
            },
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/DeactivationDate",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/DeactivationDate"
              ]
            },
            {
              "copyFromDT": "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ReactivationDate",
              "copyToCT": [
                "configuration/entityTypes/HCO/attributes/Identifiers/attributes/ReactivationDate"
              ]
            }
          ]
        }
      ]
    }
  ],
  "synchronizationConfig": {
    "entities": [
      {
        "action": "AUTOSUBSCRIBE",
        "types": [
          "configuration/entityTypes/HCO"
        ],
        "matchRules": [
          "configuration/entityTypes/HCO/matchGroups/Exact340B"
        ],
        "thresholds": {
          "default": 1,
          "custom": [
            {
              "matchRules": [
                "configuration/entityTypes/HCO/matchGroups/Exact340B"
              ],
              "threshold": 10
            }
          ]
        }
      }
    ],
    "dtSyncType": "REALTIME",
    "ctSyncType": "REALTIME",
    "contracts": []
  },
  "autoRematch": true
}

You can also download the template as a JSON file: 340B DTSS subscription template.

Edit the template to match your requirements:
- Replace {{dataTenantId340b}} with your 340B data tenant ID.
- Replace {{tenantId}} with your customer tenant ID.
- Update the attribute mappings to match your customer tenant configuration. Data types must match even when naming conventions differ.
- Verify the match rules meet your requirements. The template uses Exact340B by default. For the full list of available match rules, see Healthcare Organization (HCO) match rules.
Post the completed subscription JSON to the DTSS subscription endpoint.

The request body is the subscription JSON you edited in the previous step.
Verify the subscription was added successfully by confirming the response is 200 OK.
If your customer tenant contains existing data before adding the subscription, or if you change the match rules in the subscription, run a manual match task to perform DTSS matching and surface potential matches.
If you are deploying to a new empty tenant with ctSyncType set to REALTIME, skip this step and step 8. Matching will occur as entities are created or updated in the customer tenant.
Run a manual subscribe task to automatically process merges, based on the auto-subscribe rules defined in the DTSS subscription. This step completes the backfill and enriches the customer tenant profiles.

Result

Reltio Enrichment with 340B is active for your tenant. The 340B data tenant begins synchronizing HCO data to your customer tenant in real time based on your subscription configuration and match rules. If you ran the backfill tasks, existing profiles are enriched during the initial match.

Validation

Confirm that 340B data appears on matching HCO profiles in your customer tenant. If profiles already existed, confirm the backfill tasks completed successfully before checking profile enrichment.

For more information, see Reltio Enrichment with 340B at a glance.

Unify and manage your data

Configure and enable Reltio Enrichment with 340B

Footer