Difference between revisions of "Interfaces"
Jump to navigation
Jump to search
Anne.Danter (talk | contribs) m |
|||
| Line 10: | Line 10: | ||
*GE ConnectR | *GE ConnectR | ||
*[http://www.microsoft.com/biztalk/en/us/default.aspx Microsoft BizTalk Server] | *[http://www.microsoft.com/biztalk/en/us/default.aspx Microsoft BizTalk Server] | ||
| − | *[http:// | + | *[http://healthcare.siemens.com/diagnostics-it/laboratory-information/siemens-openlink Siemens OPENLink] |
| − | *[http://www. | + | *[http://www.corepointhealth.com/products/corepoint-connections/corepoint-integration-engine Corepoint Integration Engine] |
| − | *[http://www. | + | *[http://www.orionhealth.com/solutions/packages/rhapsody/ Orion Health Rhapsody] |
| − | *[http://www. | + | *[http://www.mdisolutions.com/products/md-link-integration-engine.html MD Link HL7 Integration & Interface Engine] |
*[http://www.intersystems.com/gensemble/?gclid=CKXn7N3m15gCFRYiagodtUjfdw Intersystems Ensemble] | *[http://www.intersystems.com/gensemble/?gclid=CKXn7N3m15gCFRYiagodtUjfdw Intersystems Ensemble] | ||
| − | *[http://www. | + | *[http://www.lawson.com/Solutions/Software/Healthcare-Integration-and-Information-Exchange/Cloverleaf-Integration-Engine/ Lawson Cloverleaf Integration Engine] |
*[http://www.mckesson.com/en_us/McKesson.com/Our%2BBusinesses/McKesson%2BProvider%2BTechnologies/Partnerships/Interface%2BEngines%252FData%2BMapping.html McKesson Pathways] | *[http://www.mckesson.com/en_us/McKesson.com/Our%2BBusinesses/McKesson%2BProvider%2BTechnologies/Partnerships/Interface%2BEngines%252FData%2BMapping.html McKesson Pathways] | ||
| − | *[http://www.sun.com/software/javaenterprisesystem/javacaps/index.jsp Sun | + | *[http://www.sun.com/software/javaenterprisesystem/javacaps/index.jsp Sun Oracle Java CAPS (eGate)] |
| − | *[http://www. | + | *[http://www.allscripts.com/content/dam/allscripts/documents/Tech-data-sheet-ProactiveAppMonitoring-SunriseeLinkTechSheet-Final.pdf Sunrise Elink - Allscripts] |
| − | |||
*[http://www.sybase.com/products/allproductsa-z/e-bizimpact Sybase E-Biz Impact] | *[http://www.sybase.com/products/allproductsa-z/e-bizimpact Sybase E-Biz Impact] | ||
*[http://ww2.pervasive.com/Integration/Solutions/Pages/Product_Solutions_Using_Data_Integrator_Home.aspx Pervasive Data Integrator] | *[http://ww2.pervasive.com/Integration/Solutions/Pages/Product_Solutions_Using_Data_Integrator_Home.aspx Pervasive Data Integrator] | ||
*[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. | + | *[http://www.mirthcorp.com/products/mirth-connect Mirth Connect] |
| − | |||
*[http://www.interfaceware.com/iguana.html Interfaceware Iguana] | *[http://www.interfaceware.com/iguana.html Interfaceware Iguana] | ||
| + | *[http://www.epic.com/software-connectivity.php Epic Bridges] | ||
==Types of Interfaces== | ==Types of Interfaces== | ||
Revision as of 19:51, 20 December 2012
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 Allscripts.
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
- Corepoint Integration Engine
- Orion Health Rhapsody
- MD Link HL7 Integration & Interface Engine
- Intersystems Ensemble
- Lawson Cloverleaf Integration Engine
- McKesson Pathways
- Sun Oracle Java CAPS (eGate)
- Sunrise Elink - Allscripts
- Sybase E-Biz Impact
- Pervasive Data Integrator
- HealthUnity HIN (Health Information Network) Product Suite
- Mirth Connect
- Interfaceware Iguana
- Epic Bridges
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?
Additional Resources
<rss number=10 desc=off>http://interfaces.galenhealthcare.com/rss.php?mode=newposts</rss>