MEDI TECH-endorsed solution for HL7 data exchange Presented by: - PowerPoint PPT Presentation

MEDI TECH-endorsed solution for HL7 data exchange

Presented by: Dave Akina , Account Representative Brittani W hite , Account Representative

About Forward Advantage Data Express Overview Results-Out Orders-In Monitoring and Alerting Capabilities Review FAQs

Founded in 1992 Communication Director platform released 1994 Data Express product released 2007 Serving over 1,000 MEDITECH hospitals Locations: ◦ Corporate Office - Fresno, CA ◦ Braintree, MA ◦ Westborough, MA

Communication Director Bed Stat im-one CHIEF Find-It Migration Integration Services for MEDITECH 6.x www.forwardadvantage.com

MEDITECH-endorsed solution Part of the MEDITECH interoperability strategy Meaningful Use Stage 1 (2011-2012) Certified Data Express delivers MEDITECH Results to physician EHRs Data Express receives physician Orders from EHRs and delivers them to MEDITECH

Issues: ◦ Too many other projects ◦ Not enough staff ◦ Lack of tools/training Resolution: ◦ Proper tools ◦ Trained staff

Results-Out

Data Express Results-Out Hospital / Health System Hospital / Health System Physician Offices Physician Offices Lab Results Lab Results HL7 Results HL7 Results I TS Results I TS Results And many other And many other EHRs EHRs

Data Express Results-Out The “Data Express Interface Bundle” must be purchased directly from MEDITECH These interfaces include: ◦ LAB ◦ MIC ◦ BBK ◦ PATH ◦ OE/DEPT (MAGIC only) ◦ RAD (MAGIC only) ◦ ITS (C/S & 6.x)

Data Express Results-Out Data Express Results-Out receives HL7 messages DIRECTLY from MEDITECH Data Express Results-Out eMaps provide a one- to-many solution – no per-connection fees Data Express Results-Out eMaps are built and maintained by Forward Advantage

Orders-In

Data Express Orders-I n Hospital / Health System Hospital / Health System Physician Offices Physician Offices Lab Orders Lab Orders Orders Orders I TS Orders I TS Orders And many other And many other EHRs EHRs

Data Express Orders-I n Order Entry Hold Queue Orders Sm art Search Positive Pre Attach to Patient Match Registration Medical Record Hold Queue

Data Express Orders-I n Send HL7 messages directly to MEDITECH eMaps are built and maintained by Forward Advantage The “Data Express Orders Interface” must be purchased directly from MEDITECH This interface includes: ◦ LAB ◦ MIC ◦ BBK ◦ PATH ◦ OE/DEPT (MAGIC only) ◦ RAD (MAGIC only) ◦ ITS (C/S & 6.x)

Monitoring and Alerting Capabilities

System Activity Monitor (SAM) ◦ SAM is an audit log for all the messages sent through Data Express (Results-Out and Orders-In) ◦ In SAM you can:  View Delivery Status of messages  Re-deliver Failed messages ◦ SAM is also used with Communication Director

SmartAlert ◦ SmartAlert automatically emails notifications when Data Express requires your attention ◦ User can set up which alerts to receive ◦ Alert Examples:  Services Stop  Preset number of messages fail ◦ SmartAlert for Communication Director is available for purchase

Takeaways

MEDITECH-endorsed solution Part of the MEDITECH interoperability strategy Meaningful Use Stage 1 (2011-2012) Certified Delivers MEDITECH Results to physician EHRs Receives physician Orders from EHRs and delivers them to MEDITECH Monitoring and Alerting Capabilities

Frequently Asked Questions

Q. What interfaces are included in the bundle? LAB A. MIC BBK PATH OE/DEPT (MAGIC) RAD (MAGIC) ITS (C/S & 6.x)

Q. Can’t I use my existing Interface Engine for this integration? You certainly can use your existing interface engine for A. exchanging Results and Orders with physician EHRs. Data Express may be a more suitable solution for you, however, if 1) You don’t have staff to write the interfaces, or 2) Your staff doesn’t have time to write the interfaces, or 3) You are looking for a proven solution for integrating MEDITECH with your physician EHRs.

Q. How do I know if I need 1, 2 or more eMaps? eMaps are built based on the specification of the EHRs. A. The number of eMaps you will need depends on the number of different EHR systems in your community. Typically speaking, there is a 1:1 ratio between the number of eMaps and the number of EHR vendors. There are scenarios where more than one eMap is required for the same vendor, such as 1) the physician has customized their EHR system, resulting in a change to the standard EHR spec, or 2) the physician’s specialty requires a personalized specification.

Q. Do you have a product that exchanges data with an HIE or RHIO? Data Express can exchange data with an HIE or RHIO A. provided that system meets two requirements: 1. It is able to exchange HL7 2. It has a specification document If the HIE or RHIO (or for that matter, any EHR, nursing home system, etc.) can meet these requirements, we can most likely exchange data with them. For any system, we will take a look at the specification document we receive from you to confirm the ability.

Q. How does Data Express handle the EHR’s Order Number? The order processing for Data Express is handled by A. MEDITECH. When Data Express receives an order from the EHR with the EHR’s Order Number (or Other Vendor Order Number), it passes that Number with the Order to MEDITECH. MEDITECH will perform their standard order processing (including the Smart Search looking for a Positive Patient Match and Pre-Reg if necessary). Once the Order is completed, MEDITECH will send the Solicited Result with the original EHR Order Number to Data Express. Data Express delivers this Result and OV Order Number to the EHR for reconciliation in its system.

Q. How does Data Express handle Orders that don’t require the patient to show up at the hospital? This is also part of the Order processing handled by A. MEDITECH. If the Order does not require patient presentation, the Order will bypass the Hold Queue and be sent directly to the appropriate department to be fulfilled.

For additional information, contact us at: DataExpress@forwardadvantage.com THANK YOU!