DATA CATALOGUE AND DATA LINEAGE
With so many different data vendors supplying data, it has become increasingly important for organisations to be able to understand what vendor data fields actually mean. The Xenomorph Data Catalogue maps all equivalent data fields into a common schema and provides graphical information about the various vendors’ naming conventions.
Using a common schema enables us to seamlessly convert data requests from one particular vendor into the format of another. This may be useful when recognising that vendor A provides the same data as vendor B, but at a cheaper price. Without changing the subscribing systems, organisations are able to map the data from one vendor to another, make requests and remap back to the original vendor’s response format. In this way, subscribing systems obtain the information they require with little reconfiguration, legacy vendor dependencies can be decoupled as required, and data lineage can be traced through the enterprise.
INSTRUMENT MATCHING (ONBOARDING)
To prevent the creation of duplicate instruments (for example when sourcing data from two different providers, with different codes and identifiers), the system runs a matching process when a new instrument is created. If the item is not found the system adds the new item and runs standard on-boarding workflows. If it is found then any new data attached to the item is merged with the existing item. If there is some ambiguity then an exception is raised so that a data manager can investigate and resolve the issue.