The MOM Console Troubleshooting and Tracking Problems Troubleshooting

The MOM: : Console Trouble-shooting and Tracking Problems

Trouble-shooting with MOM Scouting the LIS using MOM, you will uncover

OBJECTIVES Objectives of this presentation • What issues and “Problems” do we monitor via the MOM: : Console? • What are Problem Codes, Processing codes, and Problem Categories • Introduce the MOM: : Console Problem List • What issues are not written to the Problem List and thus cannot be monitored?

Topics • • MOM Problem Tracking Features Main Message screen: a user can investigate how an action in one application did not produce the expected outcome in another application or external system. Problem lists screen: a user can search here for errors and warnings that occurred during MOM message routing. E-mail notification of Problems Tracking problems using Problem Categories

What you should know This presentation builds on a basic knowledge of: – SCC ESB model: – Have accessed the MOM: : Console and have some familiarity with the Messages screen – Basic idea of what SOAP and XML and WSDL are

SCC ESB Design

MOM at SCC MOM • Message-Oriented Middleware • MOM is SCC’s message broker of the XML message packets sent on the ‘bus’ between applications and to/from external applications

MOM at SCC MOM “Problems” are trapped based on the status returned by the Destination process The issue that you find may not be a MOM “Problem”. It may be because the parent event or a child event did not occur due to a setup or configuration rule.

MOM: : Console Messages View MOM opens to the main Messages screen

MOM Message Display How is the Messages screen organized in relation to the message flow? (HANDOUT)

Messages View: Filter Criteria • Messages Filter Form: – – – Attributes: Order#, Test Code, Billing# Event code: SPECIMEN_RECEIVED Sender: ‘LAB’, ‘DXP’, ‘HIS. BLAB’ Destination: ‘WS. ESB. CLIENT. OUT. HIS. RR’ Destination Status: ‘HOLD’

APPLICATION EVENTS Message Filter Form: EVENT CODES New Event Description ORDER_ADDED Order (accession) added to a system. TEST_ADDED Test is created in a system. TEST_CANCELED Test is canceled in a system. SPECIMEN_COLLECTED Specimen is collected SPECIMEN_RECEIVED Specimen is received ORDER_CANCELED Entire order (accession) is cancelled in a system. ORDER_STATUS_CHANGED Status of the entire order has changed in a system. TEST_RELEASED Result is verified/signed out. VISIT_ADDED Visit (billing number) was created/added to a system. PATIENT_ADDED Patient MRN was created/added to a system. PATIENT_MODIFIED Patient MRN and/or patient demographic data was modified.

Routing Issue For outbound messages: • Check that the message event was sent from the application for the ordered test. (Not a MOM Problem) • If not routed to the expected Destination, check the routing rules (Logical Issue, not a MOM Problem)

Order Index Check Order Index to see if HIS# is present (Not a MOM “Problem”)

Types of searches • My experience, two type of searches: – Check for problem statuses, ‘HOLD’, for an interface or set of interfaces – Check status for a specific event(s) on an ordered test

Monitoring “HOLD” statuses • Example of a search for ‘HOLD’ on an interface

Message Scenarios Outbound: “The Good” Scenario HL 7 message is sent!

Message Scenarios Outbound: “The Ugly” Scenario A Stack Trace error may be returned and no HL 7 message sent. In most cases, this is a bug

HOLD link to Problem List • HOLD link in the Message status links to the Problem record in the Problem List (HANDOUT) • Problem List Message ID links back to the problematic message (This example is just a link back to the same message)

Message Scenarios Outbound: “The Bad” Scenario Note: some unexpected outcomes are not errors. No Problem or Processing codes are present and this does not show up, currently, in a Problem List Result Code = SKIPPED_BY_DEST Processing Code = <empty>

Message Scenarios Inbound: “The Good” Scenario Success is the posting of data: Result Code = OK Processing Code = <empty>

Message Scenarios Inbound: “The Bad” Scenario ADT data are not consistent with database information Result Code = SKIP_FAILED Processing Code = CRITICAL_MISMATCH

Message Scenarios Inbound: “The Bad” Scenario A message does not post due to a unexpected setup issue Result Code = SKIP_FAILED Processing Code = TEST_ERROR

Message Scenarios Internal: “The Ugly” Scenario A service may not be activated Result Code: TRANSPORT_ERROR Processing Code: <empty>

Problem Codes • MOM is configured to respond in different ways based on the Problem Code (subset of Result Codes) • Problem Codes and Processing Codes provided by the Destinations are also what defines a Problem to be viewed in Problem List logging (HANDOUT)

Problem List Search filters at the top and the list of qualifying Problems in the lower portion of the screen

Using Problem List Search filters and display adjustments

Problem and Processing Codes • Problem and Processing Codes in Problem List

Using Problem List Processing Codes in Problem List Search display

Processing Codes Processing Code – Partial List

Problem List Search Example Search for test code errors with results coming back from Quest Reference Lab this month. • • Date range: Sender code: Processing Code: Details: 4/1 to current QUEST REFLAB_PROBLEM “Cannot convert test codes”

Problem List Search Example Search for errors communicating from Gene to Lab when attaching a test or collecting a specimen in Gene • • Date range: 4/1 to current Event codes: SPECIMEN_COLLECTED, TEST_ATTACHED Problem Code DATA_ERROR Destinations: *_ESB_INT_IOE_LAB, *_ESB_INT_SPEC_LAB

Problem List Search Example Search for errors for messages destined for Wyndgate • • • Date range: 4/1 to current Problem Code: ALL Destinations: *_ESB_OUT_HIS_WYNDGATE In this example of a temporary TRANSPORT_ERROR, clicking on the Message ID brings up the Message screen showing that the message was sent eventually.

Problem Notification You may see notification(s) for monitoring problems by a programming group

Problem Notification Create e-mail recipient for Problem Notification

Problem Notification Set Notification Conditions

Problem Notification E-mail content example

Problem Notifications that need further evaluation are entered in task descriptions

Problem Categories Created to group problems for: – – Searching in Problem Lists for tracking and review Login selection – focuses output to messages and problem list Common groupings: Task Number, Message Flow (“Inbound”), Warn vs. Err Create problem report (to be discussed next)

Problem Categories • Creating Problem Category from Problem List – Commonly used by programming to track errors related to a task

Problem Categories Assigning Problem Category to a Processing Code – Used to group Processing Codes for Problem List search – Assign to a Problem Report

Problem Categories Search Problem List by Problem Category

Destination Categories Destination category is a grouping of MOM destinations E. g. all interfaces that handle a TEST_RELEASED event to an external system. In most cases, just the RDC (result data collector) and the *. RR interface

Problem Reports • Transport Reports – List Problems connected with Problem and Processing codes – Create Transport Report by defining a Problem Category and a Destination Category for it. – Transport Reports produce the same screen and output as a Problem List search but are created at set intervals without repeating the entry of search criteria. • Technical Reports – Backlog per destination exceeds 500 messages – Messages not processed for 20 minutes

Future Problem Reporting A re-design to accommodate larger numbers of both warning and error processing codes is being evaluated now.

Future Problem Reporting Second level of Future Problem Report View

Corrective Actions Corrective Action • Fix setup file or configuration and resend • Message cancelation from MOM to release other messages on HOLD when grouped • Inbound, it is possible to edit or add an XML message and resend

Corrective Actions Editing XML message

Problem Handling with MOM • Summary: – Message queries provides transaction statuses and details specific to the processing flow per event • Discover logical or setup issues that are not MOM Problems – Problem lists provides an evaluation mechanism to check error volume and mark problems as reviewed – Processing Codes provide a more granular way to represent both warnings and errors, regardless of processing status of the event. – Problem Notification provides an alert system

MOM Problem List Functionality

The end of the trail