TRN-0000-02 Rev 12/14/04 ConnectR Training. TRN-0000-02 Rev 12/14/04 1.Introduction: What is...

TRN-0000-02 Rev 12/14/04

ConnectR TrainingConnectR Training

TRN-0000-02 Rev 12/14/04

1. Introduction: What is ConnectR?2. The Big Picture: Data Flow Diagram3. Access: How to Log In4. Server and System Status5. System Pairs: What are the interfaces?6. Message Logs: How to Read Messages7. Error Worklist: How to Re-File an Error

Table of ContentsTable of Contents

TRN-0000-02 Rev 12/14/04

1. Ability to monitor server/system status

2. Understand the various interfaces and their associated functions

3. Ability to read various types of messages

4. Ability to monitor the error worklist5. Ability to re-file errors appropriately6. Ability to perform basic trouble

shooting with DICOM Modality worklist issues

ObjectivesObjectives

TRN-0000-02 Rev 12/14/04

ConnectR is an interface engine. It is capable of interpreting and translating DICOM and HL7 messages into a format which is compatible and understandable within the iSite® Server Database. Once the DICOM and HL7 messages are translated and updated inside the iSite Database, then the data is available for viewing in the end-user applications namely iSite® Enterprise, iSite® Radiology, and iSuite.

Introduction: What is ConnectR?Introduction: What is ConnectR?

TRN-0000-02 Rev 12/14/04

ConnectR – HL7 Inbound Interface

RIS

ORMNW New Order1. New order -- status “S”

iSite DB

The Big PictureThe Big Picture

TRN-0000-02 Rev 12/14/04

RI

Merg

e

Toolk

it


RIS

ConnectR – DMWL Interface

MO

DA

LITY

ORMNW New Order 1. New order -- status “S”

2. DMWL Query Request

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

Data Flow: 2Data Flow: 2

TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LITY



3. DMWL Query Response

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK


TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm

ConnectR – Stentor -> IDX

Interface

C-STORE

DICOM MSMQ

SERIESREG

1. New order -- status “S”



4. Modality sends images – order status “I”


TRN-0000-02 Rev 12/14/04

1. New order -- status “S”




5. Update order – status “C”

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order


TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order1. New order -- status “S”





6. Order preliminary report – status “P”

ORU Preliminary Report


TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order

ORU Preliminary Report 1. New order -- status “S”





6. Order preliminary report – status “P”

7. Order final report – status “F”

ORU Final Report

HL7


TRN-0000-02 Rev 12/14/04

1.1. In the address box, type in the IP address of your Stentor Server In the address box, type in the IP address of your Stentor Server followed by “/idxconnectr/launch.asp”followed by “/idxconnectr/launch.asp”

2.2. Select “ConnectR” for Data SourceSelect “ConnectR” for Data Source

AccessAccess

TRN-0000-02 Rev 12/14/04

To access the Status Page:

1. Click on the “Monitor” bar

2. Click on the “Status” bar

Status PageStatus Page

TRN-0000-02 Rev 12/14/04

Within ConnectR, there are numerous system pairs 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.

Monitor StatusMonitor Status

TRN-0000-02 Rev 12/14/04

DICOM PAIR

HL7 PAIR

Internal

Communication

Pair

DMWL PAIR

System PairsSystem Pairs

TRN-0000-02 Rev 12/14/04

1. Source Systems designate the first point of data entry from an outside source (i.e. Modalities for the DICOM PAIR and RIS for the HL7 pair) into ConnectR.

2. The Source Systems pass the data to their associated Target System.

Source SystemsSource Systems

TRN-0000-02 Rev 12/14/04

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

Target SystemsTarget Systems

TRN-0000-02 Rev 12/14/04

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

Last MessageLast Message

TRN-0000-02 Rev 12/14/04

1. 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.

2. Take note or contact Customer Care if Queue is in the hundreds or thousands.

QSizeQSize

TRN-0000-02 Rev 12/14/04

Source System – receives studies from the modalities and passes the messages to the target system for processing.

Target System – processes and registers the messages from the modality into the database.

DICOM PairDICOM Pair

TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order


ORU Final Report

HL7

DICOM FlowchartDICOM Flowchart

TRN-0000-02 Rev 12/14/04

Source system - receives HL7 data messages (ADTs, ORMs ORUs).

Target system - processes HL7 data messages (ADTs, ORMs, and ORUs) and updates the database.

HL7 PairHL7 Pair

TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order


ORU Final Report

HL7

HL7 FlowchartHL7 Flowchart

TRN-0000-02 Rev 12/14/04

Target system – receives updates from iSuite and passes the messages to the source system for processing.

Source system – processes the updates and forwards the updates to iSite.

Internal PairInternal Pair

TRN-0000-02 Rev 12/14/04

Source system –1. Receives the query

or request from the Modality to perform a (DICOM C-Find)

2. Sends the translated data back to DICOM modality.

DMWL SourceDMWL Source

TRN-0000-02 Rev 12/14/04

Target system –1. Processes the query

(DICOM C-Find to iSyntax) and queries the iSuite database for patient exam data with exams in either “S” – Scheduled or “I” – In Progress

2. Send result back to the Source System

DMWL TargetDMWL Target

TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LIT

Y

ORMNW New Order

C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK

iSite

Pro

cessin

g

Module

MSM

Q -

iSuite

norm


Interface

C-STORE

DICOM MSMQ

SERIESREG

ORMSC Update Order


ORU Final Report

HL7

DMWL FlowchartDMWL Flowchart

TRN-0000-02 Rev 12/14/04

To access the Status Page:

1. Click on the “Monitor”.

2. Click on the “Message Log.”

3. 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.

Message Log PageMessage Log Page

TRN-0000-02 Rev 12/14/04

Step 1: Click on the down arrow to open up the drop down list and select Stentor to IDX Source.

Step 2: Select a date by clicking on the Calendar icon. The dates highlighted in black are the only dates which have messages.

Step 1 Step 2

This Source system is the receiving bucket for DICOM Series Registration messages. ‘Raw’ DICOM message is first received in the source system before being passed onto the corresponding target system for processing.

Stentor to IDX SourceStentor to IDX Source

TRN-0000-02 Rev 12/14/04

•This Source system will display the native DICOM messages from the Modalities as well as Heartbeat Messages.

•Date and Time stamp of the DICOM message that is displayed in the Source and Target message boxes. The displayed message is the 12th message out of a total of 6977 messages received for that day.

Date / Time StampDate / Time Stamp

TRN-0000-02 Rev 12/14/04

Use the String Filter field to type in any patient identifier for ConnectR to search through all messages and locate only those DICOM message (study series) for the patient.

String FilterString Filter

TRN-0000-02 Rev 12/14/04

•The Source Box indicates what that DICOM message looked like as it entered into the system.

•The Target Box indicates what that DICOM message looked like as it left this system.

•For this system Source and Target messages will look exactly the same.

DICOM Source / TargetDICOM Source / Target

TRN-0000-02 Rev 12/14/04

The arrow buttons:

1. Move you to the very beginning of the message log (message number 1 out of a total of 6977)

2. Move you back one message at a time

3. Move you forward one message at a time

4. Move you to the very end of the message log (message number 6977 of 6977)

1234

Play ButtonsPlay Buttons

TRN-0000-02 Rev 12/14/04

•Click on the grid button in either the Target Message pane or the Source Message pane to view the ‘raw’ DICOM study message in an easy-to-read

column format.

Grid ButtonsGrid Buttons

TRN-0000-02 Rev 12/14/04

The Grid page will display the data messages in a tree-like format that makes it easier to look up individual field names and its associate value.

Grid PageGrid Page

TRN-0000-02 Rev 12/14/04

Message ID: is a unique identifier that ConnectR assigns to each data message. These numbers aide in isolating a problem data message for trouble-shooting procedure calls (translations of the raw data message) in the Target systems.

Message IDMessage ID

TRN-0000-02 Rev 12/14/04

Step 1: Click on the down arrow to open up the drop down list and select Stentor to IDX Target.

Step 2: Select a date by clicking on the Calendar icon. The dates highlighted in black are the only dates which have messages.

The Target system receives DICOM Series Registration messages from the corresponding Source system. The Target system processes the messages by using procedure calls.

A procedure call is a set of instructions that translate the actual data message into recognizable fields in the database.

Step 1 Step 2

Stentor to IDX TargetStentor to IDX Target

TRN-0000-02 Rev 12/14/04

•The Source message box displays the ‘raw’ DICOM study message that is undergoing translation.

•The Target message box displays the translations and any errors if present.

•The Source and Target messages will look different when translation of the original DICOM message has occurred.

DICOM Source / TargetDICOM Source / Target

TRN-0000-02 Rev 12/14/04

The Grid page for the Target message will display the translated data messages in a tree-like format that is easier to look up individual field names and its associate value.

DICOM Target GridDICOM Target Grid

TRN-0000-02 Rev 12/14/04

•This Source system is the receiving bucket for HL7 messages before being passed on to the Target system for processing.

•As a requirement of the HL7 standard, every ‘raw’ HL7 message received is followed by an ACK (acknowledgement) message sent back to the RIS/HIS to indicate we have received the

message.

HL7 SourceHL7 Source

TRN-0000-02 Rev 12/14/04

•The Target system receives HL7 messages from the corresponding Source system. The Target system processes the messages by using procedure calls.

•A procedure call is a set of instructions that translate the actual data message into recognizable fields in the database.

Hl7 TargetHl7 Target

TRN-0000-02 Rev 12/14/04

•This grid page will display how ConnectR has converted the HL7 message into data fields that the iSite Database can understand and recognize.

HL7 Target GridHL7 Target Grid

TRN-0000-02 Rev 12/14/04

•This Grid will display the “raw” HL7 message in a easy to read table per HL7 field name and the value.

HL7 Source GridHL7 Source Grid

TRN-0000-02 Rev 12/14/04

What is HL7?“Health Level Seven develops specifications, the most widely used being a

messaging standard that enables disparate healthcare applications to exchange keys sets of clinical and administrative data.”

What is a “Message?”A message is a basic communication unit containing information that models a

real world event.How does one read a Message?

A message is structured like an organizational chart.

HL7 OverviewHL7 Overview

Message

Segment Segment Segment Segment

Fields Fields FieldsFields

component component

Common HL7 Message Types, Segments, and Fields based on HL7 Standards http://www.hl7.org

TRN-0000-02 Rev 12/14/04

DEFINITIONS• ADT is an (A)dmit, (D)ischarge, and (T)ransfer message that is generated

when a “Trigger Event” happens like a patient gets admitted, discharged, or transferred to another facility.

• ORM is an (Or)der (M)essage which includes new orders, order status changes, and order cancels.

• ORU is a Report/Result Message.

These values are sent in the Message Header (MSH) of an ADT, ORM, or ORU message and are considered message types.

Example:<11>MSH|^~\&|IMAGING|PSJMC|TDSresults|PSJMC|20030926000401||

ORM^O01|783744|P|2.3<13>

Message TypesMessage Types

Common HL7 Message Types, Segments, and Fields based on HL7 Standards http://www.hl7.org

TRN-0000-02 Rev 12/14/04

•PID is a Patient Identifier Segment•PV1 is a Patient Visit Segment•ORC is the top level Order Information Segment•OBR is the Order Detail Segment•NTE is the Notes and Comments Segment•OBX is the Report/Result Segment in an ORU Message

Example:<11>MSH|^~\&|IMAGING|PSJMD|TDS|PSJMD|

20030926133719||ORMÔ01|785465|P|2.3<13>PID||01000083270000160771229|555-55-555^^^PSJ||

ESCARDA^NARVARO||19000606|M|||1234 SOMEWHERE AVE^^^CA^90001-0000||213-456-7890|312-987-6543||||60771229|55555555<13>

PV1||I|4S^S460|||||FEB^SINATRA^FRANKÊ^^^MD^8888||||||||||IP||||||||||||||||||||||||||200102240414<13>

ORC|SN||100A-01011800||IP|N|1^^^200102241201^^S||200309261015|ÎNTERFACE^HIS||FEB^SINATRA^FRANKÊ^^^MD^8888<13>

OBR|||100A-01011800|9025^CT PELVIS 72193^MWA||| 200102241201||||||--..|||FEB^SINATRA^FRANKÊ^^^MD^8888||58944|||| 200102240414||CT|||1^^^200102240414^^S|ST1^TAPAIN^STEVEN^^^^MD^0275~SLP^POLISH^JOSEPH^L^^^MD^9828<13>

NTE|1||CT UROGRAM ,PT GOING TO OR 1230 TODAY<13>

<28><13>

HL7 SegmentsHL7 Segments

TRN-0000-02 Rev 12/14/04

Field Positions and Names• ADT, ORM, and ORUs

– PID-02 MPI Number– PID-03 MRN – PID-05 Patient Name– PID-07 DOB– PID-08 Sex– PID-18 Patient Account Number– PID-19 SSN– PV1-07 Attending MD– PV1-17 Admitting MD

• ORM/ORUs– ORC-02 or OBR-02 Order Number– ORC-03 or OBR-03 Accession Number– ORC-12 Ordering MD– OBR-04 Exam Code and Exam Description– OBR-07 Order Date and Time– OBR-24 Resource Name– OBR-25 Order/Exam Status

• ORUs– OBX-05 Result Text

HL7 FieldsHL7 Fields

TRN-0000-02 Rev 12/14/04

Merg

e

Toolk

it


RIS


MO

DA

LITY




C-FIND-RQ

HL7

DICOM

Source Target

DATA SP CALL

iSite DB

Merg

e

Toolk

it

DICOM

C-FIND-RSP Source

ACK


TRN-0000-02 Rev 12/14/04

Take the following steps if you use DMWL and there is no response:

1. Use iSite’s Modality Worklist to query the exam you are expecting. If the exam is not there, then

2. Look at DMWL Source and Target Systems in ConnectR to see if the query and results were returned.

To look up exams in Modality Worklist,

1. Select “Yes” in this prompt

2. Select the resources (or modalities) that you want the exams for by clicking on the

3. Next use the Primary Filters to select other

matching criteria.

Troubleshooting DMWLTroubleshooting DMWL

TRN-0000-02 Rev 12/14/04

The Source system receives the query or request from the modality. The Source system then passes the query to the Target system for processing.

The query is logged as a Data Message.


TRN-0000-02 Rev 12/14/04

The Target system receives query from the Source system and translates the request into a procedure call (SP Call). This procedure call queries the Stentor database for relevant exams and passes the patient list back to the Source system.

Message Type is “SP” Call

DMWL TargetDMWL Target

TRN-0000-02 Rev 12/14/04

The Source system sends the patient list back to the modality as an Ack Message.

Message Type is “Ack Message”


TRN-0000-02 Rev 12/14/04

Other Reasons to look Other Reasons to look into ConnectRinto ConnectR• Study sent but is not present in iSite Enterprise

– Search for the study by either the accession number, MRN, or patient name in the corresponding study interface target system

– Verify that the study exists in the interface with the correct patient values

– Verify if there are any errors logged with this study

• Order Exam and/or Report sent but is not present for the corresponding study in iSite Enterprise– Search for the order and/or report in the HL7 interface target

system by either the accession number, MRN, or patient name

– Verify that the order and/or report exists in the interface with the correct patient values

– Verify if there are any errors logged with this order and/or report

TRN-0000-02 Rev 12/14/04

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

Error Worklist: 1Error Worklist: 1

TRN-0000-02 Rev 12/14/04

There are various types of

errors, but begin by justlooking at the “Patient orExam Locked by AnotherUser” errors. 1. Select Date Range2. Type in “locked” in

String Filter.

3. Click on

Step 1

Step 2

Step 3

Error Worklist: 2Error Worklist: 2

TRN-0000-02 Rev 12/14/04

Most of these “locked” errors are trying to update the status of an exam. Therefore, let’s look at the logical progression of the life of an exam.

• OBR-25– “S” for Scheduled Exams

• Exams Scheduled by the RIS.– “I” for In-progress Exams

• Internal iSite Status to designate that iSite is actively receiving images for an Exam.

– “C” for Completed Exams• Designation by the RIS that a Study

(image acquisition) has been completed.• Completed Status always comes from RIS.

– “D” for Dictated Exams• Exams which Radiologists have dictated

reports but not yet transcribed.– “P” for Preliminary Exams

• Exams have Preliminary Reports, but not signed off yet by Radiologists.

– “F” for Final Exams• Exams with Finalized Reports that have

been signed off by Radiologists

Exam StatusExam Status

TRN-0000-02 Rev 12/14/04

• It is very important to check whether errors should be re-filed prior to re-filing. – For example, there may be an error message

that is trying to complete an exam to the ‘C’ – Completed Status. At a later time another message filed successfully and updated the exam with a report to a ‘F’ – Final Status. So the current status of this exam in iSuite is “F”.

– In this example, if the error message is re-filed, than the ‘F’ – Final Status will be overwritten back to a ‘C’ status for this exam which is undesirable.

Re-Filing ErrorsRe-Filing Errors

TRN-0000-02 Rev 12/14/04

Steps to Check Errorsbefore re-filing:1. Double left

clicking on the error will open up the message log.

Step 1

Re-Filing Errors: Step 1Re-Filing Errors: Step 1

TRN-0000-02 Rev 12/14/04

Step 2:Click on to view messages

Step 2


TRN-0000-02 Rev 12/14/04

Step 3: Use the play buttons to scroll through the Target messages until you find the error.

Tip: Start from the very end then scroll forward one message at a time until you have come to the error. Go back one more.

Step 3


TRN-0000-02 Rev 12/14/04

Step 4:This message is the actual error. Grid this to find the Accession number of the exam and the status that this message was trying to update this exam to.

Step 4


TRN-0000-02 Rev 12/14/04

Step 5: Verify Exam Status Value prior to Re-filing message•Log in to iSuite•Go to the Pt Record Tab•Go to Exam Tab•Enter ACC•Look at Exam Status.•If exam status is further down the chain of progression for an exam then DO NOT re-file error.

Step 5


TRN-0000-02 Rev 12/14/04

•To remove an Error, click

•To re-file an error, click

Step 6


TRN-0000-02 Rev 12/14/04

If your trouble-shooting requires additional assistance please call Stentor Customer Support (CARE) at 1-877-328-2808 or 1-877-328-2809.

Stentor Customer CAREStentor Customer CARE

TRN-0000-02 Rev 12/14/04 ConnectR Training. TRN-0000-02 Rev 12/14/04 1.Introduction: What is...

Documents

Transcript of TRN-0000-02 Rev 12/14/04 ConnectR Training. TRN-0000-02 Rev 12/14/04 1.Introduction: What is...