Omni-Patient Server Overview

The Omni-Patient Server is a vital component of the Omni-Patient product, implemented on the iWay Service Manager platform.

The primary roles of the Omni-Patient Server are as follows:

• Process Omni Interface Documents (OIDs) and persist Source Instance records to the Enterprise Mastered Information Repository (EMIR).
• Communicate with iWay Data Quality Suite to Cleanse, Match, and Merge mastered Subjects.
• Process and persist the Golden Record for each mastered Subject in the EMIR.
• Provide a data access layer from the EMIR to outside consumers, such as Omni Patient Management Central (OPMC).

The Omni-Patient Server accomplishes these tasks through three primary components:

• Omni Interface Document (OID) Handler

  Source data is communicated to Omni-Patient through the use of Omni Interface Documents (OIDs). The OID Handler processes these XML documents, communicates with iWay Data Quality Suite, and persists updates to the EMIR.

• Remediation Request Handler

  The Remediation Request Handler manages the interaction between the Advanced Remediation tools in Omni-Patient Management Central, and components of the Omni-Patient Server. It supports both synchronous and asynchronous interaction with Advanced Remediation.

• OmniServices Layer

  The OmniServices Layer exposes the Omni-Patient data model through a RESTful web service interface. The Primary consumer of the OmniServices Layer at the present time is Omni-Patient Management Central, the primary user interface of Omni-Patient. The 360 Viewer, Data Dictionary, and Advanced Remediation functions are all expected to be supported to some degree by the OmniServices Layer.