MDM Virtualized Endpoint
If a FHIR Endpoint module is connected to a FHIR Storage (RDBMS) module which is MDM-enabled, it is possible to configure the FHIR Endpoint to be MDM Virtualized.
MDM virtualization attempts to create an endpoint that hides the complexity of the MDM implementation and the linked records, presenting a single unified view of the linked data. A simple example helps to explain this concept:
Suppose you have a FHIR repository with two patients (Patient/A and Patient/B) which are both linked to a golden record (Patient/G). You then have some Body Height Observations (LOINC code = 8302-2) in the repository, some of which are linked to the first patient and some of which are linked to the second.
In a standard non-virtualized endpoint, a search for Observation?code=http://loinc.org|8302
would return Observations referring to two separate patients. The onus is then on the client to determine that these patients are the same person.
In a virtualized endpoint, the subject element in each Observation is rewritten before being returned to the client so that it points to the golden record (Patient/G). This means that the client sees all data as belonging to a single Patient.
With MDM Virtualization enabled:
Observation?subject=Patient/A
would be automatically widened to be processed as 'Observation?subject=Patient/A,Patient/B,Patient/G'.Observation?_include=Observation:subject
) the patient is replaced with the golden record patient.The following diagram shows the architecture of the virtualized endpoint.
This setting is only possible when using a FHIR Storage (RDBMS) module.