https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Ray.Lape&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T08:40:49ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=Patient_Matching_Criteria&diff=18946Patient Matching Criteria2015-01-07T15:46:38Z<p>Ray.Lape: /* Extended Matching Logic */</p>
<hr />
<div>__TOC__<br />
=Patient Matching Criteria=<br />
<br />
==Description==<br />
The [[TouchWorks]] interface uses specific criteria in order to complete a patient match. This article explains the necessary requirements and is valid as of TouchWorks v11.1. The standard criteria is available in all versions of [[TouchWorks]]. In v11.1 there are new, "extended" matching criteria, which are optional and must be setup in each of your interface(s) that should use the extended matching criteria. Please see the "Extended Matching Criteria" below for more information.<br />
<br />
In order to match properly, [[TouchWorks]] relies on the Last name, First name and two of the following three items: MRN, DOB, SSN. A more detailed description is shown below.<br />
<br />
Regardless of matching used (Standard or Extended v11.1+ Matching), a single match is required. Let's say you are using the Extended Matching available in v11.1+ and there are two patients with the same Full Name and DOB, a match will not occur.<br />
<br />
==Fields==<br />
<br />
===Last Name===<br />
This element is required and [[TouchWorks]] uses the first 5 letters of the last name for matching purposes.<br />
<br />
===First Name===<br />
This element is required and [[TouchWorks]] uses the first 3 letters of the first name for matching purposes.<br />
<br />
===Medical Record Number===<br />
Also known as the MRN, this field is optional, but two of the three optional fields must be present to match. If MRN is used, the Organization must match as well (applicable for multi-org only). See Matching Logic below.<br />
<br />
===Date of Birth===<br />
Also known as DOB, this field is optional, but two of the three optional fields must be present to match. See Matching Logic below.<br />
<br />
===Social Security Number===<br />
Also known as SSN, this field is optional, but two of the three optional fields must be present to match. See Matching Logic below.<br />
<br />
===Insurance / PBM ===<br />
This is part of Test #4, used only for patient registrations (FilePatient_CMS). The fields used are the Card Holder Number (for the PBM) and Relationship to Card Holder. These are FilePatient_CMS fields MemberNumber (126) and PatientRelToCardholderCode (127).<br />
<br />
<br><br><br />
<br />
==Standard Matching Logic==<br />
*Test #0.1<br />
**XID Matching: XID is used by some clients, primarily IDX FlowCast / GE Centricity Business Solutions. It's a completely unique identifier, that never changes (unlike MRN can). XID matching trumps all other matching.<br />
*Test #0.2: MRN and Org - File Patient Only<br />
** If a patient is being updated, it only needs to find the record (in the same org) based on MRN.<br />
*Test #1: Name, MRN, DOB and Org<br />
*Test #2: Name, MRN, SSN and Org<br />
*Test #3: Name, DOB, SSN<br />
*Test #4: Name, DOB, Insurance / PBM Match<br />
<br />
==Extended Matching Logic==<br />
This extended matching was added in [[TouchWorks]] v11.1. There are six new optional Tests/Scenarios for matching. These require additional setup in each interface that plans to utilize the new matching.<br />
<br />
If not specified – Option 1 is assumed and standard patient matching logic occurs.<br />
<br />
If specified – At least one entry from option 1, 2, 3, 4, 13, 14 or 16 MUST be specified<br />
as the primary matching logic. If not, a -163 error will be returned to ConnectR.<br />
<br />
Options:<br />
* Option #1: Perform Standard Matching<br />
* Option #2: Perform Standard Matching, replacing MRN matching with Other Number matching<br />
* Option #3: Perform Standard Matching, replacing MRN matching with Other Number 2 matching<br />
* Option #4: Only perform XID matching - all other matching is ignored.<br />
<br />
* Option #5: Name, DOB, Driver License <br />
* Option #6: Name, DOB, Phone Number<br />
<br />
* Option #7: Name, DOB, Address Line 1 <br />
* Option #8: Name, DOB, Mothers Maiden Name<br />
* Option #9: Full Name (all characters of first and last names), DOB, Sex<br />
* Option #10: Full Name (all characters of first and last names), DOB<br />
* Option #11: Name, Other / Other 2, and SSN / DOB (11.1.7)<br />
** Off-cycle addition to the EHR. <br />
**Used with EMPI solutions. Used for demographics (ADT) matching only, across shared organizations. For example, patient Jane Smith (Other/EMPI = 1234) in Org A could have a new registration in Org B with Other/EMPI as 1234 and match to create a single chart (assuming either DOB or SSN match as well as Name and Other/2).<br />
* Option #12: Full Last Name, Date of Birth, Sex, and MRN or Other Number (11.1.7)<br />
* Option #13: MRN, Organization, Name, and Date of Birth or SSN (11.2.2)<br />
* Option #14: MasterChartID, OrgSharingDE, Name, and Date of Birth or MasterChartID, OrgSharingDE, Name, and SSN or Name, Date of Birth and SSN (11.4.0)<br />
* Option #15: MasterChartID, OrgSharingDE, Full Last Name, Date of Birth, and Sex (11.4.0)<br />
* Option #16: MasterChartID only (11.4.0)<br />
**MasterChartID is a new identifier that is unique to the Organization sharing pool. <br />
<br />
<br />
<br />
Implementation:<br />
* There is a new parameter to most inbound interfaces, called @MatchLogic<br />
** This is a pipe-delimited list of the options. For example, '1|5|7|' if you were aiming to perform standard matching, Name/DOB/Driver's License and Name/DOB/Address Line 1 matching.<br />
** You must also provide the appropriate fields that you need (Phone Number, Driver's License, etc) - these are found immediately below the @MatchLogic parameter in stored procedures other than FilePatient_CMS. In FilePatient_CMS these fields already existed higher up in the parameter list.<br />
* Phone Number matching<br />
** This is Home Phone in File Patient, and the specified Phone in other File routines<br />
** In file patient, Home Phone, must be entered in through fields 34-46, @o3x4HomePhoneArea, @o3x4HomePhoneExchange, @o3x4HomePhoneLast4 (@PatientFullHomePhone not an option as of v11.1.4).<br />
<br />
==Other Considerations==<br />
<br />
*In shared multi-org environments where there can be multiple practice management systems, the MRN may not be available as matching criteria because the patient could exist in mulitple orgs with different MRN's. This becomes a problem if SSN is not available. Some patients refuse to give out their SSN at registration, and some PM systems only store the last 4 digits.<br />
The use of an [[Empi]] can solve this problem by linking a patient that exists in multiple systems to a single MRN which becomes the primary identifier in the EHR.<br />
*In V11 GetPatientMatch will not match on Demographics unless you have an Org Sharing Pool linked to your organization. <br />
== Merged and Deactivated Patients ==<br />
<br />
Merged: Matching will not occur on patients who have been merged "from". If the Patient Merge Tool (aka CMS Patient Merge Tool) has been used to merge two patients, the patient that was Deactivated will not be considered for matching. These are patients that cannot be seen in the Patient Lookup screen, even when the Inactive check box has been checked.<br />
<br />
Deactivated: Patients that haven't been merged from, but have been deactivated in the Practice Management System, will be considered during matching; however, if they are found as the match, they will not be allowed to match. You will see a "-103 Patient is inactive" error.<br />
<br />
==Patient Matching Logic Spreadsheet==<br />
[[Media:AHS Patient Matching Logic.xls|Here]] is another representation of the information in this Wiki article. Patient Matching in [[TouchWorks]] is often times confusing and the hope is a different view into the logic may help make it more clear.</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Patient_Matching_Criteria&diff=18945Patient Matching Criteria2015-01-07T15:35:32Z<p>Ray.Lape: </p>
<hr />
<div>__TOC__<br />
=Patient Matching Criteria=<br />
<br />
==Description==<br />
The [[TouchWorks]] interface uses specific criteria in order to complete a patient match. This article explains the necessary requirements and is valid as of TouchWorks v11.1. The standard criteria is available in all versions of [[TouchWorks]]. In v11.1 there are new, "extended" matching criteria, which are optional and must be setup in each of your interface(s) that should use the extended matching criteria. Please see the "Extended Matching Criteria" below for more information.<br />
<br />
In order to match properly, [[TouchWorks]] relies on the Last name, First name and two of the following three items: MRN, DOB, SSN. A more detailed description is shown below.<br />
<br />
Regardless of matching used (Standard or Extended v11.1+ Matching), a single match is required. Let's say you are using the Extended Matching available in v11.1+ and there are two patients with the same Full Name and DOB, a match will not occur.<br />
<br />
==Fields==<br />
<br />
===Last Name===<br />
This element is required and [[TouchWorks]] uses the first 5 letters of the last name for matching purposes.<br />
<br />
===First Name===<br />
This element is required and [[TouchWorks]] uses the first 3 letters of the first name for matching purposes.<br />
<br />
===Medical Record Number===<br />
Also known as the MRN, this field is optional, but two of the three optional fields must be present to match. If MRN is used, the Organization must match as well (applicable for multi-org only). See Matching Logic below.<br />
<br />
===Date of Birth===<br />
Also known as DOB, this field is optional, but two of the three optional fields must be present to match. See Matching Logic below.<br />
<br />
===Social Security Number===<br />
Also known as SSN, this field is optional, but two of the three optional fields must be present to match. See Matching Logic below.<br />
<br />
===Insurance / PBM ===<br />
This is part of Test #4, used only for patient registrations (FilePatient_CMS). The fields used are the Card Holder Number (for the PBM) and Relationship to Card Holder. These are FilePatient_CMS fields MemberNumber (126) and PatientRelToCardholderCode (127).<br />
<br />
<br><br><br />
<br />
==Standard Matching Logic==<br />
*Test #0.1<br />
**XID Matching: XID is used by some clients, primarily IDX FlowCast / GE Centricity Business Solutions. It's a completely unique identifier, that never changes (unlike MRN can). XID matching trumps all other matching.<br />
*Test #0.2: MRN and Org - File Patient Only<br />
** If a patient is being updated, it only needs to find the record (in the same org) based on MRN.<br />
*Test #1: Name, MRN, DOB and Org<br />
*Test #2: Name, MRN, SSN and Org<br />
*Test #3: Name, DOB, SSN<br />
*Test #4: Name, DOB, Insurance / PBM Match<br />
<br />
==Extended Matching Logic==<br />
This extended matching was added in [[TouchWorks]] v11.1. There are six new optional Tests/Scenarios for matching. These require additional setup in each interface that plans to utilize the new matching.<br />
<br />
One of the first four options must be used. If not, a -163 error will be returned to ConnectR.<br />
<br />
Options:<br />
* Option #1: Perform Standard Matching<br />
* Option #2: Perform Standard Matching, replacing MRN matching with Other Number matching<br />
* Option #3: Perform Standard Matching, replacing MRN matching with Other Number 2 matching<br />
* Option #4: Only perform XID matching - all other matching is ignored.<br />
<br />
* Option #5: Name, DOB, Driver License <br />
* Option #6: Name, DOB, Phone Number<br />
<br />
* Option #7: Name, DOB, Address Line 1 <br />
* Option #8: Name, DOB, Mothers Maiden Name<br />
* Option #9: Full Name (all characters of first and last names), DOB, Sex<br />
** Getting in to matches of last resort - use with caution<br />
* Option #10: Full Name (all characters of first and last names), DOB<br />
* Option #11: Name, Other / Other 2, and SSN / DOB<br />
** Off-cycle addition to the EHR. <br />
**Used with EMPI solutions. Used for demographics (ADT) matching only, across shared organizations. For example, patient Jane Smith (Other/EMPI = 1234) in Org A could have a new registration in Org B with Other/EMPI as 1234 and match to create a single chart (assuming either DOB or SSN match as well as Name and Other/2).<br />
**Not currently available (as of v11.1.7), though this option may be offered on an as-needed basis.<br />
<br />
<br />
Implementation:<br />
* There is a new parameter to most inbound interfaces, called @MatchLogic<br />
** This is a pipe-delimited list of the options. For example, '1|5|7|' if you were aiming to perform standard matching, Name/DOB/Driver's License and Name/DOB/Address Line 1 matching.<br />
** You must also provide the appropriate fields that you need (Phone Number, Driver's License, etc) - these are found immediately below the @MatchLogic parameter in stored procedures other than FilePatient_CMS. In FilePatient_CMS these fields already existed higher up in the parameter list.<br />
* Phone Number matching<br />
** This is Home Phone in File Patient, and the specified Phone in other File routines<br />
** In file patient, Home Phone, must be entered in through fields 34-46, @o3x4HomePhoneArea, @o3x4HomePhoneExchange, @o3x4HomePhoneLast4 (@PatientFullHomePhone not an option as of v11.1.4).<br />
==Other Considerations==<br />
<br />
*In shared multi-org environments where there can be multiple practice management systems, the MRN may not be available as matching criteria because the patient could exist in mulitple orgs with different MRN's. This becomes a problem if SSN is not available. Some patients refuse to give out their SSN at registration, and some PM systems only store the last 4 digits.<br />
The use of an [[Empi]] can solve this problem by linking a patient that exists in multiple systems to a single MRN which becomes the primary identifier in the EHR.<br />
*In V11 GetPatientMatch will not match on Demographics unless you have an Org Sharing Pool linked to your organization. <br />
== Merged and Deactivated Patients ==<br />
<br />
Merged: Matching will not occur on patients who have been merged "from". If the Patient Merge Tool (aka CMS Patient Merge Tool) has been used to merge two patients, the patient that was Deactivated will not be considered for matching. These are patients that cannot be seen in the Patient Lookup screen, even when the Inactive check box has been checked.<br />
<br />
Deactivated: Patients that haven't been merged from, but have been deactivated in the Practice Management System, will be considered during matching; however, if they are found as the match, they will not be allowed to match. You will see a "-103 Patient is inactive" error.<br />
<br />
==Patient Matching Logic Spreadsheet==<br />
[[Media:AHS Patient Matching Logic.xls|Here]] is another representation of the information in this Wiki article. Patient Matching in [[TouchWorks]] is often times confusing and the hope is a different view into the logic may help make it more clear.</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Interface_Troubleshooting&diff=18917ConnectR Interface Troubleshooting2014-12-09T17:15:27Z<p>Ray.Lape: </p>
<hr />
<div>[[Category:ConnectR]]<br />
== Debug Procedure ==<br />
1. Ensure Error Message Definitions are loaded into ConnectR database. If Error Message Definitions are not loaded into ConnectR database there is a database script available to load.<br><br />
2. Copy command from Target Message Grid into SQL Query window<br><br />
[[Image:ConnectR_Debug_Documentation_Img2.jpg]]<br><br><br />
3. Remove beginning and end parenthesis<br><br />
4. Edit/Find ‘ -> Replace with ‘’(single quote with double single quote)<br>Note that SQL does not process double quotation marks. Find '''Single Quotation Mark''' and replace with '''two Single Quotations Marks'''.<br />
[[Image:ConnectR_Debug_Documentation_Img6.jpg]]<br><br><br />
5. Insert a comma after the name of the stored procedure<br><br><br />
6. Add a single quote before the first value being passed to the stored procedure and add a single quote after the last value<br><br><br />
7. Run sp_idxgenspcall, sp_name (for example, FileApppointment_CMS), with the remaining SQLCommand encapsulated in single quotes (both at the beginning and end). Also, remember to insert a comma after the name of the stored procedure. Before you execute this query, make sure the results are set to 'Results to Text'.<br><br />
8. Us the sp_idxgenspcall query at the beginning of the text. <br><br />
9. Query Options / select Text under Results. <br><br />
10. Copy text results & paste into new query window<br><br />
[[Image:ConnectR_Debug_Documentation_Img7.jpg]]<br><br><br />
11. Add begin tran (at the beginning of the script) / rollback tran (to the end of the script) to query. Execute query and utilize this information to root cause the error.<br><br />
12. If 0 is not returned, then continue to query the stored procedure call by Highlight the Stored Procedure / Right Click Scripts Stored Procedure as / Create to / New Query Editor Window, this will allow you to review the call procedure and what the expected value is for each field, you can also search the call for the error codes.<br><br />
<br />
== Example ==<br />
In the example shown below, required fields were present in the Stored Procedure called by the mapping, but were not present in the current Interface mapping. Thus the outcome was that the target message had to be changed to include the additional fields.<br><br />
[[Image:ConnectR_Debug_Documentation_Img5.jpg]]<br><br><br />
<br />
== Hint ==<br />
Cycle systems after changing a mapping<br><br />
[[Image:ConnectR_Debug_Documentation_Img8.jpg]]<br><br><br />
<br />
== Notes ==<br />
If you are encountering SQL formatting, syntax, or other errors when trying to run the queries check the following:<br />
#There should be a comma after the name of the stored procedure. For example, the beginning of the query should read, "sp_idxgenspcall FileAppoinment_CMS,"<br />
#The text immediately following this comma should be enclosed in a single quotation, and the corresponding single closing quotation should be the last character input as part of the query.<br />
#Make sure the results of the query in step 5 are sent to text, as this information is needed for step #7.</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Allscripts_CIE_-_Error_Resolution_with_the_Reconciler.pdf&diff=18761File:Allscripts CIE - Error Resolution with the Reconciler.pdf2014-09-12T19:04:39Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_CIE_-_Error_Resolution_with_the_Reconciler&diff=18760Allscripts CIE - Error Resolution with the Reconciler2014-09-12T19:04:15Z<p>Ray.Lape: Created page with "Category:Webcasts __TOC__ ==Webcast Overview== Join us to for an overview of what interface error resolution will look like and how it works once you make the switch to ..."</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
Join us to for an overview of what interface error resolution will look like and how it works once you make the switch to the Allscripts Common Interface Engine.<br />
<br />
==Q&A==<br />
'''Q. You are using an XML example. Will we cotinue to use HL7 v2.x messages if that is our current set up.?'''<br />
<br>'''A.''' Your interfaces will continue to use the message format they use today. If they are HL7 v2.3 today they will continue with that structure when migrated. However in order to file data into or pull data out of the Works database you will be using an XML format that will be translated into or from HL7.<br />
<br />
<br />
'''Q. Also is there any plan by Allscripts to migrate AIE to CIE? If so will it use a single instance of Rhapsody or will we have an instance for each application?'''<br />
<br>'''A.''' It is our understanding that CIE will eventually be the interface engine used across all Allscripts products.<br />
<br />
<br />
'''Q. Finally, it we already have Rhapsody, could we just use that instance? (Version 5.5)'''<br />
<br>'''A.''' Yes, if you already have Rhapsody you could use that instance. Currently only version 4.1 is supported with Allscripts, but newer version will later be supported.<br />
<br />
<br />
'''Q. Can we limit which interfaces users are allow to work in the error queue?'''<br />
<br>'''A.''' No, unfortunately the security in the application does not allow that level of granularity yet.<br />
<br />
<br />
'''Q. What happens if some of our interfaces share the same InterfaceSourceID? '''<br />
<br>'''A.''' You will need to add logic in the Reconciler route to set one of the interfaces to a different InterfaceSourceID to allow you to segregate those interfaces in the error queue.<br />
<br />
<br />
'''Q. Is this something that would already be configured? Or do we have to configure it? '''<br />
<br>'''A.''' The interfaces from ConnectR will have to be configured in Rhapsody. There isn't a current method to simply copy the interfaces from ConnectR to Rhapsody.<br />
<br />
==Files==<br />
Delivered 09/10/2014: <br />
*[[Media:Allscripts CIE - Error Resolution with the Reconciler.pdf|Download slideshow]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR&diff=17722ConnectR2014-04-10T19:30:07Z<p>Ray.Lape: /* Resources */</p>
<hr />
<div>== Overview ==<br />
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.<br />
<br />
== History with Allscripts ==<br />
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.<br />
<br />
== Versions ==<br />
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.<br />
<br />
=== Version 4.5 ===<br />
*Clients<br />
** Windows - The windows client is the primary method for accessing this version of ConnectR. It supports the Allscripts-developed CMS Bridge Tool.<br />
** 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 desirable features had not yet been ported from the Windows client.<br />
<br />
=== Version 4.6.0 ===<br />
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.<br />
<br />
=== Version 4.6.2 ===<br />
* Clients - 4.6.2 can only be accessed through the web client.<br />
* 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.<br />
* Hot fixes - Update 15 is the latest hot fix from GE.<br />
<br />
=== Upgrading from 4.5 to 4.6.2 ===<br />
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.<br />
<br />
What's new in 4.6.2:<br />
* The Web Client is fully functional.<br />
* Script errors are now displayed in the Message Log and Error Worklist<br />
* Script errors are now fatal errors that prevent data from being sent, rather than being silently ignored<br />
* Bridge is supported in the web client<br />
* A number of bug fixes have been made since 4.5.133<br />
<br />
Upgrade Path<br />
With careful planning and thorough testing, you can mitigate most issues that you may encounter in an upgrade. The areas to focus on include:<br />
* Have a test ConnectR environment. If your group does not have one, get one installed and move all of your test interfaces over.<br />
* Test all of your interfaces as thoroughly as possible.<br />
** Ideally, this means you will have all interfaces have the same volume of data, and types of data, flow through your test ConnectR environment.<br />
** At a minimum, this means you will have tested all interfaces, with a few dozen messages<br />
** What to check for:<br />
*** Validate that there are no Application and Non-Application errors<br />
*** Grid the source and target messages to ensure that they appear as they would in production<br />
*** 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).<br />
*** Manually test every Script used by an interface in your production ConnectR environment<br />
*** Upgrade production on a Friday and test all weekend. Monitor the errors all weekend.<br />
<br />
== Resources ==<br />
[[Image:smallgoldstar.jpg|16px]] [http://www.galenhealthcare.com/interface-service/ Galen Professional Services]<br />
* [[Ack Messages]]<br />
* [[AE-EHR Interfaced Result-Driven Order Reconciliation]]<br />
* [http://interfaces.galenhealthcare.com Allscripts Interface Developers Network]<br />
* [[Bulk Load]]<br />
* [[Categorized Common ConnectR Errors]]<br />
* [[Clustering ConnectR]]<br />
* [[ConnectR Audit]]<br />
* [[ConnectR Connection Codes And Descriptions]]<br />
* [[ConnectR Customized Error Bridge Approach]]<br />
* [[ConnectR Error List Utility]]<br />
* [[ConnectR Interface Current State]]<br />
* [[ConnectR Interface Troubleshooting]]<br />
* [[ConnectR Jobs]]<br />
* [[ConnectR Move to Live Checklist]]<br />
* [[ConnectR on IE7, IE8 and greater]]<br />
* [[ConnectR Outbound Interface Connectivity Errors]]<br />
* [[ConnectR Performance]]<br />
* [[ConnectR Pre Proc Script]]<br />
* [[ConnectR Script - Return More Than One Value]]<br />
* [[ConnectR Superset Source]]<br />
* [[ConnectR Test, Development and Production (Live) Environment Best Practices]]<br />
* [[Developing Bridge-compatible stored procedures]]<br />
* [[FAQs]]<br />
* [[GE ConnectR Script Definition]]<br />
* [[GE ConnectR Troubleshooting]]<br />
* [[Incorrect syntax near '=']]<br />
* [[Interface-Driven Tasking]]<br />
* [[Interfaced Document Encounter Matching]]<br />
* [[Importing an Outbound Interface]]<br />
* [[Import/Export Interfaces]]<br />
* [[Item Dictionary Synchronization]]<br />
* [[Loading Message Definitions]]<br />
* [[Message Definition Load From DB]]<br />
* [[Outbound Interface Filtering]]<br />
* [[Setup of a new Test Environment which utilizes Pass-Thrus from Production]]<br />
* [[ConnectR Install Issues]]<br />
* [[Valid values for "Form" parameters in inbound interface mapping]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Outbound_Interface_Connectivity_Errors&diff=17721ConnectR Outbound Interface Connectivity Errors2014-04-10T19:28:21Z<p>Ray.Lape: Created page with "There are a number of error codes that may appear in the message log for outbound interfaces in ConnectR that generally indicate some sort of connectivity issue with the targe..."</p>
<hr />
<div>There are a number of error codes that may appear in the message log for outbound interfaces in ConnectR that generally indicate some sort of connectivity issue with the target system. These errors are often caused by just a blip in connectivity and may not be of concern. However, if these errors are frequently occuring and causing issues with an interface it may require troubleshooting the network connectivity with the target vendor.<br />
<br />
Below are a few of the error codes commonly seen and brief details about the error codes.<br />
<br />
*Error Code 10054 is a winsock error. <br />
**Connection reset by peer. <br />
**An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close.<br />
<br />
*Error Code 10053 means that an established connection has been dropped. <br />
**Software caused connection abort. <br />
**An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error. <br />
<br />
*Error Code 10038 <br />
**Socket operation on nonsocket. <br />
**An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Database_-_Vouchers&diff=17050Allscripts PM Database - Vouchers2013-11-25T13:40:18Z<p>Ray.Lape: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
Join us as we continue our series of reporting against the Allscripts PM Database. In this session we will explore the voucher data. We will review the tables involved, look at the database diagrams and write T-SQL queries against the database in SQL Server Management Studio. <br />
<br />
==Q&A==<br />
'''Q. Is there a way to modify the reports that the application is pointing to?'''<br />
<br>'''A.''' At this point there is not a way to modify these reports. Custom reports would be developed external to the application.<br />
<br />
==Files==<br />
Delivered 10/30/2013: <br />
*[[Media:Allscripts PM Database Reporting - Financial Data.pdf|Download slideshow]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Database_-_Vouchers&diff=17049Allscripts PM Database - Vouchers2013-11-25T13:35:34Z<p>Ray.Lape: Created page with "Category:Webcasts __TOC__ ==Webcast Overview== Join us as we continue our series of reporting against the Allscripts PM Database. In this session we will explore the vo..."</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
Join us as we continue our series of reporting against the Allscripts PM Database. In this session we will explore the voucher data. We will review the tables involved, look at the database diagrams and write T-SQL queries against the database in SQL Server Management Studio. <br />
<br />
<br />
==Files==<br />
Delivered 10/30/2013: <br />
*[[Media:Allscripts PM Database Reporting - Financial Data.pdf|Download slideshow]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:CXR_CIE.pdf&diff=16738File:CXR CIE.pdf2013-08-20T19:20:56Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Rhapsody_Webcast_Series:_Making_the_Switch_from_ConnectR_to_CIE&diff=16737Rhapsody Webcast Series: Making the Switch from ConnectR to CIE2013-08-20T19:20:26Z<p>Ray.Lape: Created page with "Category:Webcasts __TOC__ =='''Overview'''== Allscripts recently announced their strategy to migrate interface engines for EnterpriseTM clients from the legacy GE Connec..."</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
=='''Overview'''==<br />
<br />
Allscripts recently announced their strategy to migrate interface engines for EnterpriseTM clients from the legacy GE ConnectR application to Common Interface Engine (CIE) – a re-branded version of the Orion RhapsodyTM interface engine. This webcast will provide an overview of the CIE architecture, present the benefits of switching engines, and demonstrate and compare a functioning Reg/Sched in both CxR and CIE. Don’t miss out on this opportunity to get an inside view into what’s to come in the world of Allscripts integrations.<br />
<br />
=='''Resources'''==<br />
<br />
[[Media:CXR_CIE.pdf|ConnectR to CIE]] Presented July 26, 2013<br />
<br />
=='''Links'''==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Referral_Order_Optimization&diff=16706Referral Order Optimization2013-08-08T14:32:27Z<p>Ray.Lape: /* Webcast Q&A */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
Join us to learn how Galen is assisting clients optimize their referral order workflow with a solution to electronically send referral orders with related clinical information to outside providers. In this session we will demonstrate how the solution is integrated into the workflow in Enterprise EHR.<br />
<br />
===Webcast Q&A===<br />
<br />
'''Q: Did you say this was an Add-on from AS?'''<br />
<br />
'''A:''' No, this is actually an Add-on product offered by Galen.<br />
<br />
'''Q: Is this workflow primarily for external referrals?'''<br />
<br />
'''A:''' Yes, the workflow discussed and the product demonstrated in the webcast is primarily intended for external referrals to providers using other EHR systems.<br />
<br />
'''Q: What is the difference between Allscripts ARN and Galen's product?'''<br />
<br />
'''A:''' The primary difference is that the solution from Galen provides the flexibility to integrate with any external system.<br />
<br />
===Resources===<br />
[[Media:Referral Optimization.pdf|Referral Order Optimization (PDF)]]<br />
<br />
==Links==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Referral_Order_Optimization&diff=16705Referral Order Optimization2013-08-08T13:37:58Z<p>Ray.Lape: Created page with "Category:Webcasts __TOC__ Join us to learn how Galen is assisting clients optimize their referral order workflow with a solution to electronically send referral orders wi..."</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
Join us to learn how Galen is assisting clients optimize their referral order workflow with a solution to electronically send referral orders with related clinical information to outside providers. In this session we will demonstrate how the solution is integrated into the workflow in Enterprise EHR.<br />
<br />
===Webcast Q&A===<br />
<br />
'''Q: '''<br />
<br />
'''A:''' <br />
<br />
===Resources===<br />
[[Media:Referral Optimization.pdf|Referral Order Optimization (PDF)]]<br />
<br />
==Links==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Referral_Optimization.pdf&diff=16704File:Referral Optimization.pdf2013-08-08T13:37:44Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Database_-_Patients&diff=16183Allscripts PM Database - Patients2013-04-10T13:03:48Z<p>Ray.Lape: /* Q&A */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
This webcast will provide an overview of the Allscripts Enterprise PM Database model. In this session we will zero in on the patient demographics and provider data. We will review the tables involved, look at the database diagrams and write T-SQL queries against the database in SQL Server Management Studio. <br />
<br />
==Q&A==<br />
'''Q. Can referring providers be removed from PM?'''<br />
<br>'''A.''' Referring providers can be inactivated or can be removed as a referral source to prevent them from showing in the application, but can't be completely removed from the database.<br />
<br />
'''Q. Can you address patient notes?'''<br />
<br>'''A.''' Patient notes are stored in the Notes table where the Note_Type_ID references the Patient Notes type in the Note_Types table.<br />
<br />
'''Q. Are there any tables that we would have to worry about rollback transactions on with using NOLOCK hint?'''<br />
<br>'''A.''' Anytime you are using a NOLOCK hint you have the possibility of pulling back a record that may have been part of a transaction that got rolled back. It is best to run your report at times when you would not be expecting many other transactions to be occurring in the database.<br />
<br />
==Files==<br />
Delivered 4/3/2013: <br />
*[[Media:Intro_to_PM_Database.pdf|Download slideshow]]<br />
<br />
== Links ==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Database_-_Patients&diff=16156Allscripts PM Database - Patients2013-04-09T13:15:12Z<p>Ray.Lape: </p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
This webcast will provide an overview of the Allscripts Enterprise PM Database model. In this session we will zero in on the patient demographics and provider data. We will review the tables involved, look at the database diagrams and write T-SQL queries against the database in SQL Server Management Studio. <br />
<br />
==Q&A==<br />
'''Q. '''<br />
<br>'''A.''' <br />
<br />
<br />
==Files==<br />
Delivered 4/3/2013: <br />
*[[Media:Intro_to_PM_Database.pdf|Download slideshow]]<br />
<br />
== Links ==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Intro_to_PM_Database.pdf&diff=16155File:Intro to PM Database.pdf2013-04-09T13:12:19Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Database_-_Patients&diff=16154Allscripts PM Database - Patients2013-04-09T13:05:58Z<p>Ray.Lape: Created page with "Category:Webcasts __TOC__ ==Webcast Overview== This webcast will provide an overview of the Allscripts Enterprise PM Database model. In this session we will zero in on ..."</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
This webcast will provide an overview of the Allscripts Enterprise PM Database model. In this session we will zero in on the patient demographics and provider data. We will review the tables involved, look at the database diagrams and write T-SQL queries against the database in SQL Server Management Studio. <br />
<br />
==Q&A==<br />
'''Q. '''<br />
<br>'''A.''' <br />
<br />
<br />
==Files==<br />
Delivered 4/3/2013: <br />
*[[Media:Intro to PM Database.pdf|Download slideshow]]<br />
<br />
== Links ==</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Error_List_Utility&diff=14336ConnectR Error List Utility2012-09-21T14:49:14Z<p>Ray.Lape: /* Using Error List */</p>
<hr />
<div>__TOC__<br />
<br />
=Overview=<br />
Allscripts delivers a tool on the ConnectR Interface Server called "Error List" that can assist in bulk refiling error messages in [[ConnectR]]. This tool is useful when working with a new interface or anytime when dealing with a high volume of errors. It will allow you to quickly find all the values that are causing the errors. Once the issue with those values have been resolved, it will then allow you to refile all of the same error type for a specific target system.<br />
<br />
<br />
==Using Error List==<br />
<br />
*Connect to the following web address from the ConnectR server:<br />
**http://localhost/touchworksbridge/ELLogin.aspx<br />
<br />
*If the client has EIT, then connect to this address:<br />
**http://localhost/EIT<br />
**Click the link for Error List<br />
<br />
<br />
*Login using the ConnectR DSN and a ConnectR username.<br />
<br />
<br />
[[File:ErrorListTool1.jpg]]<br />
<br />
<br />
*Choose the target system, message type, and error message in question.<br />
<br />
<br />
[[File:ErrorListTool2.jpg]]<br />
<br />
<br />
*Choose the parameter that may be causing the error message.<br />
**You will get a list of the values from this parameter in the next step.<br />
**Keep in mind that you can choose multiple parameters and receive the values from multiple parameters in the list.<br />
<br />
<br />
[[File:ErrorListTool3.jpg]]<br />
<br />
<br />
*Click "GetErrors" and get a list of the values from that parameter for the error messages that you choose.<br />
<br />
<br />
[[File:ErrorListTool4.jpg]]<br />
<br />
<br />
*Fix the issue with those values.<br />
**This could mean adding to a dictionary or correcting the logic in the ConnectR Mapping.<br />
<br />
*Click "Refile Messages" once the issue with those values has been fixed.<br />
<br />
==Use Cases For Error List==<br />
*Determining the dictionary values that are missing out of a large number of errors.<br />
*Determining the output of a certain parameter across many error messages after a mapping change.<br />
*Extracting a list of information about error messages to send to someone responsible for the source system (i.e. Reference Lab).</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Webcasts&diff=14045Webcasts2012-07-25T19:32:14Z<p>Ray.Lape: </p>
<hr />
<div>Galen Healthcare is proud to offer a series of '''Free Webcasts'''. Any handouts or Q&A can be found on the following links.<br />
<br />
July 25, 2012 - [[Configuration and Deployment of Imagelink]]<br />
<br />
July 11, 2012 - [[Virtualization Technologies]]<br />
<br />
June 27, 2012 - [[Allscripts PM Interface Engine – Basic Setup and Monitoring]]<br />
<br />
June 22, 2012 - [[Advanced Note Build]]<br />
<br />
June 13, 2012 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
June 8, 2012 - [[Tasking Fundamentals]]<br />
<br />
May 25, 2012 - [[Organizational Considerations when Staff Terminate]]<br />
<br />
April 18, 2012 - [[Allscripts EEHR Servers - Web]]<br />
<br />
March 30, 2012 - [[Allscripts Enterprise EHR - OID Pt 2 - Advanced Order Features ]]<br />
<br />
February 22, 2012 - [[Galen Interface Solutions]]<br />
<br />
February 17, 2012 - [[Allscripts Enterprise EHR - OID Pt 1 - Basics of the OID]]<br />
<br />
February 3, 2012 - [[SSMT- CMT]]<br />
<br />
January 25, 2012 - ConnectR - Advanced Troubleshooting<br />
<br />
January 20, 2012 - [[Group to Specialty Mapping]] <br />
<br />
January 12, 2012 - [[VitalCenter Overview & Demo]] <br />
<br />
January 6, 2012 - Top 5 Workflow Challenges Resolved <br />
<br />
December 14, 2011 - [[Allscripts EEHR Servers - Message]] <br />
<br />
December 9, 2011 - [[Health Management Plan]] <br />
<br />
November 30, 2011 - [[ConnectR - Advanced Design]] <br />
<br />
November 16, 2011 -[[Reporting - Minimizing the Requisition]] <br />
<br />
November 11, 2011 - [[Charge Webcast]] <br />
<br />
November 2, 2011 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
October 28, 2011 - Basic Note Build - V11.2 <br />
<br />
October 14,2011 - [[MU Selection and Configuration of Measures]] <br />
<br />
May 2011 - [[CareGuide Webcast]]<br />
<br />
April 1, 2011 -[[Enterprise EHR Tasking]] <br />
<br />
March 18, 2011 - [[Allscripts Enterprise EHR - Order Synchronization]] <br />
<br />
March 04,2011 - [[ePrescribing/Surescripts RxHub]] <br />
<br />
February 18, 2011 - [[Allscripts Enterprise EHR - Advanced OID SSMT]] <br />
<br />
January 18, 2011 - [[Allscripts Enterprise EHR - OID SSMT Fundamentals]] <br />
<br />
November 17, 2010 - [[Reports - Analytics]] <br />
<br />
November 03, 2010 - [[Interfaces - Advanced Design]] <br />
<br />
October 20, 2010 - [[Reports - Order and Results]] <br />
<br />
October 06, 2010 - [[Tech - System Maintenance]] <br />
<br />
September 24, 2010 - [[Allscripts Enterprise EHR - Orders]] <br />
<br />
September 22, 2010 - [[Interfaces - Troubleshooting]] <br />
<br />
September 10, 2010 - [[Allscripts Enterprise EHR - Advanced Notes]] <br />
<br />
September 08, 2010 - [[Reports - Patient]] <br />
<br />
August 27, 2010 - [[Allscripts Enterprise EHR - Building Orders (Basics)]] <br />
<br />
August 25, 2010 - [[Interfaces - Imagelink]] <br />
<br />
August 13, 2010 - [[Allscripts Enterprise EHR - Building Notes (Basics)]] <br />
<br />
August 11, 2010 - [[Allscripts Analytics]] <br />
<br />
<br />
'''See schedule and register at:'''<br />
[http://www.galenhealthcare.com/calendar/ Webinar Calendar]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Imagelink.pdf&diff=14044File:Imagelink.pdf2012-07-25T19:31:19Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Configuration_and_Deployment_of_Imagelink&diff=14043Configuration and Deployment of Imagelink2012-07-25T19:30:58Z<p>Ray.Lape: Created page with "__TOC__ ==Webcast Overview== This webcast will provide an overview of Imagelink configuration within the AE-EHR and implementation of corresponding result interface dependencie..."</p>
<hr />
<div>__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
This webcast will provide an overview of Imagelink configuration within the AE-EHR and implementation of corresponding result interface dependencies.<br />
<br />
==Q&A==<br />
'''Q. Is it possible to include user credentials that would be invoked when clicking the imagelink button?'''<br />
<br>'''A.''' a. Yes, this can be accomplished via a URL variable in the Imagelink setup<br />
<br />
'''Q. What file types are supported?'''<br />
<br>'''A.''' a. All images types that render in IE are acceptable<br />
<br />
==Files==<br />
Delivered 7/25/2012: <br />
*[[Media:Imagelink.pdf|Download slideshow]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Webcasts&diff=13938Webcasts2012-06-27T19:32:34Z<p>Ray.Lape: </p>
<hr />
<div>Galen Healthcare is proud to offer a series of '''Free Webcasts'''. Any handouts or Q&A can be found on the following links.<br />
<br />
June 27, 2012 - [[Allscripts PM Interface Engine – Basic Setup and Monitoring]]<br />
<br />
June 22, 2012 - [[Advanced Note Build]]<br />
<br />
June 13, 2012 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
May 25, 2012 - [[Organizational Considerations when Staff Terminate]]<br />
<br />
April 18, 2012 - [[Allscripts EEHR Servers - Web]]<br />
<br />
March 30, 2012 - [[Allscripts Enterprise EHR - OID Pt 2 - Advanced Order Features ]]<br />
<br />
February 22, 2012 - [[Galen Interface Solutions]]<br />
<br />
February 17, 2012 - [[Allscripts Enterprise EHR - OID Pt 1 - Basics of the OID]]<br />
<br />
February 3, 2012 - [[SSMT- CMT]]<br />
<br />
January 25, 2012 - ConnectR - Advanced Troubleshooting<br />
<br />
January 20, 2012 - [[Group to Specialty Mapping]] <br />
<br />
January 12, 2012 - [[VitalCenter Overview & Demo]] <br />
<br />
January 6, 2012 - Top 5 Workflow Challenges Resolved <br />
<br />
December 14, 2011 - [[Allscripts EEHR Servers - Message]] <br />
<br />
December 9, 2011 - [[Health Management Plan]] <br />
<br />
November 30, 2011 - [[ConnectR - Advanced Design]] <br />
<br />
November 16, 2011 -[[Reporting - Minimizing the Requisition]] <br />
<br />
November 11, 2011 - [[Charge Webcast]] <br />
<br />
November 2, 2011 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
October 28, 2011 - Basic Note Build - V11.2 <br />
<br />
October 14,2011 - [[MU Selection and Configuration of Measures]] <br />
<br />
May 2011 - [[CareGuide Webcast]]<br />
<br />
April 1, 2011 -[[Enterprise EHR Tasking]] <br />
<br />
March 18, 2011 - [[Allscripts Enterprise EHR - Order Synchronization]] <br />
<br />
March 04,2011 - [[ePrescribing/Surescripts RxHub]] <br />
<br />
February 18, 2011 - [[Allscripts Enterprise EHR - Advanced OID SSMT]] <br />
<br />
January 18, 2011 - [[Allscripts Enterprise EHR - OID SSMT Fundamentals]] <br />
<br />
November 17, 2010 - [[Reports - Analytics]] <br />
<br />
November 03, 2010 - [[Interfaces - Advanced Design]] <br />
<br />
October 20, 2010 - [[Reports - Order and Results]] <br />
<br />
October 06, 2010 - [[Tech - System Maintenance]] <br />
<br />
September 24, 2010 - [[Allscripts Enterprise EHR - Orders]] <br />
<br />
September 22, 2010 - [[Interfaces - Troubleshooting]] <br />
<br />
September 10, 2010 - [[Allscripts Enterprise EHR - Advanced Notes]] <br />
<br />
September 08, 2010 - [[Reports - Patient]] <br />
<br />
August 27, 2010 - [[Allscripts Enterprise EHR - Building Orders (Basics)]] <br />
<br />
August 25, 2010 - [[Interfaces - Imagelink]] <br />
<br />
August 13, 2010 - [[Allscripts Enterprise EHR - Building Notes (Basics)]] <br />
<br />
August 11, 2010 - [[Allscripts Analytics]] <br />
<br />
<br />
'''See schedule and register at:'''<br />
[http://www.galenhealthcare.com/calendar/ Webinar Calendar]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Interface_Engine_%E2%80%93_Basic_Setup_and_Monitoring&diff=13937Allscripts PM Interface Engine – Basic Setup and Monitoring2012-06-27T19:31:28Z<p>Ray.Lape: </p>
<hr />
<div>__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
This webcast will provide an overview of the components of an interface in AIE, the interface engine for Allscripts PM. Components that will be covered include connectivity, translation files, trigger events and more. We will also review basic monitoring opportunities for AIE interfaces.<br />
<br />
==Q&A==<br />
'''Q. How do you bulk load patients or appointments?'''<br />
<br>'''A.''' AIE does provide a method to bulk load in the utilities section on the left hand bottom of the screen. This historically did not work well for bulk loads of greater than 10K. It would fail somewhere before 10K. It may work better now, but you can also bulk load via a SQL script by inserting the records into the export events table. This is probably the more commonly used method and it provides greater flexibility. <br />
<br />
'''Q. What are some senarios that you would need to modify a stylesheet?'''<br />
<br>'''A.''' There could be various reasons depending on the organization, but one that come to mind is maybe you have a new additional information field that you want to capture data in and send to EHR. You can easily set up the translation to pull that data into an empty PID segment to send to EHR.<br />
<br />
'''Q. What are your common troubleshooting steps when you experience a problem?'''<br />
<br>'''A.''' First check to see if messages are sitting unprocessed that shouldn’t be, then check the activity log for any critical or fatal errors, then look at the export events or import events table for the last record that processed successfully and compare it to the failed record to see what the problem is. <br />
<br />
==Files==<br />
Delivered 6/27/2012: <br />
*[[Media:Allscripts PM Interface Webcast.pdf|Download slideshow]]<br />
*[[Media:Common Enum References.pdf|Download Common Enum References]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Interface_Engine_%E2%80%93_Basic_Setup_and_Monitoring&diff=13936Allscripts PM Interface Engine – Basic Setup and Monitoring2012-06-27T19:30:31Z<p>Ray.Lape: </p>
<hr />
<div>==Webcast Overview==<br />
This webcast will provide an overview of the components of an interface in AIE, the interface engine for Allscripts PM. Components that will be covered include connectivity, translation files, trigger events and more. We will also review basic monitoring opportunities for AIE interfaces.<br />
<br />
==Q&A==<br />
'''Q. How do you bulk load patients or appointments?'''<br />
<br>'''A. AIE does provide a method to bulk load in the utilities section on the left hand bottom of the screen. This historically did not work well for bulk loads of greater than 10K. It would fail somewhere before 10K. It may work better now, but you can also bulk load via a SQL script by inserting the records into the export events table. This is probably the more commonly used method and it provides greater flexibility.''' <br />
<br />
'''Q. What are some senarios that you would need to modify a stylesheet?'''<br />
<br>'''A. There could be various reasons depending on the organization, but one that come to mind is maybe you have a new additional information field that you want to capture data in and send to EHR. You can easily set up the translation to pull that data into an empty PID segment to send to EHR.'''<br />
<br />
'''Q. What are your common troubleshooting steps when you experience a problem?'''<br />
<br>'''A. First check to see if messages are sitting unprocessed that shouldn’t be, then check the activity log for any critical or fatal errors, then look at the export events or import events table for the last record that processed successfully and compare it to the failed record to see what the problem is.''' <br />
<br />
==Files==<br />
Delivered 6/27/2012: <br />
*[[Media:Allscripts PM Interface Webcast.pdf|Download slideshow]]<br />
*[[Media:Common Enum References.pdf|Download Common Enum References]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Common_Enum_References.pdf&diff=13935File:Common Enum References.pdf2012-06-27T19:25:28Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:Allscripts_PM_Interface_Webcast.pdf&diff=13934File:Allscripts PM Interface Webcast.pdf2012-06-27T19:25:11Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=Allscripts_PM_Interface_Engine_%E2%80%93_Basic_Setup_and_Monitoring&diff=13933Allscripts PM Interface Engine – Basic Setup and Monitoring2012-06-27T19:24:52Z<p>Ray.Lape: Created page with "==Webcast Overview== This webcast will provide an overview of the components of an interface in AIE, the interface engine for Allscripts PM. Components that will be covered inclu..."</p>
<hr />
<div>==Webcast Overview==<br />
This webcast will provide an overview of the components of an interface in AIE, the interface engine for Allscripts PM. Components that will be covered include connectivity, translation files, trigger events and more. We will also review basic monitoring opportunities for AIE interfaces.<br />
<br />
==Files==<br />
Delivered 6/27/2012: <br />
*[[Media:Allscripts PM Interface Webcast.pdf|Download slideshow]]<br />
*[[Media:Common Enum References.pdf|Download Common Enum References]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR&diff=12652ConnectR2012-02-10T14:03:29Z<p>Ray.Lape: </p>
<hr />
<div>== Overview ==<br />
GE's ConnectR interface engine facilitates the transfer of information to different healthcare systems. Many of the pages on the Galen wiki will refer to its use relative to the Allscripts EHR, and transferring information into, and out of the Allscripts Enterprise EHR.<br />
<br />
<br />
== History with Allscripts ==<br />
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.<br />
<br />
== Versions ==<br />
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.<br />
<br />
=== Version 4.5 ===<br />
*Clients<br />
** Windows - The windows client is the primary method for accessing this version of ConnectR. It supports the Allscripts-developed CMS Bridge Tool.<br />
** 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.<br />
<br />
=== Version 4.6.0 ===<br />
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.<br />
<br />
=== Version 4.6.2 ===<br />
* Clients - 4.6.2 can only be accessed through the web client.<br />
* 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.<br />
* Hot fixes - Update 15 is the latest hot fix from GE.<br />
<br />
=== Upgrading from 4.5 to 4.6.2 ===<br />
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.<br />
<br />
What's new in 4.6.2:<br />
* The Web Client is fully functional.<br />
* Script errors are now displayed in the Message Log and Error Worklist<br />
* Script errors are now fatal errors that prevent data from being sent, rather than being silently ignored<br />
* Bridge is supported in the web client<br />
* A number of bug fixes have been made since 4.5.133<br />
<br />
Upgrade Path<br />
With careful planning and thorough testing, you can mitigate most issues that you may encounter in an upgrade. The areas to focus on include:<br />
* Have a test ConnectR environment. If your group does not have one, get one installed and move all of your test interfaces over.<br />
* Test all of your interfaces as thoroughly as possible.<br />
** Ideally, this means you will have all interfaces have the same volume of data, and types of data, flow through your test ConnectR environment.<br />
** At a minimum, this means you will have tested all interfaces, with a few dozen messages<br />
** What to check for:<br />
*** Validate that there are no Application and Non-Application errors<br />
*** Grid the source and target messages to ensure that they appear as they would in production<br />
*** 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).<br />
*** Manually test every Script used by an interface in your production ConnectR environment<br />
*** Upgrade production on a Friday and test all weekend. Monitor the errors all weekend.<br />
<br />
== Resources ==<br />
* [[ConnectR Application Install Troubleshooting]]<br />
* [[ConnectR Performance]]<br />
* [http://www.galenhealthcare.com/interface-service/ Galen Professional Services]<br />
* [http://interfaces.galenhealthcare.com Allscripts Interface Developers Network]<br />
* [[FAQs]]<br />
* [[Ack Messages]]<br />
* [[Clustering ConnectR]]<br />
* [[ConnectR Audit]]<br />
* [[ConnectR Interface Current State]]<br />
* [[ConnectR Test, Development and Production (Live) Environment Best Practices]]<br />
* [[ConnectR Interface Training]]<br />
* [[GE ConnectR Script Definition]]<br />
* [[GE ConnectR Troubleshooting]]<br />
* [[Developing Bridge-compatible stored procedures]]<br />
* [[ConnectR Interface Troubleshooting]]<br />
* [[Bulk Load]]<br />
* [[Item Dictionary Synchronization]]<br />
* [[Interface-Driven Tasking]]<br />
* [[ConnectR Move to Live Checklist]]<br />
* [[Setup of a new Test Environment which utilizes Pass-Thrus from Production]]<br />
* [[Refile Script for Target]]<br />
* [[Categorized Common ConnectR Errors]]<br />
* [[ConnectR Error List Utility]]<br />
* [[Incorrect syntax near '=']]<br />
* [[Valid values for "Form" parameters in inbound interface mapping]]<br />
* [[ConnectR Connection Codes And Descriptions]]<br />
* [[Interfaced Document Encounter Matching]]<br />
* [[ConnectR Customized Error Bridge Approach]]<br />
* [[ConnectR Pre Proc Script]]<br />
* [[ConnectR Script - Return More Than One Value]]<br />
* [[ConnectR on IE7, IE8 and greater]]<br />
* [[Import/Export Interfaces]]<br />
* [[Importing an Outbound Interface]]<br />
* [[ConnectR Superset Source]]<br />
* [[Outbound Interface Filtering]]<br />
* [[AE-EHR Interfaced Result-Driven Order Reconciliation]]<br />
* [[Loading Message Definitions]]<br />
* [[Starting System Service Issues]]<br />
* [[Message Definition Load From DB]]<br />
* [[ConnectR Jobs]]</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Error_List_Utility&diff=12651ConnectR Error List Utility2012-02-10T13:59:55Z<p>Ray.Lape: </p>
<hr />
<div>=Overview=<br />
Allscripts delivers a tool on the ConnectR Interface Server called "Error List" that can assist in bulk refiling error messages in ConnectR. This tool is useful when working with a new interface or anytime when dealing with a high volume of errors. It will allow you to quickly find all the values that are causing the errors. Once the issue with those values have been resolved, it will then allow you to refile all of the same error type for a specific target system.<br />
<br />
<br />
==Using Error List==<br />
<br />
*Connect to the following web address from the ConnectR server:<br />
**http://localhost/touchworksbridge/ELLogin.aspx<br />
<br />
*Login using the ConnectR DSN and a ConnectR username.<br />
<br />
<br />
[[File:ErrorListTool1.jpg]]<br />
<br />
<br />
*Choose the target system, message type, and error message in question.<br />
<br />
<br />
[[File:ErrorListTool2.jpg]]<br />
<br />
<br />
*Choose the parameter that may be causing the error message.<br />
**You will get a list of the values from this parameter in the next step.<br />
**Keep in mind that you can choose multiple parameters and receive the values from multiple parameters in the list.<br />
<br />
<br />
[[File:ErrorListTool3.jpg]]<br />
<br />
<br />
*Click "GetErrors" and get a list of the values from that parameter for the error messages that you choose.<br />
<br />
<br />
[[File:ErrorListTool4.jpg]]<br />
<br />
<br />
*Fix the issue with those values.<br />
**This could mean adding to a dictionary or correcting the logic in the ConnectR Mapping.<br />
<br />
*Click "Refile Messages" once the issue with those values has been fixed.<br />
<br />
<br />
==Use Cases For Error List==<br />
*Determining the dictionary values that are missing out of a large number of errors.<br />
*Determining the output of a certain parameter across many error messages after a mapping change.<br />
*Extracting a list of information about error messages to send to someone responsible for the source system (i.e. Reference Lab).</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Error_List_Utility&diff=12650ConnectR Error List Utility2012-02-10T13:58:55Z<p>Ray.Lape: </p>
<hr />
<div>=Overview=<br />
Allscripts delivers a tool on the ConnectR Interface Server called "Error List" that can assist in bulk refiling error messages in ConnectR. This tool is useful when working with a high volume of errors. It will allow you to quickly find all the values that are causing the errors. Once the issue with those values have been resolved, it will then allow you to refile all of the same error type for a specific target system.<br />
<br />
<br />
==Using Error List==<br />
<br />
*Connect to the following web address from the ConnectR server:<br />
**http://localhost/touchworksbridge/ELLogin.aspx<br />
<br />
*Login using the ConnectR DSN and a ConnectR username.<br />
<br />
<br />
[[File:ErrorListTool1.jpg]]<br />
<br />
<br />
*Choose the target system, message type, and error message in question.<br />
<br />
<br />
[[File:ErrorListTool2.jpg]]<br />
<br />
<br />
*Choose the parameter that may be causing the error message.<br />
**You will get a list of the values from this parameter in the next step.<br />
**Keep in mind that you can choose multiple parameters and receive the values from multiple parameters in the list.<br />
<br />
<br />
[[File:ErrorListTool3.jpg]]<br />
<br />
<br />
*Click "GetErrors" and get a list of the values from that parameter for the error messages that you choose.<br />
<br />
<br />
[[File:ErrorListTool4.jpg]]<br />
<br />
<br />
*Fix the issue with those values.<br />
**This could mean adding to a dictionary or correcting the logic in the ConnectR Mapping.<br />
<br />
*Click "Refile Messages" once the issue with those values has been fixed.<br />
<br />
<br />
==Use Cases For Error List==<br />
*Determining the dictionary values that are missing out of a large number of errors.<br />
*Determining the output of a certain parameter across many error messages after a mapping change.<br />
*Extracting a list of information about error messages to send to someone responsible for the source system (i.e. Reference Lab).</div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:ErrorListTool4.jpg&diff=12649File:ErrorListTool4.jpg2012-02-10T13:57:40Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:ErrorListTool3.jpg&diff=12648File:ErrorListTool3.jpg2012-02-10T13:57:18Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:ErrorListTool2.jpg&diff=12647File:ErrorListTool2.jpg2012-02-10T13:56:45Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:ErrorListTool1.jpg&diff=12646File:ErrorListTool1.jpg2012-02-10T13:55:36Z<p>Ray.Lape: uploaded a new version of &quot;File:ErrorListTool1.jpg&quot;</p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=File:ErrorListTool1.jpg&diff=12645File:ErrorListTool1.jpg2012-02-10T13:54:01Z<p>Ray.Lape: </p>
<hr />
<div></div>Ray.Lapehttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Error_List_Utility&diff=12644ConnectR Error List Utility2012-02-10T13:52:26Z<p>Ray.Lape: Created page with "=Overview= Allscripts delivers a tool called "Error List" that can assist in bulk refiling error messages in ConnectR. This tool is useful when working with a high volume of err..."</p>
<hr />
<div>=Overview=<br />
Allscripts delivers a tool called "Error List" that can assist in bulk refiling error messages in ConnectR. This tool is useful when working with a high volume of errors. It will allow you to quickly find all the values that are causing the errors. Once the issue with those values have been resolved, it will then allow you to refile all of the same error type for a specific target system.<br />
<br />
<br />
==Using Error List==<br />
<br />
*Connect to the following web address from the ConnectR server:<br />
**http://localhost/touchworksbridge/ELLogin.aspx<br />
<br />
*Login using the ConnectR DSN and a ConnectR username.<br />
<br />
<br />
[[File:ErrorListTool1.jpg]]<br />
<br />
<br />
*Choose the target system, message type, and error message in question.<br />
<br />
<br />
[[File:ErrorListTool2.jpg]]<br />
<br />
<br />
*Choose the parameter that may be causing the error message.<br />
**You will get a list of the values from this parameter in the next step.<br />
**Keep in mind that you can choose multiple parameters and receive the values from multiple parameters in the list.<br />
<br />
<br />
[[File:ErrorListTool3.jpg]]<br />
<br />
<br />
*Click "GetErrors" and get a list of the values from that parameter for the error messages that you choose.<br />
<br />
<br />
[[File:ErrorListTool4.jpg]]<br />
<br />
<br />
*Fix the issue with those values.<br />
**This could mean adding to a dictionary or correcting the logic in the ConnectR Mapping.<br />
<br />
*Click "Refile Messages" once the issue with those values has been fixed.<br />
<br />
<br />
==Use Cases For Error List==<br />
*Determining the dictionary values that are missing out of a large number of errors.<br />
*Determining the output of a certain parameter across many error messages after a mapping change.<br />
*Extracting a list of information about error messages to send to someone responsible for the source system (i.e. Reference Lab).</div>Ray.Lape