1 / 34

ConnectR: Error Worklist

ConnectR: Error Worklist. Table of Contents. Review of ConnectR Common HL7 Inbound Target Errors HL7 Inbound Target Error Worklist DMWL Troubleshooting. Learning Objectives. Understand the function of the Error Worklist Understand some common error types and the cause of some common errors

vila
Download Presentation

ConnectR: Error Worklist

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ConnectR: Error Worklist

  2. Table of Contents • Review of ConnectR • Common HL7 Inbound Target Errors • HL7 Inbound Target Error Worklist • DMWL Troubleshooting

  3. Learning Objectives • Understand the function of the Error Worklist • Understand some common error types and the cause of some common errors • Utilize the HL7 Inbound Target Error Worklist to resolve or remove errors • Understand how to troubleshoot DMWL

  4. Review

  5. Review • ConnectR is an interface engine that receives data messages from HIS/RIS, processes (translates) this data, and inserts or updates the data in the database • Patient and exam data from external systems is entered in the iSite database and may be viewed in the iSite Enterprise, iSuite, and iSite Radiology applications

  6. Review • Issues may arise during message processing in any type of interface • Message processing errors can affect patient care because either DICOM images are not being registered in the database or HL7 messages are not being posted along with the DICOM images • The Error Worklist provides a list of message processing errors that may require action to ensure that patient care is not effected

  7. Common HL7 Inbound Target Errors

  8. Invalid Scheduled Date/Time (-3053) • This error indicates that the schedule date/time in an HL7 ORM message is not formatted properly • As an example “20040730 060” is probably 6:00 am, but ConnectR is unable to process the invalid “space” character in this field • The illegal character should be removed in the RIS and the message resent

  9. Attending Provider Not Found (-3091) • The Provider identifier " xxxxxx " contains an illegal character, or was not present at all • The illegal character should be removed in the RIS, or missing characters added, and the message resent

  10. Patient Locked by Another User (-3107) • This error indicates a timing conflict for an HL7 message, either a user has locked the patient record or another message attempted filing simultaneously on the same interface • This error may usually be resolved by re-filing, though manual clearing of the lock using iSuite may be required • NOTE: The current exam status in iSite should be reviewed prior to re-filing the message because, if the current status is ‘Final’ and the message is for a ‘Preliminary’ status, the exam status would revert back to Preliminary and would not have latest report

  11. Exam Locked by Another User (-3110) • This error indicates a timing conflict for an HL7 message, either a user has locked the exam record or another message attempted filing simultaneously on the same interface • This error may usually be resolved by refiling, though manual clearing of the lock using iSuite may be required • NOTE: The current exam status in iSite should be reviewed prior to refiling the message because, if the current status is ‘Final’ and the message is for a ‘Complete’ status, the exam status would revert back to ‘Complete,’ a report would not be available, and the exam could possibly be dictated again

  12. Order Number Not Found (-3148) • This may occur if an HL7 message is received for an order that has been previously cancelled or inactivated • This may also occur on an ORMOC/CA (Cancel) if the order does not already exist in the system • This error is often seen following a conversion from an iSite Pilot to a Production system, because many patients and exams will not have an existing context in iSite • The number of these errors should eventually be reduced or eliminated

  13. Patient Not Found (-3150) • This error indicates that the patient referenced in an ORMCA/OC (Cancel) or ADT Merge message does not already exist in the system • This error is often seen following a conversion from an iSite Pilot to a Production system, because many patients and exams will not have an existing context in iSite • The number of these errors should eventually be reduced or eliminated

  14. Unable to lookup Exam (-3310) • This error results from an ORMCA/OC (Cancel) message which references an Accession Number that does not exist in the system • This error is often seen following a conversion from an iSite Pilot to a Production system, because many patients and exams will not have an existing context in iSite • The number of these errors should eventually be reduced or eliminated • This error type may be safely ignored

  15. Acc Number in use on another patient (-3755) • This error is the result of an HL7 ORM or ORU message that references an Accession Number which is in use on another patient • An Accession Number may be utilized only once within an iSite Organization; therefore, the message should be corrected in the RIS and the message resent

  16. Unknown Error (-3999) • Call Philips Customer Care at 1-877-328-2808 or 1-877-328-2809 • Unknown Errors may be caused by many different factors • Re-filing is not recommended • If you find a rash of Unknown Errors, please indicate this to the Customer Care representative – this may be symptomatic of a larger issue

  17. HL7 Inbound Target Error Worklist

  18. HL7 Target Error Worklist • HL7 errors can be viewed in the Error Worklist by selecting the HL7 Target System

  19. Error Worklist • Select “All Errors” from the Error Type Filter • Select Date Range • Click on Build List

  20. Resolving Errors: Step 1 • “Double-click” on the error to open up the message log for the message related to the error

  21. Resolving Errors: Step 2 • A message log window appears with the offending Data Message displayed • Move forward one message to see the text of the error Step 2

  22. Resolving Errors: Step 3 • Use the play buttons to scroll through the Target messages until you find the error • The message that caused the error and prevented the data from filing in the database is the message prior to the error

  23. Resolving Errors: Step 4 • This is the message that resulted in the error • Grid this to find the accession number of the exam and the status that this message was trying to update this exam to

  24. Resolving Errors: Step 5 • Verify Exam Status Value prior to re-filing message • Log in to iSuite • Select Pt Record Module • Select Exam Option • Enter ACC (Accession Number) • Review the Exam Status • NOTE: If exam status in iSuite is further in the exam lifecycle than the message that erred in ConnectR, then DO NOT re-file the error

  25. Resolving Errors: Step 6 • Remove or Refile Errors on the Error Worklist: • Remove an error: click Remove • Refile an error: click Refile • NOTE: Only qualified and trained personnel should determine if an error should be removed or refiled

  26. DMWL Troubleshooting

  27. DICOM Modality Worklist • Observation: DICOM Modality Worklist functions, but does not include the expected exam • Resolution: • Confirm that the exam is available in the Technologist Worklist and is “Scheduled” or “In Progress” for the current date and time minus 24 hours through current date and time plus 2 hours • Verify that patient and exam data was entered correctly on modality • NOTE: Data entry errors could cause exceptions or duplicate Study instance Unique Identifiers (UIDs)

  28. DMWL Troubleshooting iSuite Technologist Worklist • Take the following steps if you use DMWL and there is no response: • Use the iSuite Technologist Worklist to find the exam • If the exam is present (in either “S” or “I” status), then look at DMWL Source and Target Systems in ConnectR • To look up exams in the Technologist Worklist: • Select “Yes” in this prompt • Select the resources (or modalities) that you want the exams for by clicking on the • Use the Primary Filters to select other matching criteria • Select “search/refresh” to view the list of matching exams

  29. DMWL Source • A DMWL Source message log will show Data, ACK, and Error messages • Unlike all other Source and Target systems, the Msg IDs of Source messages do not correspond to Msg IDs of Target messages

  30. DMWL Source • To find a Source’s corresponding Target message, make note of the timestamp of the Source message • Search by that timestamp in the Target message log • Data Messages represent the inbound query from a Modality

  31. DMWL Source • The ACK Message immediately following the Data Message represents the outbound results of that query; therefore, moving chronologically through the message log you will see Data – ACK – Data – ACK

  32. DMWL Source • To search for queries from a particular AE Title, enter the AE Title in the String Filter - This returns only Data Messages (inbound queries) • To view the ACK Message (results) for the Data Message found, clear the String Filter value and click the Refresh button then move forward one message to see the ACK

  33. For assistance, please call customer support at 1-877-328-2808 or 1-877-328-2809

More Related