As my hospital converts to more corporate applications, my Meditech system has become more interoperable. The folks at Meditech have been incredibly supportive of a very complex systems agenda at our site.
A few weeks ago we went live with Siemens Soarian Financials and Scheduling, feeding our Meditech clinical systems. This two-year implementation was part of a corporate Soarian project and our hospital was the first site. The design is simple. Soarian Financials generates a “master” ADT feed to a “submerged” Meditech admissions module. Custom charge interfaces route from Meditech back to Soarian for billing purposes. Meditech has other submerged admission customers, but we’re told we are the first site using Soarian. Once Meditech receives demographic information from Soarian, the clinical dataflow remains the same.
This was an amazing effort by our local and corporate teams as well as our vendor partners — Meditech, Siemens and Accenture — who acted as the implementation consultants. This project, however, is only one example of how Meditech has helped make things work for me in my three year tenure as CIO of this site.
Because we are part of an integrated delivery system, our corporate direction has been towards more common systems, particularly in the fiscal and administrative spaces. For example, shortly after I arrived, we began a PeopleSoft implementation to replace Meditech’s HR, payroll, accounts payable, general ledger and materials management functions.
Ambulatory Interoperability and Medication Reconciliation
On the clinical side, our network has an internally developed integrated ambulatory medical record. Results and documents are sent from Meditech to be viewable in this EMR. We also have non-Meditech applications for the Emergency Department, Gastroenterology Unit and for medication reconciliation. In the latter case, we can pull medications from our enterprise medication repository to build a home medication list upon admission. For discharge, these meds can be reconciled with CPOE orders to create a new home med list. When the patient returns to their PCP, this medication list can be electronically reconciled in the enterprise ambulatory record.
Closed Loop Medication Administration
Our hospital implemented Meditech CPOE in the winter of 2006 to meet some quality metrics for our corporation. Meditech recommends installation of their eMAR product first, followed by CPOE. Because we had over 100 order sets in use and best practices, Meditech modified their eMAR module in ways we suggested. We delayed our eMAR project for the next release, but as a result, the CPOE, Pharmacy and eMAR functionality worked seamlessly.
Web Service Integration
Finally, the most challenging test of interoperability involves integrating Meditech allergies with our enterprise allergy repository (PEAR). In this model, an allergy recorded in Meditech is filed into PEAR, which can be viewed immediately in the native systems at other hospitals in our network, as well as our ambulatory record. Likewise, allergies filed in those systems are synched with the Meditech allergy record and displayed real time. This initiative is scheduled to be live early next year.
Not only has Meditech been patient with my significant changes, but also they have invested in making their system safely exchange critical data elements with other systems to support our evolving business model. Who says Meditech isn’t flexible?