ConnectR Interface Errors

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search

Appointment

-103: Patient is deactivated
-115: Appointment could not be created in TouchWorks. Please Submit a Webfirst Ticket.
-132: Cancelling an Appointment is not allowed once medical data is added to the visit in TouchWorks
-133: The Appointment Number sent is already in use in TouchWorks for a different Appointment. Please Submit a Webfirst Ticket.
-134: Appointment Number is already in use by another visit In TouchWorks with Medical Data. Please Submit a Webfirst Ticket.
-135: Appointment Number already in user by another visit In TouchWorks with current Appointments. Please Submit a Webfirst
-136: The Appointment number is currently in use for a valid appointment. Please Submit a Webfirst Ticket.
-137: Failed Inserting Injury Information. Please Submit a Webfirst Ticket.
-138: Failed Updating Injury Information. Please Submit a Webfirst Ticket.
-139: Failed Worker Comp Information. Please Submit a Webfirst Ticket.

Registration

-187: The MRN cannot be updated because it is already in use for a different Patient
-193: Internal Organization cannot be zero. Please Submit a Webfirst Ticket.
-188: Enterprise MRN and Organization MRN are not for same patient. Please Submit a Webfirst Ticket.
-189: Organization MRN is invalid. Please Submit a Webfirst Ticket.
-190: Enterprise MRN is invalid. Please Submit a Webfirst Ticket.
-191: The MRN you are trying to change is not in TW. Please Submit a Webfirst Ticket.
-102: Patient last name is required in TouchWorks. Please add a lastname in your Registration System.
-113: Patient could not be created in TouchWorks. Please Submit a Webfirst Ticket.
-122: Patient Insurance info could not be filed (non-fatal)
-101: Patient Organization and Enterprise MRNs dont match
-253: Patient exists in TouchWorks with the same demographics and a different Organization MRN
-254: Could not file Patient Directives in TouchWorks. Please Submit a Webfirst Ticket.
-255: Patient Security Group lookup failed, no matches found.
-256: Could not file Patient AccessGroup in TouchWorks. Please Submit a Webfirst Ticket.
-257: Could not update Patient Security Group
-258: Could not file Patient Security Group
-259: Contact Relationship code is Inactive

Document

-116: Provider does not validate
-196: There is no data sent in the Text. Please submit a Webfirst Ticket.
-192: Invalid NoteType DE
-199: Must specify a note type for an unsolicited transcription
-198: Cannot use a V2 note type for an unsolicited dictation
-171: Bad Marker
-197: The Dictation Marker sent is not in TouchWorks. Please submit a Webfirst Ticket.
-173: The Dictation Marker sent is not for this patient. Please submit a Webfirst Ticket.
-112: Error updating Activity_Header
-172: Transcription date has more than one encounter for the specified patient
-174: Transcription Marker Has Been Already Used
-175: Update attempted on same accession, different patient
-170: Transcription could not be created
-235: The Accession Number sent is already in use for different patient in TouchWorks. Please submit a Webfirst Ticket.
-121: The Structured Note is in use and currently locked.
-123: The document cannot be created in TouchWorks. Please submit a Webfirst Ticket.
-240: This Document has already be Finalized, you cannot not overwrite an invalidate

Result

-176: Provider sent is not valid in TouchWorks.
-177: Ordering Provider was not sent and is required in TouchWorks.
-194: Accession number was not sent and is required in TouchWorks
-195: Encounter Date/Time was not sent and is required in TouchWorks
-141: Result Item sent is not in TouchWorks. Please update the Item dictionary and refile the message.
-142: Result Item Classification sent is not in TouchWorks. Please update the Item dictionary and refile the message.
-145: Specified QO not in specified QO Class. Please update the Item dictionary and refile the message.
-181: Units supplied is not valid for Item
-143: Result Answer Data Type is not in TouchWorks.
-144: Unable to file result. Please submit a Webfirst Ticket.
-182: Could not file Result Text. Please submit a Webfirst Ticket.
-183: Could not file reference range text. Please submit a Webfirst Ticket.
-149: Could not file Annotation. Please submit a Webfirst Ticket.
-145: Specified QODE not found in specified QOCLASS
-146: Numeric result received is not a real number. Please submit a Webfirst Ticket.
-147: Result is greater than storable limit. Please submit a Webfirst Ticket.
-148: Bad Accession Number: Result Accession Number and External Visit Number do not match
-148: Result could not be created
-233: The Performed date/time sent is in the future. Please have the sender fix and resend the message
-601: Result cannot be set to preliminary because it is already final.
-602: Invalid task request
-603: Unable to identify QO_Classification_DE from alternate identifier

Dictionaries

-2005000: Answer Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015000: Answer Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2008002: Appointment Cancel Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2018002: Appointment Cancel Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2002002: Appointment Status Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2012002: Appointment Status Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2002000: Appointment Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2012000: Appointment Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005093: Billing Area Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015093: Billing Area Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005099: Billing Location Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015099: Billing Location Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005099: Chart Location Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015099: Chart Location Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001076: Document Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011076: Document Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001028: Employment Status Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011028: Employment Status Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001031: Encounter Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011031: Encounter Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2003008: Injury Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2013008: Injury Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2003002: Insurance Class Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2013002: Insurance Class Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001050: Location Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011050: Location Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005056: Note Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015056: Note Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001014: Provider Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011014: Provider Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005008: QO Classification DE[Item Classification]) Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015008: QO Classification DE[Item Classification]) Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005003: Qo DE[Item]) Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015003: Qo DE[Item]) Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001023: Race Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011023: Race Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001018: Relationship Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011018: Relationship Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001030: Religion Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011030: Religion Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2002003: Resource Dictionary Does Not Contain the Value Sent in the Message. Please set the Provider as Scheduleable in the Provider Dictionary and refile the message.
-2012003: Resource Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001019: Sex Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011019: Sex Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005032: Source Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015032: Source Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005036: Unit Code Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015036: Unit Code Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001021: Visit Status Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011021: Visit Status Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001022: Visit Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011022: Visit Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005120: Distribution Type Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015120: Distribution Type Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2001077: Directives Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2011077: Directives Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-2005094: Referring Provider Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2005038: Where Performed Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-2015094: Referring Provider Dictionary Contains more than one of Values Sent in the Message. Please Update the Dictionary and refile the message.
-50: Failed inserting into Dictionary_Entry table. Please Submit a Webfirst Ticket.
-54: Mnemonic sent is already in use and must be unique
-55: Failed updating Dictionary_Entry
-56: Failed inserting into target Dictionary Table. Please Submit a Webfirst Ticket.
-57: Failed inserting into ICD9Diag_Class_ICD9Diag. Please Submit a Webfirst Ticket.
-58: Failed inserting into Dictionary_Audit. Please Submit a Webfirst Ticket.
-59: Failed updating target Dictionary Table. Please Submit a Webfirst Ticket.
-60: Failed updating ICD9Diag_Class_ICD9Diag. Please Submit a Webfirst Ticket.
-61: Read-only dictionary. Please Submit a Webfirst Ticket.
-62: Failed inserting Dict_Definition_Set table. Please Submit a Webfirst Ticket.
-63: Failed updating Dict_Definition_Set table. Please Submit a Webfirst Ticket.
-64: Could not rename deleted entry. Please Submit a Webfirst Ticket.
-70: Not an External Organization. Please Submit a Webfirst Ticket.
-71: Code sent is already in use and must be unique
-72: Unsupported Dictionary. Please Submit a Webfirst Ticket.
-73: No Dictionary Entry Provided. Please Submit a Webfirst Ticket.
-74: Provider is not a User. Please Submit a Webfirst Ticket.
-80: UPIN sent is already in use and must be unique

ClinicalInterfaceChecking

-186: The Accession Number sent must be unique in TouchWorks and this one is in use. Please Submit a Webfirst Ticket.
-185: The Encounter is being used by a different patient. Please Submit a Webfirst Ticket.
-184: Visit indicated has more than one Encounter
-180: Activity does not belong to Patient. Please Submit a Webfirst Ticket.
-179: The External Visit Number sent is already in use in TouchWorks. Please Submit a Webfirst Ticket.
-178: External Visit Number is not invalid. Please Submit a Webfirst Ticket.
-162: Date of service does not match encounter date
-148: Visit Number is in use by a different activity. Please Submit a Webfirst Ticket.
-131: The External Visit Number sent is being used for a different patient. Please Submit a Webfirst Ticket.
-130: Visit Number cannot be Null. Please Submit a Webfirst Ticket.
-100: Patient cannot be identified based on the data sent by the External Source. Use the bridge utility to file the message

ClinicalInterfaceFiler

-109: Activity could not be created in TouchWorks. Please Submit a Webfirst Ticket
-110: There was an error in TouchWorks trying to create a Visit. Please Submit a Webfirst Ticket
-111: There was an error in TouchWorks trying to create an Encounter. Please Submit a Webfirst Ticket
-152: Annotation could not be created in TouchWorks. Please Submit a Webfirst Ticket

ADT

-236: The Hospital MRN cannot be updated because it is already in use for a different Patient in TouchWorks
-237: The Hospital MRN cannot be added because it is already in use for a different Patient in TouchWorks
-238: This ADT event Could not be filed, Please submit a Webfirst Ticket
-239: Hospital organization ID is not in TouchWorks, Please Submit a Webfirst Ticket
-240: Could not overwrite an invalid or final document
-241: Hospital MRN and Origination MRN are for different patients in TouchWorks
-242: Referring Provider Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-243: Billing Location Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-244: Billing Area Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-245: Division Dictionary Does Not Contain the Value Sent in the Message. Please Update the Dictionary and refile the message.
-246: The External Visit Number sent is already in use by another patient
-247: The Hospital must be set up as an External Organization, Please submit a Webfirst Ticket
-248: Admit Date is missing or the Date format is not Valid. Please Submit a Webfirst Ticket
-249: Bad List Filter Criteria. Please Submit a Webfirst Ticket.
-250: Could not file Patient List Entry. Please Submit a Webfirst Ticket.
-251: Could not file Visit Insurance. Please Submit a Webfirst Ticket.
-252: Could not Delete Patient List Entry. Please Submit a Webfirst Ticket.

Inbound Order

-300: Provider does not have authorization to order this item
-301: Unable to set status for a new order
-302: Modifier was not sent or is not in the Modifier Dictionary
-303: Authorization Mode was not sent or is not in the Authorization Mode Dictionary
-304: Requested performing location was not sent or is not in the Requested performing location Dictionary
-305: LoadWIPOrder call failed. Please Submit a Webfirst Ticket.
-306: SetV4Annotation call failed. Please Submit a Webfirst Ticket.
-307: SetAdditionalInformationWIP call failed. Please Submit a Webfirst Ticket.
-309: IntegrateAdditionalInformation call failed. Please Submit a Webfirst Ticket.
-301001: FileOrder - Order must be Unauthorized, Ordered, or Needs Information
-301002: FileOrder - Requested Order Status is invalid(10 to 4,10)
-301003: FileOrder - Requested Order Status is invalid (9 to 9,5,4)
-301004: FileOrder - Requested Order Status is invalid (6 to 6,4,2)
-301005: FileOrder - Requested Order Status is invalid (2 to 2,4)
-301006: FileOrder - Requested Order Status is invalid (7 to 7,4)
-301007: FileOrder - Ordering provider information cannot be changed once an order has an Active status
-301008: FileOrder - Order Priority information cannot be changed once an order has an Active status
-301009: FileOrder - Clinical Priority information cannot be changed once an order has an Active status
-301010: FileOrder - Requested Performing Location information cannot be changed once an order has an Active status
-301011: FileOrder - Authorization Number information cannot be changed once an order has an Active status
-301012: FileOrder - Qomod1de information cannot be changed once an order has an Active status
-301013: FileOrder - Qomod2de information cannot be changed once an order has an Active status
-301014: FileOrder - Qomod3de information cannot be changed once an order has an Active status
-301015: FileOrder - ClinicalSourcede information cannot be changed
-301016: FileOrder - Requested Order Status is invalid
-301017: FileOrder - Canceled, Discontinued, and EIE are not valid statuses for a new order
-301018: FileOrder - Invalid Order Status Transition for Existing Order
-301019: FileOrder - EncounterDTTM is NULL
-301020: FileOrder - Unable to identify Additional_Information_DE from alternate identifier
-301021: FileOrder - Unable to identify Additional_Information_DE
-301022: FileOrder - Additional Information entry is not in the picklist
-301023: FileOrder - Additional_Information_DE entry is not linked to the order
-301024: FileOrder - required additional information can not be defaulted
-301025: FileOrder - Resulted orders can not be changed
-301026: FileOrder - In Progress is not a valid status without a Specimen Collection date

FileProvider

-620701: XID is in use by a different provider
-620703: Could not determine provider name from information passed
-620704: Access Group used is not in TouchWorks
-620705: Internal org could not be determined. Please Submit a Webfirst Ticket
-620706: Provider already exists with a different name
-620707: Entry Code sent is already in use by a different Provider.
-620708: Internal Org could not be determined from the Regsystem passed. Please Submit a Webfirst Ticket.
-620709: Workplace passed does not exist. Please Submit a Webfirst Ticket.
-620710: Passed FW database does not exist. Please Submit a Webfirst Ticket.
-620711: Passed FW default system does not exist. Please Submit a Webfirst Ticket.

Detailed Error Descriptions

There are a handful of errors that are somewhat common; however, do not have simple solutions. These errors are outlined here.

  • -178 - "External Visit Number is not invalid. Please Submit a Webfirst Ticket."
    • Description: This occurs when existing clinical data are found (e.g. Results on FileResult_CMS) and the visit that's looked up during the filing of the clinical data does not match the visit associated to the existing clinical data.
    • Common Scenario: The Visit Number used is the Accession Number, plus the year of the results (based on date sent). If results are sent over as preliminary on Dec 29 and the final results come over on Jan 5. The year would be different, creating a different Visit Number (VisitNumberEXT).
    • Base Stored Procedure: ClinicalInterfaceChecking
    • Fix: ensure the Visit Number that's sent in through the interface will not differ when the same clinical data (e.g. results) are sent in.
      • Work around: Invalidate the current Results, then re-file the updates results that had erred in ConnectR.
  • -145: Specified QO not in specified QO Class. Please update the Item dictionary and refile the message.
    • Description: The resultable is not linked to the orderable item. Let's say this is a White Blood Count (WBC) on a CBC w/Diff that's being filed. What this error says is that the WBC and CBC w/Diff exist, but their not linked together. The WBC exists and may be linked to a CBC without Diff, but needs to be associated to the CBC w/Diff Orderable Item.
    • Fix: Update TWAdmin (or SA, if v10) to associate the Resultable Item with the Orderable Item. This may be done in the Orderable Item Dictionary (OID) in v11 under TWAdmin->Dictionaries. In the OID details you'll see an area to link Resultable Items.
  • -136: The Appointment number is currently in use for a valid appointment. Please Submit a Webfirst Ticket.
    • Description: an appointment exists at another date or time with the same External Appointment Number. You will see this if your PM system allows "moves" appointments without sending a new Appointment Number.
    • Fixes:
      • Your PM system could cancel the initial appointment and create a new appointment with a new Appointment Number.
      • Your PM system could do a "BAR Move", named after IDX's Billing and Accounts Receivable (currently part of GE Centricity Business Solutions). A bar move entails canceling the initial appointment and your interface would set the "Appt Cancel Reason" to BAR Move. Then a second message would be sent with the updated appointment time.
Retrieved from "https://wiki.galenhealthcare.com/index.php?title=ConnectR_Interface_Errors&oldid=8908"