Difference between revisions of "Interfaces"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
*[http://www.healthunity.com/products.aspx HealthUnity HIN (Health Information Network) Product Suite] | *[http://www.healthunity.com/products.aspx HealthUnity HIN (Health Information Network) Product Suite] | ||
*[http://www.MirthProject.org Mirth - The Open Source Integration Engine] | *[http://www.MirthProject.org Mirth - The Open Source Integration Engine] | ||
| + | *[http://www.infinimed.com InfiniMed, Inc. - IMEDI Integration Engine] | ||
== Types of Interfaces == | == Types of Interfaces == | ||
Revision as of 14:51, 9 July 2009
Interfaces are connections between two systems. ConnectR is the interface management and monitoring tool of choice for Allscripts implementations. An example of an interface would be the data flowing from a scheduling system into TouchWorks.
A single interface consists of both a source and target system. Each interface uses a map to define where to put incoming data on the way back out. Additionally translation tables can be used to map more than one value to a single output value.
Interface Engines
- GE ConnectR
- Microsoft BizTalk Server
- Siemens OPENLink
- Neotool NeoIntegrate
- MDI Solutions MDLink
- Orion Health Rhapsody
- Intersystems Ensemble
- Healthvision Cloverleaf
- McKesson Pathways
- Sun eGate & Java CAPS
- Summit Integration Suite
- Eclipsys Elink
- Sybase E-Biz Impact
- Pervasive Data Integrator
- HealthUnity HIN (Health Information Network) Product Suite
- Mirth - The Open Source Integration Engine
- InfiniMed, Inc. - IMEDI Integration Engine
Types of Interfaces
- ADT Patient List
- Charge
- Conversions
- Dictate
- Document (Inbound)
- Document (Outbound)
- Immunization
- Order
- Reg/Sched
- Results
- Outbound Immunization