1 / 43

ConnectR: Overview

ConnectR: Overview . Learning Objectives. Understand the function of all ConnectR interfaces Monitor ConnectR interface statuses View Message Logs. Table of Contents. Introduction ConnectR Interfaces Message Logs. Introduction. Introduction.

majed
Télécharger la présentation

ConnectR: Overview

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: Overview

  2. Learning Objectives • Understand the function of all ConnectR interfaces • Monitor ConnectR interface statuses • View Message Logs

  3. Table of Contents • Introduction • ConnectR Interfaces • Message Logs

  4. Introduction

  5. Introduction • ConnectR is an interface engine that receives data messages from HIS/RIS, processes (translates) this data, and inserts/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. Introduction • 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

  7. Access • In the address box, type in the IP address of your Philips iSite Server followed by “/idxconnectr/launch.asp” • Type “User ID” and “Password” in the appropriate fields • ConnectR Log-ins are independent of all other iSite Log-ins; therefore you may need to request Philips iSite CARE to add new ConnectR Log-ins • Select “ConnectR” for Data Source

  8. Status Page • To access the Status Page: • Click on the “Monitor” bar • Click on the “Status” bar

  9. Monitor Status • Within ConnectR, there are numerous system pairs (Source and Target) that handle different types of data coming into the system by converting the data to a format that the iSite database can understand • The server status as well as the status of each of these system pairs can be monitored

  10. System Pairs DICOM PAIR HL7 PAIR Internal Communication Pair DMWL PAIR

  11. Source Systems • Source Systems designate the first point of data entry from an outside source into ConnectR • The Source Systems pass the data to their associated Target System which will insert/update the data in the iSite database

  12. Target Systems • The Target Systems then process the data and update the iSite Database with the information that the data messages contained

  13. Last Message • The Last Message column displays the date and time stamp of the last message that came through that associated system

  14. QSize • The QSize column displays the number of messages waiting in the queue to be processed. A “0” value indicates that the interface is processing messages in an expedient manner • Take note or contact Customer Care if Queue is in the hundreds or thousands

  15. ConnectR Interfaces

  16. Stentor to IDX Interface • Stentor to IDX Source – Stentor to IDX Target • Internal messaging based on data received in DICOM Headers from modalities (study registration, study deletions, study completion status) • Source system – receives internal messages about studies from iSite nodes and passes the messages to the target system for processing • Target system – processes and registers the messages from the modality into the database

  17. DICOM Pair • Source system – receives internal messages about studies from iSite nodes and passes the messages to the target system for processing • Target system – processes and registers the messages from the modality into the database

  18. DICOM Series Registration Flowchart ConnectR – HL7 Inbound Interface New Order ORMNW ORMSC Update/Complete Order RIS ORU Preliminary Report ORU Final Report iSite DB ConnectR – DMWL Interface C-FIND-RQ Source Target Merge Toolkit Merge Toolkit DICOM DATA SP CALL C-FIND-RSP Source MODALITY DICOM ACK iSite Processing Module MSMQ - iSuitenorm C-STORE SERIESREG MSMQ DICOM ConnectR – Philips -> IDX Interface

  19. HL7 Inbound Interface • HL7 Inbound Source – HL7 Inbound Target • Source system - receives HL7 data messages (ADT, ORM, ORU) from HIS/RIS • Target system - processes HL7 data messages received from the HL7 Inbound Source and inserts/updates data in the iSite database

  20. HL7 Pair • Source system - receives HL7 data messages (ADT, ORM, ORU) from HIS/RIS • Target system - processes HL7 data messages received from the HL7 Inbound Source and inserts/updates data in the iSite database

  21. Target SP CALL ConnectR – HL7 Inbound Interface New Order ORMNW ORMSC Update/Complete Order RIS ORU Preliminary Report ORU Final Report ConnectR – DMWL Interface iSite DB C-FIND-RQ Source Merge Toolkit Merge Toolkit DICOM DATA C-FIND-RSP Source MODALITY DICOM ACK iSite Processing Module MSMQ - iSuitenorm C-STORE SERIESREG MSMQ DICOM ConnectR – Philips -> IDX Interface

  22. IDX to Stentor Interface • IDX to Stentor Source – IDX to Stentor Target • Internal messaging from the iSite database to iSite nodes (via MSMQ) to update DICOM Headers (demographic updates, study deletions, accession number updates) • Source system – receives updates from iSite database triggers and passes the messages to the target system for processing • Target system – processes the updates and forwards the updates to the iSite nodes (via MSMQ)

  23. Internal Pair • Source system – receives updates from iSite database triggers and passes the messages to the target system for processing • Target system – processes the updates and forwards the updates to the iSite nodes (via MSMQ)

  24. DICOM Modality Worklist Interface • DICOM Modality Worklist Source – DICOM Modality Worklist Target • DICOM Modality Worklist interface is a pure DICOM to Database and back to DICOM (two-way) interface • Source system – receives the DMWL query from the Modality (DICOM C-Find) • Target system – queries the iSite database via ODBC based on the query received in the Source. By default queries will return orders in either (S)cheduled or (I)nProgress status • Source system – sends the results from the query made by the Target interface back to the querying modality (DICOM C-FIND-RSP)

  25. DMWL Source • Source system – receives the DMWL query from the Modality (DICOM C-Find) • Target system – queries the iSite database via ODBC based on the query received in the Source • By default queries will return orders in either (S)cheduled or (I)nProgress status • Source system – sends the results of the query made by the Target interface back to the querying modality (DICOM C-FIND-RSP)

  26. DMWL Flowchart ConnectR – HL7 Inbound Interface New Order ORMNW ORMSC Update Order RIS ORU Preliminary Report HL7 ORU Final Report HL7 ConnectR – DMWL Interface iSite DB C-FIND-RQ Source Target Merge Toolkit Merge Toolkit DICOM DATA SP CALL C-FIND-RSP Source MODALITY DICOM ACK iSite Processing Module MSMQ - iSuitenorm C-STORE SERIESREG MSMQ DICOM ConnectR – Philips -> IDX Interface

  27. AutoCreate Interface • Some sites may have an AutoCreate interface in addition to an HL7 interface (i.e. receipt of images for which no HL7 will be received, as in studies from outside reading centers or affiliated clinics/hospitals without a RIS) • AutoCreate Source – AutoCreate Target • This interface pair is used with non-HL7 integrated systems. AutoCreate means that an accession number will be automatically created when an accession number is not present in STUDYREGISTRATION message • Source system – receives internal messages about studies from iSite nodes and passes the messages to the target system for processing • Target system – Creates/updates patients and orders based on DICOM Header information and registers the associated study in the iSite database

  28. Message Logs

  29. Message Log Page • To access the Status Page: • Click on the “Monitor” • Click on the “Message Log” • Select a system on the drop down arrow to view the original data messages that came into that system and how the data messages look as they leave that system

  30. Choosing An Interface • Step 1: Click on the down arrow to open up the drop down list and select the desired interface • Step 2: Select a date range by clicking on the Calendar icon • The dates highlighted in black are the only dates which have messages

  31. Stentor to IDX source • Source systems will display the original HL7 or image registration messages from the Modalities as well as Heartbeat Messages • The date and time stamp of the message displayed in the Target message box

  32. String Filter • Use the String Filter field to type in a search parameter (MRN, ACC, SUID are the most useful) for ConnectR to search through all messages • Record the Msg ID of the resulting messages) to find the correlated Target messages

  33. Message ID • Msg ID is a unique identifier that ConnectR assigns to each data message • Record a Source system Msg ID to look up the correlated Target messages • To search by Msg ID, type the number into the Msg ID field, not the String Filter

  34. Play Buttons • The arrow buttons: • Move to the beginning of the message log (the first message) • Move back one message at a time • Move forward one message time • Move you to the end of the message log (the last message)

  35. Grid Buttons • Click on the grid button in either the Target Message pane or the Source Message pane to view the message in an easy-to-read column format

  36. Grid Page • The Grid page will display the data messages in a tree-like format that makes it easier to look up individual field names and values

  37. Target Message Logs • Target systems show Target messages generated by the Source system • Target systems also show error messages immediately after the Target message that failed to process

  38. HL7 Source Message Logs • Systems may show different types of messages • Look at the Msg Type text box to determine what kind of message you are viewing • An HL7 Source will show “Data Messages” (HL7 messages received from a HIS/RIS) as well as the corresponding “ACK Messages” (an ACK is an acknowledgement from ConnectR to the sending system that the message was received successfully)

  39. HL7 Source Message Logs • When using the String Filter, it is useful to select only the “Data/SP” checkbox in Msg Filter – “ACK Messages” generally will not contain useful information, and removing them from the search halves the records that ConnectR must search through

  40. HL7 Target • The Target system will show Data, Error, and Operation Messages • To search the Target message log, first use the String Filter in the Source to determine Msg IDs • Enter the appropriate Msg ID into the Target message log to view all associated Data and Error messages

  41. HL7 Target • Avoid using the String Filter to search the Target message log • Of the many Target messages generated by the Source messages, only a few will contain common identifiers • String Filter searches will not return Error messages

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

More Related