Difference between revisions of "Category:ConnectR"
John.Buckley (talk | contribs) (Created page with "== Overview == GE's ConnectR interface engine which facilitates the transfer of information to different healthcare systems via HL7. Many of the pages on the Galen wiki will ...") |
John.Buckley (talk | contribs) |
||
Line 49: | Line 49: | ||
* [[AE-EHR Interfaced Result-Driven Order Reconciliation]] | * [[AE-EHR Interfaced Result-Driven Order Reconciliation]] | ||
* [http://interfaces.galenhealthcare.com Allscripts Interface Developers Network] | * [http://interfaces.galenhealthcare.com Allscripts Interface Developers Network] | ||
− | |||
* [[Categorized Common ConnectR Errors]] | * [[Categorized Common ConnectR Errors]] | ||
* [[Clustering ConnectR]] | * [[Clustering ConnectR]] |
Revision as of 14:08, 16 November 2012
Overview
GE's ConnectR interface engine which facilitates the transfer of information to different healthcare systems via HL7. Many of the pages on the Galen wiki will refer to its use in relation to transferring information into and out of the Allscripts Enterprise EHR.
History with Allscripts
ConnectR was developed by IDX before IDX was acquired by GE in 2005. Allscripts purchased a division of IDX in 2001, called ChannelHealth. Along with the acquisition, Allscripts gained the rights to use ConnectR (and the IDX/GE Web Framework) effectively into perpetuity (as long as the two companies have common clients, though your organization does not need to be a client of both). The ConnectR interface engine is used as the standard interface engine by Allscripts to facilitate communication between other healthcare systems, such as Practice Management Systems, Radiology, Lab, Transcription, etc.
Versions
Most Allscripts client run either version 4.5 or 4.6 of ConnectR, specifically 4.5 build 133 and 4.6.2.267 (aka 4.6.2). 4.5 offers a Windows client, whose Desktop and Start Menu shortcut is IDXConnectR 4.0. This leads to some confusion of which version of ConnectR is being run - it's 4.5, despite the naming of the icon.
Version 4.5
- Clients
- Windows - The windows client is the primary method for accessing this version of ConnectR. It supports the Allscripts-developed CMS Bridge Tool.
- Web - The web client is not used by many in 4.5. 4.5 was the first version in which a Web client was available and certain desireable features had not yet been ported from the Windows client.
Version 4.6.0
This release was not rolled out to many clients. One limitation was the inability to Bridge patient matching errors, which is was a show-stopper for most groups.
Version 4.6.2
- Clients - 4.6.2 can only be accessed through the web client.
- Bridge - Bridge is supported in 4.6.2. As of January 2009, Allscripts is actively developing Bridge, adding new features and fixing any issues found in the product.
- Hot fixes - Update 15 is the latest hot fix from GE.
Upgrading from 4.5 to 4.6.2
This is a hot topic. 4.6.2 offers some features not found in 4.5, as well as some bug fixes. New issues have been found in 4.6.2, making it sometimes challenging to upgrade.
What's new in 4.6.2:
- The Web Client is fully functional.
- Script errors are now displayed in the Message Log and Error Worklist
- Script errors are now fatal errors that prevent data from being sent, rather than being silently ignored
- Bridge is supported in the web client
- A number of bug fixes have been made since 4.5.133
Upgrade Path With careful planning and thorough testing, you can mitigate most issues that you may encounter in an upgrade. The areas to focus on include:
- Have a test ConnectR environment. If your group does not have one, get one installed and move all of your test interfaces over.
- Test all of your interfaces as thoroughly as possible.
- Ideally, this means you will have all interfaces have the same volume of data, and types of data, flow through your test ConnectR environment.
- At a minimum, this means you will have tested all interfaces, with a few dozen messages
- What to check for:
- Validate that there are no Application and Non-Application errors
- Grid the source and target messages to ensure that they appear as they would in production
- Validate that the data shows correctly in the receiving system. This is Allscripts for inbound messages (Registration, Scheduling, Results, Documents, etc) and your other systems for outbound messages (Charge, Order, Dictate, etc).
- Manually test every Script used by an interface in your production ConnectR environment
- Upgrade production on a Friday and test all weekend. Monitor the errors all weekend.
Resources
- Ack Messages
- AE-EHR Interfaced Result-Driven Order Reconciliation
- Allscripts Interface Developers Network
- Categorized Common ConnectR Errors
- Clustering ConnectR
- ConnectR Audit
- ConnectR Connection Codes And Descriptions
- ConnectR Customized Error Bridge Approach
- ConnectR Error List Utility
- ConnectR Interface Current State
- ConnectR Interface Troubleshooting
- ConnectR Jobs
- ConnectR Move to Live Checklist
- ConnectR on IE7, IE8 and greater
- ConnectR Performance
- ConnectR Pre Proc Script
- ConnectR Script - Return More Than One Value
- ConnectR Superset Source
- ConnectR Test, Development and Production (Live) Environment Best Practices
- Developing Bridge-compatible stored procedures
- FAQs
- GE ConnectR Script Definition
- GE ConnectR Troubleshooting
- Incorrect syntax near '='
- Interface-Driven Tasking
- Interfaced Document Encounter Matching
- Importing an Outbound Interface
- Import/Export Interfaces
- Item Dictionary Synchronization
- Loading Message Definitions
- Message Definition Load From DB
- Outbound Interface Filtering
- Setup of a new Test Environment which utilizes Pass-Thrus from Production
- ConnectR Install Issues
- Valid values for "Form" parameters in inbound interface mapping
Pages in category "ConnectR"
The following 46 pages are in this category, out of 46 total.
-
- -180: Activity does not belong to Patient. Please Submit a Webfirst Ticket.
- -233: The Performed date/time sent is in the future. Please have the sender fix and resend the message
- -261: Clinical and Result Date/Time must be defined.
- -4000006: Corrupt Resultable Item Dictionary
- -603: Unable to identify QO Classification DE from alternate identifier
- -606: Error: Unable to file result. More than one result activity header per order.
- -607: Multiple alternate identifiers found for orderable item
C
- Clustering ConnectR
- ConnectR Audit
- ConnectR Connection Codes And Descriptions
- ConnectR Customized Error Bridge Approach
- ConnectR Error List Utility
- ConnectR Install Issues
- ConnectR Interface Current State
- ConnectR Interface Errors
- ConnectR Interface Troubleshooting
- ConnectR Move to Live Checklist
- ConnectR on IE7, IE8 and greater
- ConnectR Pre Proc Script
- ConnectR Script - Return More Than One Value
- ConnectR System Service does not show
- ConnectR Test, Development and Production (Live) Environment Best Practices
- ConnectR VBScript Error
- COUNT field incorrect
I
S
Media in category "ConnectR"
The following 23 files are in this category, out of 23 total.
- ACS ImpSetOrderResultWsync2.gif 903 × 511; 25 KB
- ACS ImpSetOrderResultWsync3.gif 898 × 731; 26 KB
- ACS ImpSetOrderResultWsync4.gif 900 × 567; 25 KB
- ConnectR Debug Documentation Img2.jpg 717 × 443; 131 KB
- ConnectR Debug Documentation Img5.jpg 857 × 465; 121 KB
- ConnectR Debug Documentation Img6.jpg 935 × 524; 129 KB
- ConnectR Debug Documentation Img7.jpg 1,009 × 692; 104 KB
- ConnectR Debug Documentation Img8.jpg 794 × 483; 136 KB
- ConnectR in IE7.jpg 545 × 462; 40 KB
- ConnectR Message Definition Load From.jpg 1,416 × 815; 226 KB
- ConnectR Server Definition2.jpg 768 × 600; 92 KB
- ConnectR System Service Missing.jpg 1,003 × 673; 200 KB
- ConnectR System Service Missing2.jpg 658 × 753; 166 KB
- ConnectR System Service Missing3.jpg 657 × 571; 114 KB
- ConnectR VBScript Error.jpg 585 × 127; 15 KB
- Connectrroot1.png 991 × 698; 24 KB
- Cxr1.jpg 867 × 437; 163 KB
- Cxr2.jpg 798 × 606; 145 KB
- Cxr4.jpg 837 × 251; 32 KB
- Cxr5.jpg 455 × 129; 16 KB
- CxRPreProcScript.jpg 893 × 572; 150 KB
- CxRPreProcScript2.jpg 1,010 × 650; 257 KB
- Qoclassqo.png 555 × 257; 12 KB