Issues Handling Across Reference Data Sets in US Health Insurance

An interesting reference data case example was done at a health insurance company based in the US. The case is illustrated below but it contains an animation that you can see by following this link.


In this example, the Collibra Platform functions as a hub for reference data management. There are two ways to trigger change. In a first embodiment, the change is triggered by a business user who raises a ticket requesting a new code value to be added to the code sets. To this end, the business user fills in a form in order to provide as much information as possible to the responsible (e.g., chief steward or DGO) who will make an informed decision to onboard or reject the requested code value. If on-boarded, a sequence of activities is triggered and assigned automatically (by means of a custom workflow), in which subject matter experts and stewards collaborate to define the code value and publish it once approved. Once approved, the registered IT systems are informed about the update, so they can pull (through the Collibra API) the new code and add it to their code tables. This promotes the status of the code from “accepted”  to “deployed”. In a second embodiment, it is not the human business user but any IT system that does operational data management activities and to this end applies the code sets in Collibra, that will report an issue with existing codes (see “push invalid codes” in the diagram) or the lack for the latter. This triggers another cycle or drafting and approving.

You have to login to comment.