Difference between revisions of "Interfaces"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
 
(19 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
'''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.
+
'''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.
 
  
 +
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.
 +
<startFeed />
 
==HL7 Resources==
 
==HL7 Resources==
 +
*[[HL7 FHIR]]
 +
*[[HL7 Editors]]
 +
*[http://www.hl7.org.au/HL7-Tools.htm HL7 Tools]
  
−
[[HL7 Editors]]
+
==Interface Engines==
−
 
+
*[http://wiki.galenhealthcare.com/ConnectR GE ConnectR]
−
[http://www.hl7.org.au/HL7-Tools.htm HL7 Tools]
 
−
 
 
−
== Interface Engines ==
 
−
*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://www.medical.siemens.com/webapp/wcs/stores/servlet/CategoryDisplay~q_catalogId~e_-1~a_categoryId~e_1018027~a_catTree~e_100010,1008631,1018465,1017717,1018015,1018027~a_langId~e_-1~a_storeId~e_10001.htm Siemens OPENLink]
+
*[http://healthcare.siemens.com/diagnostics-it/laboratory-information/siemens-openlink Siemens OPENLink]
−
*[http://www.neotool.com/products/neointegrate Neotool NeoIntegrate]
+
*[http://www.corepointhealth.com/products/corepoint-connections/corepoint-integration-engine Corepoint Integration Engine]
−
*[http://www.mdisolutions.com/products/md_link.php MDI Solutions MDLink]
+
*[http://www.orionhealth.com/solutions/packages/rhapsody/ Orion Health Rhapsody]
−
*[http://www.orionhealth.com/products/rhapsody/ Orion Health Rhapsody]
+
*[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.quovadx.com/body.cfm?id=232 Healthvision Cloverleaf]
+
*[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 eGate & Java CAPS]
+
*[http://www.sun.com/software/javaenterprisesystem/javacaps/index.jsp Sun Oracle Java CAPS (eGate)]
−
*[http://www.summit-healthcare.com/index.php?option=com_content&task=view&id=15&Itemid=202 Summit Integration Suite]
+
*[http://www.allscripts.com/content/dam/allscripts/documents/Tech-data-sheet-ProactiveAppMonitoring-SunriseeLinkTechSheet-Final.pdf Sunrise Elink - Allscripts]
−
*[http://www.eclipsys.com/solutions/eLink.asp Eclipsys Elink]
 
 
*[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://www.mirthcorp.com/products/mirth-connect Mirth Connect]
−
*[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.infinimed.com/Products_IMEDI.html InfiniMed, Inc. - IMEDI Integration Engine]
 
 
*[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]
 +
*[http://www.qvera.com/products/qie Qvera Interface Engine]
 +
*[http://www.nextgen.com/PDF/Interface_Server_Requirements.pdf NextGen Rosetta Interface Engine]
 +
*[http://healthcare.pilotfishtechnology.com/hl7-interface-engine.php PilotFish Interface Engine]
 +
*[http://www.summit-healthcare.com/products-healthcare-systems-integration-summit-connect.htm Summit Express Connect]
 +
*[http://www.iatric.com/EasyConnectJaguar Iatric EasyConnect Jaguar]
  
−
== Types of Interfaces ==
+
==Types of Interfaces==
 
*ADT Patient List  
 
*ADT Patient List  
 
*Charge  
 
*Charge  
Line 41: Line 42:
 
*Results
 
*Results
 
*Outbound Immunization
 
*Outbound Immunization
 +
*[[HIX (Health Insurance Exchange]]
 +
 +
 +
==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?
  
−
== Interface Engine Purchasing Considerations ==
+
<endFeed />
−
# '''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==
 
==Additional Resources==
−
[http://interfaces.galenhealthcare.com Allscripts Interface Developers Network]
+
*[http://interfaces.galenhealthcare.com Allscripts Interface Developers Network]
 +
<rss number=10 desc=off>http://interfaces.galenhealthcare.com/rss.php?mode=newposts</rss>

Latest revision as of 18:21, 28 November 2015

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

Types of Interfaces


Interface Engine Purchasing Considerations

  1. Installation - How easy is the engine to install? Is there a migration path from your existing interface engine?
  2. Usability - How intuitive is the user interface? Does it offer the capability of both GUI and code programming of interfaces?
  3. 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?
  4. Reliability - Does the engine have 24X7 operation? What are typical causes/estimates of downtime?
  5. Scalability - Is this engine built to support increases in throughput? What is the nominal number of interfaces it can support without performance degradation?
  6. Configurability - Does the interface engine allow for customization and extensions to be carried out by the customer or 3rd party resources, without vendor involvement?
  7. Target Market - Does the vendor have a primary focus on health care?
  8. 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>

Retrieved from "https://wiki.galenhealthcare.com/index.php?title=Interfaces&oldid=19938"