LINKMED® Interface Tutorial: LINKMED® HL7 Interface Overview |
The LINKMED® HL7 TCP/IP Receiver and Transmitter
The LINKMED® TCP/IP HL7 Receiver is used to receive
HL7 message from the HIS or HL7 compliant systems.
The LINKMED® TCP/IP HL7 Transmitter is used to send
HL7 Result/Report and/or Billing Messages back to the HIS
or other HL7 compliant systems
The LINKMED® TCP/IP drivers can send and receive information in virtually any format over many TCP/IP protocols, effectively bridging other systems with the LINKMED® Interface environment.
-
Inbound Interface
HIS sends HL7 messages----------> LINKMED® HL7 TCP/IP Receiver-----------> LINKMED® IE-------->HL7 converts to other format
-
Outbound Interface
Study's result ----------> LINKMED® IE creates HL7 result message-----------> LINKMED® HL7 TCP/IP Transmitter sends HL7 result message-------->HIS or EMR systems
2. LINKMED® Dynamic Message Mapper:
The LINKMED® Dynamic message Mapper application is used to create Interface Template or adjust pre-configured Interface Template. The LINKMED® Interface Engine reads instruction in the Interface Template to translate data from one format to another.
3. Inbound Interface:
The LINKMED® Interface Engine processed
filtered and reformatted HL7 and non-HL7 format to other
file format by reading the Interface template created
by user. The following are LINKMED® default Inbound
HL7 interface workflows:
-
HIS or EMR systems send HL7 messages to LINKMED® interface.
-
LINKMED® HL7 TCP/IP Receiver receives and send HL7 message acknowledgements.
-
LINKMED® Receiver processes HL7 messages.
-
Parsed HL7 messages are imported to vendors applications or systems.
-
Inbound demographics data are also stored in LINKMED® intermediate database (bi-directional interface).
-
Assigned patient unique key identifiers for orders so result can be reconciled to correct orders.
-
Accepting HL7 ADT updates to HL7 orders (ORM) automatically
-
Native supports for ADT patient merged messages on both patient ID or patient Account numbers
4. Outbound Interface:
The LINKMED® Interface Engine processed and
reconciled study reports with ADT or Orders, then creates
HL7 result (ORU) or Documentation (MDM) messages and sends
that back to the HIS or EMR systems.
The following are LINKMED® default Outbound HL7
interface workflows:
-
Lab results, Diagnostic study or Transcribed reports received back from Vendors systems are reconciled with orders or ADT information's stored in LINKMED® intermediate database.
-
HL7 result message (ORU)or Documentation (MDM) message is created if all records unique key identifiers are matched.
-
Reports with unmatched unique key identifiers are processed and can be reconciled with ADT or Order sends later from the HIS or EMR OE systems.
-
Reports can be viewed and print from LINKMED® WebSelect client application.
-
HL7 result (ORU) or Documentation (MDM) messages are created per client's system specifications down to HL7 field level.
5. Implementing the interface:
LINKMED® IE provides software and applications needed to create and implement your interface. You can create both test interface and production interface environments within the same LINKMED® Interface server . The following are LINKMED® default interface trigering events:
-
HIS or EMR Systems send HL7 ADT /Order message to LINKMED® Interface.
-
Vendors creating Mapper " Interface Template" according to their application or system requirements.
-
Vendors activates the LINKMED® Scheduler module to trigger the interface
Note:
LINKMED®
interface
engine
can
be executed from
any
system
command
prompt
to trigger
the
interface.
|
System requirements:
|
Minimum
|
Recommended
|
| CPU | Pentium Class 1.0 GHZ | Pentium Dual/Quad Core 2.0 GHZ or higher |
| Storage Space | 100 GB Hard Drive | > 200 GB Hard Drive |
| Operating System | Windows® 2000/XP/7 Pro | Windows® Server 2000/2003/2008 |
| Random Access Memory | 1 GB of RAM | 4 GB of RAM |
| Local Area Network | 100/1000 | 100/1000 |
| Optional IIS* installed | IIS 6 | IIS 6 or above |
| * IIS=Microsoft® Internet Information Services | ||
|
|
