MEDITECH Integration, Interface and Interoperability Best Practices
The following tips and tricks offer best practice guidance to leverage and configure the capabilities of MEDITECH to deliver efficient, secure, and scalable integration.
Leverage the applications you have within your portfolio and buy a MEDITECH module if possible.
Following the principles outlined in application portfolio management best practices. Consolidate applications with duplicative functionality to eliminate redundant MEDITECH interfaces. Where possible, leverage the native capability of the EMR through use of modules.
Manage integration as MEDITECH EMR-Centric.
Map nomenclatures, dictionaries to MEDITECH as the standard instead of conforming to OV requirements. Request modifications from OV instead of performing within the enterprise interface engine.
Use a steering committee to ensure organizational individual departments don’t compromise enterprise standardization.
Avoid acquiescing to unique departmental requests and strictly follow integration and coding standards (HL7, LOINC, NDC, etc.).
Get an ADT feed into every possible system.
This facilitates EMPI and mitigates patient matching issues. ADT feeds are fairly straightforward to create and most OV systems support inbound feeds.
Consolidate OV systems.
For example, establish an Enterprise Image Repository with one feed to MEDITECH from different departments – Cardiology, Sleep Lab, Radiology, etc. – instead of having a direct feed to the imaging application for those departments. Avoid point-to-point interfaces and enforce a hub-and-spoke approach.
Be stringent with unsolicited results.
Require an order for reconciliation. When sending results to partners, document how the result displays in the OV system; Does it truncate? Is it an image or discrete result? This is especially important for microbiology results, where OV system’s may be limited in its capabilities to render.
Establish test patients in MEDITECH Test ring and OV LIVE ring.
Most OV don’t have test systems. Leverage test patients with realistic data and test case scenarios for verification and validation.
Leverage existing resources, starter kits, and IP within the community where possible.
Automate and build interfaces to allow for simple change and self-management.
Configure alerting and notifications. Leverage lookup tables where modifications are expected to avoid code changes. Provide inherent controls to map/filter, add and adjust interfaces as needed.
Share data with outside HIEs & public health organizations.
Assess and optimize your enterprise integration environment by downloading the Integration Architectural Design, Planning & Migration whitepaper