MEDITECH Interface Manager

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to: navigation, search

Overview

Native client-side application used to configured and manage MEDITECH endpoint to send and receive information between MEDITECH and outside vendor (OV) systems.

MEDITECH MIS Interface Manager.jpg MEDITECH MIS Interface Manager Path Value Set Mapping.jpg

Components

  • Outbox Message Generator: Creates HL7 messages
  • Delivery Service: Communicates between MEDITECH & OV system
  • Inbox Message Filer: Takes pieces of HL7 message & files to MEDITECH applications
  • Background Job Daemon: Monitors all the background jobs on a background job client

Inbound MEDITECH Interface Components

Inbound MEDITECH Interface Components.jpg

Outbound MEDITECH Interface Components

Outbound MEDITECH Interface Components.jpg

FAQ

Q: How do I filter outbound results based on location?

A: Leveraging a toolbox parameter in the message generator dictionary, MEDITECH can filter the results by location through a lookup.

Q: How are child susceptibilities linked to the identified organizations in a HL7 microbiology result message?

A: OBR.26 is used to link the susceptibility procedures to the organisms. OBR.26.1 contains the Observation ID and OBR.26.2 contains the Observation Sub-ID. The combination of those two values uniquely identifies which organism the susceptibility procedure is linked to.

Q: What would prevent results from sending to the OV interface?

A: Check the LIS Lab Site configuration to ensure the outbound LAB/MIC/BBK/PTH Results to OV interface is linked to an LIS Labs Site as defined on page 3 of the LIS Lab Site Dictionary (Ancillary->Laboratory->Dictionaries->LIS A-L->Lab Site->Enter/Edit).

Q: What causes “Unable to open active socket” in MEDITECH interface manager?

A: This error is commonly associated with connectivity issues to the OV system. Ensure the OV system is set to listen on the IP/port defined and check for firewall rules that may be blocking connection on the IP/port. To troubleshoot, toggle the delivery service background job within Interface Manager.

Q: What does the following interface message indicate: “Messages stuck in a READING status in the message filer?”

A: This is a lock, caused by a user opening a patient file for the purposes of editing. The message filer or formatter will not process a transaction related to that file until the user closes the patient file. The intent of this functionality is to prevent overwriting of data and keep the events on a patient sequential.

Q: What is the patient matching criteria for an inbound ADT feed?

A: Name, MRN, Sex, and DOB are used and cannot be edited via any interface transaction, as this ensures Medical Record integrity on the patient

Q: How do I gain access to the MIS Interface Manager?

A: The menu/process needs to be added to the user profile. Within the Interface Manager Access dictionary, profiles can be created with different access levels based upon interface.

What is the ITI Suite?

A: The ITI suite are set of interfaces that facilitate the exchange of the CCD from vendor to vendor. They use the standard XDS.b profile which assists with registration, distribution, and access across EHR’s

What are the dependencies for Direct/CCD setup

A: This requires access to the Interface Manager Access Dictionary – specifically the “Send Unsolicited CCD” routine. “Create CCD Activity” must be set to “Yes.”

Q: What are the different statuses of interfaces within the MIS Interface Manager?

A:

  • Never-Ran: Interface job has never been turned on
  • Running: interface job is on & functioning
  • Halt-User: interface job was stopped by a user
  • Halt-Error: interface job has stopped due to an error

Q: Why are messages are stuck in a Queued Status within MIS Interface Manager?

A:

  • Ensure the delivery services is running.
  • Verify the message is valid.
  • Toggle interface off/on.

Q: How do I set data persistence within MIS Interface Manager?

A: “View Message Type Purge Delay” shows the number of days that the interface manager will hold a message before it purges. 7 days is the standard purge delay.

Q: What are the different statuses of messages within MIS Interface Manager?

A:

  • Inbound
    • Creating: The Interface Manager delivery services is creating the Interface Manager message.
    • Fail-Create: The Interface Manager delivery services failed to create the Interface Manager message.
    • Queued: The message is in the Interface Manager waiting to be read.
    • Reading: The application message filer is reading the message.
    • Fail-Read: The application message filer is reading the message.
    • Read-Warn: The application message filer filed the message, but encountered problems reading a portion of it
    • Cancelled: The user cancelled the message, the system will not deliver the message.
    • Hold: A user holds the message in the Interface Manager so that the message does not purge
    • Read: The message filed successfully to the application.
  • Outbound
    • Creating: The message generator is creating the message.
    • Fail-Create: The message generator failed to create the message.
    • Queued: The message is in the Interface Manager waiting to be sent.
    • Sending: The delivery service is sending the Interface Manager message to the outside application.
    • Fail-Send: The delivery service failed to send the Interface Manager message to the outside application. The delivery services does not automatically re-send the message.
    • Sent: The message is sent to the outside application.
    • Cancelled: The user cancelled the message. The system will not deliver the message
    • Hold: A user holds the message in the Interface Manager so that the message does not purge.

Q: What is the difference between an interface and a connection?

A: Connections are used to pass data between NPR (Non-Procedural Representation) and M-AT (MEDITECH Advanced Technology) applications – the two programming languages MEDITECH 6.x applications are written in. Interfaces reside with the NBR component of the MIS application and are used to pass data between NPR applications and OV systems. ==Q: Why do Image update messages from PACS yield the following FAIL-READ status: “Cannot find ITS Order for this Image Object ID”+ A: The order number returned in OBR.2 of the inbound message does not match the order number in OBR.2 of the original order. The OV must send the original order/accession in OBR.2

Q: My OV PACS systems support PDF launch to view PACs images. Does MEDITECH support receipt of the PDF?

A: The interface supports a URL pointer to reference the PDF file on a network server, sent in OBX.5 of the inbound message.