The LINK Mapper application enables you to create and modify
LINKMED® Mapper interface templates. These Mapper
templates insert or extract ADT/Order information from HL7
message that had been configured in the template and converts
them to appropriate format that can be inserted to your
system database. For example the Inbound Mapper is configured
to convert HL7 to User delimiters on the Inbound interface
and converts study reports to HL7 messages on the Outbound
interface. LINKMED® IDK is shipped with several
Mapper interface templates that are pre-configured for different
HIS or EMR systems, additional HL7 segments or fields can
be added or modified using the LINKMED® Message Mapper
application
- How the LINKMED® Message Mapper defines HL7
Interface
There are two types of Mapper templates being used in LINKMED®
interface:
- Uni-directional interface (Mapper Inbound
Tab) as in Result or Billing Mapper, uses one side of
Input and Output features
- Bi-Directional Interface (Inbound and
Outbound Tab) as in matching ADT/Order with study reports,
uses both side of Input and Output features (HL7--->Other
formats and Other formats-----> HL7)
- Inbound Interface Data Flow
- HL7 message stream sends from HIS/EMR systems is
received by LINKMED® HL7 TCP/IP Receiver . The
HL7 message is created and put in the LINKMED®
Inbound interface folder (OrderR). The Mapper interface
template Inbound Input is pointing to this directory
folder (Interface input file format=HL7) where messages
are processed by the LINKMED® Interface Engine
to other format specified in the Mapper Interface Template.
Note: The LINKMED® HL7 TCP/IP
Receiver Mapper-Based uses this directory but does not
create HL7 message from stream, The Receiver parses
HL7 messages directly into LINKMED® intermediate
Interface database or output parsed messages to output
directory
- The interface Inbound output directory folder (OrderS)
on the Mapper is where data extracted and converted
to your system format from HL7 messages are output to
(when needed), direct database query to LINKMED®
Interface Intermediate database can also be configured
when creating your interface template
- The LINKMED® Bi-directional interface makes
use of an intermediate database. Available DB to choose
from are: DBF, MySQL or other SQL
Access to LINKMED® MySQL intermediate database
is from LINKMED® Select client application. Access
to LINKMED® DBF intermediate database is from
LINKSelect client. Both of the above database access applications
are included in the toolkit.
Note: This intermediate database can also
be accessed using SQL query, http query or ODBC compliant
applications
- Outbound Interface Data Flow
The LINKMED® Interface Engine processed
and reconciled study reports with previously received
ADT or Order messages by matching the study report with
Key Identifiers of ADT or Order message stored in its
intermediate database. If a match is found then HL7 message
(ORU or MDM) is created and sent back to the Ordering
system. If a match is not found the study report is sent
to LINKMED® Result Reconciliation Module for further
reconciliation process
The following are LINKMED® default Outbound HL7
interface workflow:
-
Lab results, Diagnostic study or Transcribed
reports received back from Vendors systems are reconciled
with Orders or ADT information's stored in the LINKMED®
interface intermediate database by matching report Key
Identifiers to ADT/Order Key Identifiers created when
the ADT or Order messages are received by LINKMED®
Interface Module.
-
HL7 result message (ORU), Documentation
(MDM) message or Billing message (DFT) is created if
all Unique key identifiers are matched.
-
Reports with unmatched Key Identifiers
are processed for later reconciliation with ADT or Order
sent later from the HIS or EMR OE systems.
- Study reports can be viewed and print from LINKMED® Select client (MySQL DB only)
-
HL7 messages are configured according
to client's specifications (down to HL7 field level).
- Accessing the Mapper Options Configuration Window
To Access the Mapper Options Configuration Window from LINKMED®
installed server or PC
..........................................................................................................................................................
| Home | Products
| Partners
| Contact |
News | Contact Us
|
|