1. Trouble-shooting with MOM
Describe the Interfaces and features in MOM pertinent to trouble-shooting result reporting

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

3. What does ESB/MOM Messages replace?
Flashback to the “resrep” trace

4. Presentation Description
Describe the ESB architecture and the content of the MOM user interface Messages screen
Describe the Result Reporting processes that are the destinations for the TEST_RELEASED event.
Search basics for four issues:
routing based on attributes
result content
Formatting
event status

5. Overview of ESB/MOM
Message Flow – MOM is a Message Router

6. TEST_RELEASED event routing
The presentation example event is the TEST_RELEASED event, when a result in LAB/MIC/BB is verified or a Gene test is signed out.
Diagram shows the MOM process steps:
Parent event TEST_RELEASED with Source Application (e.g. LAB)
MOM to Destinations, e.g. RDC Result Data Collector
Destinations status response to MOM
Child event TEST_RELEASED based on payload from destination and routing configuration, e.g. RR interface
Note: routing for events “*_RESEND and TEST_CALLED” involve the same RR components

7. MOM view of TEST_RELEASED routing
Viewing the same data flow in MOM Messages tab

8. TEST_RELEASED routing configuration
How is MOM Routing Configured?
Setup Mappings

9. TEST_RELEASED event’s Sources and Destinations – Integration

10. TEST_RELEASED event’s Destinations
Destination “WS.ESB.RES.COLLECTOR”
Nomenclature: unchanged from system to system
<WS or DB><SCC.LAB or ESB><IN or INT or OUT><SERVICE>
always mapped in MOM from the base “CMN_SIN_RDC” interface in SoftDMI
When conversing, often shortened to “RDC”
Other Collectors CMN_SIN_{PDC},_{VDC},_{XDC}
Pulls all data regarding the ordered test into a “canonical” format
Patient data
Order data
Specimen data
Result data
Discrete for LAB/MIC/BB/GIS technologies
Textual for GIS technologies only

11. TEST_RELEASED event’s Destinations
Destination “WS.ESB.RES.COLLECTOR”
Canonical after XML re-formatting: canonical is easiest to view with the XML link provided with the Child TEST_RELEASED event

12. TEST_RELEASED event’s Destinations
Destination “WS.{HIS}.OUT.HIS.RR”
Result Reporting to external system
Nomenclature: substitute HIS acronym in place of {HIS}
Configured based on Specifications from a model in SoftDMI, then mapped in MOM to the same name
When conversing, often shortened to “RR” interface
Specification Rules and Content applied here
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 display segments
Re-format to HL7
Translation Services for HIS coded elements
Pull genindex information, e.g. HIS Placer number

13. TEST_RELEASED event’s Destinations
Destination “WS.{HIS}.OUT.HIS.RR”
Configuration for all components is in SoftDMI

14. TEST_RELEASED event’s Destinations
Destination “WS.SCC.ESB.INT.IRR.LAB”
Result Reporting update from Gene Suite to Lab
Nomenclature: unchanged from system to system
always mapped in MOM from the base “SCC_INT_LAB_IRR” interface in SoftDMI
What does this do?
Post status to any matching components
Updates
Status: FINAL, CANCELED, PENDING/PRELIMINARY
Component result value
“See” or “InProcess” or “Final” or “Cancelled” {technology}
Verification (Sign out) TS when status FINAL/CANCELED
Verified by (Sign out user ID) when status FINAL/CANCELED
Observation TS and Observer Tech ID updated for any status (Result type only)
Note that updates by this interface are triggered by other events, e.g. REPORT_REACTIVATED

15. Result Reporting processes - Other
ESB Communication interfaces– SCC is transitioning to ESB- based
Nomenclature “SCC.OUT.{HIS}.FRM.SND”
Configured based on Specifications from a template in SoftDMI, then mapped in MOM to the same name
Often referred to as “SND”
Required for
Stand-alone Gene implementations
Outputs with an embedded PDF

16. Result Reporting processes – Other
Other exceptional processes may be defined
E.g. CCHS example which checks final status of the entire order before composing the result message

17. Problem Topics First, mention search capabilities in the Messages view
Second, discuss four categories of reporting issues that might come up:
Routing based on message data
Data Content
Data formatting
Message processing status

18. First, Search Features
Search criteria

19. 1. Routing based on Attribute
Issue: Message not sent
Routing based on Attributes is done both by MOM and the Destinations:
MOM: Check the Green two-headed icon
Destinations: determine if the record qualifies to be processed:
The Details in MOM use to be somewhat cryptic; they are getting better

20. 1. Routing based on Attribute
Routing based on Attributes is done both by MOM and the Destinations:
MOM: Check the Green two-headed icon
Destinations: determine if the record qualifies to be processed:
The Details in MOM use to be somewhat cryptic; they are getting better

21. 1. Routing based on Attribute
Use the following features to quickly find attributes
The Details in MOM use to be somewhat cryptic; they are getting better

22. 2. Result Content Problems
Issue: missing component result or improper discrete data
Two places in MOM messaging to check:
Details returned by RR interface
XML from the Child event (Data Collector info)
The Details in MOM use to be somewhat cryptic; they are getting better

23. 2. Result Content Problems
Two places in MOM messaging to check:
Details returned by RR interface
XML from the Child event (Data Collector info)
The XML provides additional flagging information

24. 2. Result Content Problems
With experience you will find search criteria that will pinpoint the message that contains appropriate feedback.
With content-type problems, I use search criteria that are specific to the order, the TEST_RELEASED event, the destination, and choose Child message only

25. 2. Result Content Problems
Second Example: No URL sent with discrete result
If no useful information in the Details section, check the XML from the Data Collector.

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

27. 2. 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:

28. 2. Result Content Problem
Canceled Test results conversion by the *.RR interface:
“.XYZ” results may not be configured to be sent
Check the Details or the before (XML) & after (HL7)
Configuration is in DMI for this functionality under the Miscellaneous section.

29. 3. Result Format Problems
Issue: text wrapping incorrectly
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

30. 3. Result Format Problems
Change from legacy Result Reporting
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 HL7 (Green flag) or the Destination trace to see the DSP as the XML will not have the DSP

31. 3. Result Format Problems
For the programmers out there, viewing the Style Sheets
You can view the style-sheets for the display text build if you want...

32. 4. Result Status Problems
Issue: result not sent
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.

33. 4. Result Status Problems
First, know the possible Destination statuses returned to MOM:
OK  OK
DATA_ERROR  HOLD status, required intervention
TRANSPORT ERROR  WAIT may be temporary, then HOLD
WAIT_FOR_ACK  OK, until it isn’t
UNDELIVERABLE  OK, but not for RR (error in configuration)
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  WAIT may be temporary, then HOLD
TIMEOUT_ERROR  WAIT may be temporary, then HOLD

34. 4. 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.
HOLD status should be referred to SCC to investigate – these go to the Problem List

35. 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
Four key interfaces were reviewed: RDC, HIS.RR, IRR.LAB, and SND
The trace information is stored in a database. Given a reasonable knowledge and experience with using the Messages screen in MOM, this view should provide an easy and quick utility for investigating resulting issues