Troubleshooting with MOM Supporting features in MOM for

Trouble-shooting with MOM Supporting features in MOM for the evaluation of data content, data formatting, and messaging statuses

Background Knowledge HL 7 and XML formats Previous introduction to the MOM user interface and the Messages tab Familiar with the basic interaction between SCC and external applications

Presentation Description Describe the ESB architecture and the content of the MOM user interface Messages screen Since most installations will have ESB reporting components, the focus for this presentation will be on the TEST_RELEASED event to Result Reporting processes. • ESB-MOM replaces legacy outbound interfaces for all 4. 5 Lab as well as Standalone Gene implementations • For Gene standalone implementations, legacy inbound interfaces are replaced by ESB processes as well. Provide guidance for trouble-shooting issues of result content, formatting, and status

Outline • • • MOM/ESB Integration overview Events, sources, and destinations for Result Reporting MOM GUI and Messages tab First, show Result Reporting processing functions Second, describe functions for each process Next, go through three types of problems and where to check for data about the issue • CONTENT PROBLEMS • FORMAT PROBLEMS • STATUS PROBLEMS

Overview of ESB/MOM Message Flow

Events, sources, and destinations For this power point, we’ll focus on the TEST_RELEASED event, when a result in LAB/MIC is verified or a GIS report is signed out. MOM Messages view shows: 1. Parent event TEST_RELEASED with Source (e. g. ) 2. Destinations including RDC Result Data Collector 3. Destinations status response to MOM 4. Child event TEST_RELEASED based on payload from destination and routing configuration

Events, sources, and destinations Viewing the same data flow in MOM Messages tab

TEST_RELEASED event’s Sources and Destinations • Parent TEST_RELEASED • SOURCE: BB/BIO/FLW/CTG/DXP/MOL/HLA/IWS: • DESTINATION: • “WS. ESB. RES_COLLECTOR” = Result Data Collector • Child TEST_RELEASED • SOURCE: GIS/BB • DESTINATIONS: • • “WS. SCC. ESB. INT. IRR. LAB” = Result Reporting to Lab from Gene Suite or IWS “WS. SCC. ESB. INT. UPD. SWP” = Update Soft. Web. Plus “WS. SCC. ESB. INT. CLU. CSM” = Update Call list application “WS. CLIENT. OUT. HIS. RR” = Result Reporting to HIS (for BB, Standalone Gene Suite and for Supplemental results) • Parent TEST_RELEASED with SOURCE = LAB: • DESTINATIONS: • • • “WS. SCC. ESB. INT. IWS. NOTIFY” = Notify IWS of results for test with IWS component “WS. ESB. RES_COLLECTOR” = Result Data Collector “DB. SCC. LAB. STATUS. MONITOR” = Update Order Status Monitor db • Child TEST_RELEASED triggered when “WS. ESB. RES_COLLECTOR” returns data • SOURCE: LAB • DESTINATIONS: • • • “WS. SCC. OUT. AR. RR” = Result Reporting to Soft. AR “WS. SCC. ESB. INT. UPD. SWP” = Update Soft. Web. Plus “WS. CLIENT. OUT. HIS. RR” = Result Reporting to HIS

TEST_RELEASED event’s Sources and Destinations • Destination “WS. ESB. RES. COLLECTOR” • Pulls all data regarding the ordered test into a “canonical” format • • Patient data Order data Specimen data Result data • Discrete for LAB/MIC • Discrete/Textual for GIS technologies • This is easiest to view with the XML link provided with the Child TEST_RELEASED event

TEST_RELEASED event’s Sources and Destinations • Destination “WS. SCC. ESB. INT. IRR. LAB” • Result Reporting to Lab from Gene Suite • What does this do? • Calculates status • Updates • Status: FINAL, CANCELED, PENDING/PRELIMINARY • Component result value • “See” or “In. Process” or “Final” or “Cancelled” {technology} • Verification (Sign out) TS when status FINAL/CANCELED • Verified by (Sign out user ID, not viewable in Lab GUI) when status FINAL/CANCELED • Observation TS and Observer Tech ID updated for any status (Result type only)

TEST_RELEASED event’s Sources and Destinations • Destination “WS. CLIENT. OUT. HIS. RR” • Result Reporting to Lab from Gene Suite • What does this do? • Does test qualify to be sent to this HIS? • Output-specific rules, e. g. • Cancelled observation format • Inclusion of comments or placement of comments • • Create Lab/Mic/BB/Gene DSP segments Re-format to HL 7 Translation Services for HIS coded elements Pull genindex information, e. g. HIS Placer number

Result Reporting processes • ESB SND – SCC is transitioning to an ESB-based SND communicating interface. Required for • Stand-alone Gene implementations • Outputs with an embedded PDF

Result Reporting processes – Other • Other exceptional processes may be defined • E. g. CCHS example which checks final status of the entire order

Problem Topics Let’s look at three categories of reporting issues that might come up and how we may isolate the problem within one of these processes as viewed via the MOM Console • Data Content • Data formatting • Message processing status

Result Content Problems Example: missing or incorrect result for a component: Usually, this is an output specific issue and can be found by checking the Details section of the *. RR Destination:

Result Content Problems Example: missing or incorrect result for a component: • Troubleshooting suggestion to isolate the specific TEST_RELEASED message: • Use search criteria that are specific to the order, the TEST_RELEASED event, the destination, and choose Child message only

Result Content Problems Search criteria

Result Content Problems • Example: No URL sent with discrete result • Again, check the Details section of the Child TEST_RELEASED message. In this case, no note is viewed, so check the XML next – this is the payload provided by the Result Data Collector (RDC)

Result Content Problem • Example: No URL sent with discrete result • In this case, you find the clue:

Result Content Problem • Translation Service issues • Test codes • Field Mappings • Some Translation Service warnings are printed in the Details section. To see all in the trace, open the *. RR trace and select the Translation record:

Result Content Problem • Canceled Test results are converted by the *. RR interface: • • Auto-default dotted results Manually dotted results “. XYZ” results Check the Details or the before (XML) & after (HL 7)

Result Format Problems Which process creates the display formatting depends on the application: • Gene Suite display text is an ascii version of the actual report and is collected by the RES_COLLECTOR (RDC). • Look for the DSP sections in the XML of the child message

Result Format Problems Which process creates the display formatting depends on the application: • MIC display text is formatted now by the ESB *. RR interface. With legacy RR, this was performed by a MIC process and provided to the legacy RR. • BB display text is also formatted now by the ESB *. RR interface. • Go to the HL 7 (Green flag) or the Destination trace to see the DSP as the XML will not have the DSP

Result Status Problems Trouble-shooting a missing result or checking on a Problem List item You may want to see if a message has been sent and if not what may be holding it up in MOM. To do this, you will check to see if the messaging in MOM is in a Delivered status and if the HL 7 message (Green Flag icon) has been set.

Result Status Problems First, know the possible Destination statuses returned to MOM: OK DATA_ERROR NOT OK, required intervention TRANSPORT ERROR NOT OK, may be temporary WAIT_FOR_ACK OK, until it isn’t UNDELIVERABLE OK SKIPPED = MOM skipped this destination OK SKIPPED_BY_DEST = Destination skipped further processing OK • SKIP_FAILED Warning, check Details, may be setup issue • RESOURCE_BUSY = Temporary application problem, e. g. locked record NOT OK, often temporary • TIMEOUT_ERROR NOT OK, often temporary • •

Result Status Problems Message life cycle in terms of the status: when an event message is sent to MOM such as a TEST_RELEASED event: -MOM will give it an initial SEND status. -Once the message is sent to the Destinations, a PENDING status is assigned. HAPPY DAY SCENARIOS -If the message is processed without error a DELIVERED status is assigned. -If the message has no appropriate mapping it is placed in a UNDELIVERABLE status NOT SO HAPPY DAY SCENARIOS -If there is a problem that requires MOM to automatically re-send, then the status of WAIT is assigned. -But if there is a unavoidable problem or the re-send limit is exhausted, then the message is placed in a HOLD status and must be handled manually, either Canceled or Manually sent.

Result Status Problems MOM will place a message in DELIVERED status when it receives the following Destination Result codes: • OK, see the green flag icon showing the HL 7 message • SKIPPED_BY_DEST (Based on current configuration) • SKIP_FAILED (Skipping event does not warrant Holding up messaging)

Result Status Problems - WAIT MOM will place a message in WAIT status when it receives the following Destination Result codes: • TRANSPORT ERROR (TCP communication error, transport exception in Stack trace) • RESOURCE BUSY (Record is locked) • TIMEOUT ERROR (No response by Destination) MOM will retry sending the message at a periodic rate until message is processed or until retry max is reached and at that point the message is put in a HOLD status. Also, if your interface is supports sending Number Assignments, the message status WAIT_ACK indicates that the messaging is waiting for the returned HIS Placer # before processing further.

Result Status Problems - HOLD MOM will place a message in HOLD status when it receives the following Destination Result codes: • DATA ERROR (Missing HIS#, SOAP Fault) • Re-sending attempts reaches the max for TRANSPORT ERROR, RESOURCE BUSY, and TIMEOUT ERROR statuses.

SUMMARY • ESB-MOM is an architecture for integrating all applications, both internal and external • MOM user interface provides a view that reflects the message-oriented design • ESB-MOM’s RDC and RR processes mirror legacy RR functionality. The trace information is stored in a database. Display and search capabilities are an enhancement from previous flat trace files. • Filtering for the child TEST_RELEASED event will provide most trouble-shooting information with least effort • Message status HOLD will require manual intervention and will hold up delivery of subsequent events with the same grouping identifier.