MDIX Products

MDIX’s Interoperability Solutions employ a model driven architecture. At the core of this approach is transforming one format to another, be they an industry standards, those of a healthcare vendor and HIEs, or you own internal formats. In addition to managing change, this model driven approach provides the following benefits:

Reusable and shareable

  • Reduces time and resources needed for your solution. FHIR, CDA, and V2 industry standard models are prebuilt and downloadable as open source. If you have built your own internal transformation models, they can be reused.

  • High quality. Software and artifacts that are used over and over have a higher quality than custom developed, bespoke software. Most transformation used in MDIX solutions models have been built and vetted by industry experts and the healthcare community.

Any transformation model works with any other transformation model

  • Implementing your solution is easier. As open source, transformation models are already developed and tested. Your problem may be reduced to implementing a transformation model for your internal format making solutions much simpler.

  • Implementing your solution is faster. Using prebuilt transformation models, much of your project is done before you start. In fact, if your solution requires the transformation of one industry format to another, your solution simply may be reduced to a configuration process.

  • Change is isolated. Since any transformation model works with any other transformation model, changes are isolated. You may not need to do anything other than configure a new model in your systems.

Open Source

MDIX uses open source MDMI software and content providing services for all aspects of MDMI processing including:

  • Map Development
  • MDMI services in the cloud
  • Operational service level support agreements

More information is available at GitHub

MDIX Transformation Model Workbench

MDIX Transformation Model Workbench is used to create and maintain any transformation model for any format. There are two components to the Workbench, the MDMI Map Editor and the MDIX Semantic Element Exchange Registry (SEER).

MDMI Map Editor

The Editor is the end-user application for creating and modifying transformation models, which we call maps, and offers these productivity capabilities.

Productivity for Model Developers.

  • Writing code is not required to develop a map. One only needs to understand the format and meaning of their data to develop a map.

  • The Editor can automatically create maps from external sources such as XML and UML models.

  • The only mapping done in an MDIX Transformation Model is to map the semantic concepts of your format to equivalent concepts in the SEER. The Editor is integrated with the SEER making finding the equivalent concept simple.

  • Generating computable files for MDIX Runtime Products is an automated process.

Productivity for other Team Members

  • Tools have been developed for generating reports automatically such as a gap analysis reports to show information missing in the transformation. This tooling allows customization for your own reports.

  • Testing and Debugging Tools. A testing capability is in the Editor the to verify the transformations created.

MDIX Semantic Element Exchange Repository (SEER)

The MDIX SEER is a cloud-based service that is the keystone of MDIX Transformation Model interoperability. Through the SEER, any MDIX map can interact with any other MDIX map developed by you or anyone else.

The MDIX SEER contains the business concepts exchanged in healthcare information. It embodies every clinical and administrative healthcare concept needed in industry standard exchange formats as well as other concepts. New content is easily added when new business concepts have been identified.


MDIX Purpose Built Runtime Products

MDIX offers three products addressing the major functions of message exchange, each optimized for its specific purpose. We understand that our interoperability products are a component of your solution, so we package them as software services employing industry standard interfaces. Our objective is to make integration into your systems a configuration exercise, not a software development project.


MDIX Transformation Service

The most basic service is the transformation of a source file into a target file. This capability is central to many use cases. Examples include

  • Receiving a file from a partner
  • An HIE receiving a document from a community member
  • Receiving a batch of files that updates a data warehouse or data lake
  • Sending a report to a regulatory agency
  • Migrating legacy data to a new system
  • and many more

The MDIX Transformation Service provides added value components to core transformation capabilities such as

  • Transformation model management
  • Configurable logging facilities
  • Interfaces to operational management dashboards
  • Source and target message validation
  • Interfaces to terminology services
  • and others

MDIX Transaction Service

Provides additional capabilities to the MDIX Transfromation Service, this provides query capabilities for handling dialogues between a sending organization and receiving organization. The product incorporates sending of a request and transforms the request into a form the receiver can process. Then using the MDIX Transformation Service it transforms the receiver response into the sender format.

Some example use cases are

  • An HL7 v2 message
  • A request by a healthcare provider to an insurance company for authorization
  • A request by an Account Care Organization for specific patient information
  • or even as a FHIR service to receive a FHIR query and send back a FHIR bundle

MDIX Healthcare Workflow Service

Delivering high quality, individually patient-centered treatment, sometimes referred to as Clinical Pathways, is the goal of every healthcare provider and their partners. It is impossible to achieve this goal without IT involvement. Healthcare IT cannot achieve this unless its implementations can interoperate with and integrate with others for

  • Connecting with new partners
  • Process improvement
  • Delivering new knowledge and technology at point of care
  • and even requirements from new business models

Interoperability solutions are a core capability for Healthcare IT to deliver on this goal.

MDIX stands alone delivering a dynamic, robust, high quality service as an interoperability solution for Clinical Pathways. As a founding member of the BPM+ Health Consortium, MDIX has demonstrated our ability to knit together, in a configurable fashion, different vendor and provider shareable solutions. Solutions that dynamically capture information based on a situation, incorporating rules of the situation then deliver information necessary to the next IT component based on the Clinical Pathway.

Our ability to dynamically discover situational information combined with our model driven approach to isolating and then implementing change makes us unique.