1. Introduction to the MOM Console
By Richard Newton SCC HIS Interface Product Specialist

2. Introduction to the MOM Console
Using the MOM (Message Oriented Middleware) Console
Accessing the MOM Console
Messages in the MOM Console
Message status and meanings
Searching in the MOM Console
Routes and Attributes in the MOM Console
The ‘Problems List’ in the MOM Console
Reconciling and reporting issues found in the MOM Console

3. What is the MOM Console?
The MOM Console is your one-stop-shop for all things HIS interfaces. It provides tools necessary for searching event based messages and status’ and aids in troubleshooting HIS interface related problems.

4. MOM System Integration
MOM is the Middleware that sits in a layer between the applications and the EIS/ESB processes.

5. Who should use the MOM console?
The MOM Console is for anyone who has a need to verify delivery of messages to external systems. It is especially useful for anyone who is charged with the responsibility of identifying and reconciling HIS interface related issues pertaining to delivery of messages to and from external systems.
HIS
SCC

6. Accessing the MOM Console
The MOM Console is accessible two ways. The primary way to access the MOM console is using the SoftLab ‘Tools’ menu. A new browser window appears with the login dialog.
The secondary way to access the MOM console is through the ‘SoftDMI’ application. A clickable link to the local instance of MOM is present at the bottom of the SoftDMI application window. The link takes you directly to the MOM login dialog.

7. Searching in the MOM Console
Following successful login, the console will appear. The user will be presented with search tools and a list of the latest event based messages processed by the system.
Search criteria
Message List

8. MOM Search Criteria Content Specific Routing, Event, Status
The MOM Console offers a healthy list of searchable criteria. Up to two message content specific attributes and various other routing, event, and status values can be used in a search.
Content Specific
Routing, Event, Status

9. Search results
The MOM Console presents search results based on the attributes selected listed by the newest events top-down. Each event displays a message ID, event code, message links, attributes, and current status.

10. What can you search for in the MOM console?
The MOM Console allows searches based on a combination of message attributes, routes (interfaces), event codes, and status. Expand the message to show route details.
Expanded message showing all evaluated routes.

11. The Message Attributes List
The message attributes are listed in each event based message in the MOM search results. The attribute values can easily be seen by clicking the “Attributes view” icon.
The number of attributes displayed per page is adjustable.
Message attributes
“Attributes view”

12. Searchable message content attributes
The MOM Console provides the ability to search on attributes found in the attributes list of MOM messages. Attributes reflect record specific data elements of the event being processed.
ADT_PATIENT
ADT_VISIT
ALLTESTS
BILLING
CORRID
ELR_TEST
MRN
ORDER
ORIGIN
REDUNDANT
SENDER
SEQ
TEST
TIDS
CLINIC
DEPOT
DESTMSGID
DUPLICATED
DUPLICATED_DOCTOR
EVENT
HIS_ORDER
HIS_PATIENT
IN-MSG-ID
LAST_REPORT_IN_CHAIN
MODULES=LAB, ON_HOLD_ORDER
ORDERABLE_OUTSIDE
ORDER_TYPE
OUTREACH
PATIENTTYPE_PREFIX
REGION_PREFIX
RELATED_SYS
RESULTS_REMOVED
SPM_DUMMY
SUPPLEMENTAL
TERMINAL
TEST_STATUS
USER

13. Filtering by message content attributes
To search by a content specific attribute such as an MRN, the attribute name and value can be defined as search criteria. Simply enter the attribute name with exact syntax and the expected value in the ‘Attribute name/value:’ fields. You may enter two attributes and specify whether the pair of attributes are to both appear (AND) or either one to appear (OR) by checking/unchecking the AND (OR is default) checkbox. If you use attributes that are not patient or order record specific, you will need to check the ‘Adv. Attr. Search’ checkbox.

14. Viewing the HL7 output of a MOM message
Messages appearing in MOM that have processed and delivered messages to a destination will present a green flag as a link to view the actual HL7 message output.

15. MOM message status
The MOM Console displays the current status of each message in the far right column of search results. These are the possible status and their meanings.
SEND [Message is waiting to be sent to its destination]
WAIT [Message is waiting for the pending processing of another message]
WAIT_ACK [Message is waiting pending the assignment of an HIS order number]
DELIVERED [The message is delivered to its destination, processing has finished]
FAILED [The attempt to send the message has failed]
CANCELLED [The message processing has been cancelled manually by user before it was delivered]
HOLD [The message is placed on ‘hold’ due to some error that causes a processing timeout]
IN_PROCESS [The message is being processed for delivery to its destination]
REPLACED [The message was replaced by a newer message]
REPROCESS [The message has been flagged for reprocessing by a user]
RESEND [The message has been triggered by a user to be resent to its destination]
SKIPPED [The message was manually skipped by a user]
SKIPPED_BY_DESTINATION [The message did not qualify to be sent to the listed destination]
SKIP_FAILED [The attempted manual skip failed to process]
UNDELIVERABLE [A message did not qualify to be sent to any of the evaluated destinations]

16. MOM final status’ with no further processing
Final statuses of message (no more delivery attempts will be made, status will not change unless user perform manual action): CANCELLED, DELIVERED, FAILED, REPLACED, SKIPPED, SKIPPED_BY_DEST, UNDELIVERABLE
Temporary statuses (system will made attempt to deliver message and change its status): IN_PROCESS, RESEND, SEND, WAIT, WAIT_ACK

17. Which status’ warrant attention
When reviewing the status of a message, the type of status may imply a need for attention or action. These are the more notable status types that should be considered a need for investigation or other action in an attempt to reconcile a delivery issue.
WAIT_ACK
FAILED
HOLD
SKIP_FAILED
[May indicate that the HIS is not responding to an order number assignment request. Check the HIS.]
[Some issue has caused the message not to be delivered. Setup or other issues may be responsible. Some investigation is required to determine the root cause of failure. Using the ‘Resend’ option after a setup correction can be used to reprocess the message. ]
[The message is placed on ‘hold’ due to some error that has caused a processing timeout]
[Warning, check Details. May indicate a setup issue.]

18. Filtering by message status in MOM
The MOM Console allows the user to filter on many different criteria including the current message status. To find all messages of a specific status like ‘FAILED’ for instance, the user can simple select the status in the “Destination Status” list box.
Note: Any combination of status, route, sender code, event code, and attribute can be used to narrow down messages of a particular status having the specified search attributes.

19. Enter keywords here to find a route quickly
Filtering by interface route
Often times a user may need to view all messages destined for a particular route (interface). This could be an interface to an internal or external system. Filtering by interface route is as easy as selecting the route or multiple routes in the “Destinations:” list box. Simply click in the desired route or Ctrl-Click multiple routes to select the ones to filter on. Click filter and the resulting output will be for those routes only.
Note: There is a search box above the Destinations list box. Enter a term like ‘RR’ or ‘EPIC’ to quickly find the desired route in the list box. Any combination of routes and other attributes can be used. No route selected will enable all routes in the search.
Enter keywords here to find a route quickly

20. Routes specific to internal integration
SCC_INT_GIS_IOE – the LAB->GENE integration
SCC_INT_LAB_IOE – the GENE->LAB integration
SCC_INT_GIS_NOTIFY – notify GENE about new results in Lab for GENE order
SCC_INT_GIS_ORDMV – notify GENE that order was moved
SCC_INT_GIS_PATMOD – notify GENE patient was modified
SCC_INT_LAB_SPECUPD – specimen updates in LAB (e.g. from GENE)
SCC_INSTANT_BILLING – sends notification to AR about charges from GENE
SCC_INT_CSM_TCL – notification to ‘Call List’ from GENE and LAB (TEST_CALLED events)
SCC_INT_CSM_UPD – notifications to ‘Call List’
SCC_INT_GIS_TCL – notification to ‘Call List’ from LAB to GENE
SCC

21. Click the dropdown arrow to expose all available event codes.
Filtering by event. What are events?
The MOM Console processes messages by ‘event’. Events represent an occurrence in the sending software module. Whenever a reportable ‘event’ occurs in the module such as a specimen collection or verification of results, the corresponding event is sent to ESB/EIS and is viewable in the MOM console as a message to be processed and sent to a destination. MOM users are able to filter base on ‘Event’ by clicking the view arrow and selecting the appropriate event from the list. Multiple events can be selected.
Click the dropdown arrow to expose all available event codes.

22. What events are processed in MOM?
These events can be found in the ‘Event Code’ drop-down list in MOM
Specimen Events
SPECIMEN_ADDED
SPECIMEN_BARCODED
SPECIMEN_COLLECTED
SPECIMEN_RECEIVED
Test Events
TEST_ADDED
TEST_CALLED
TEST_CANCELED
TEST_RELEASED
TEST_CALLED_MODIFIED
Order Events
ORDER_ADDED
ORDER_MODIFIED
ORDER_RECEIVED
ORDER_RESEND
Patient Events
PATIENT_ADDED
PATIENT_DELETED
PATIENT_MERGED
PATIENT_MODIFIED
Visit Events
VISIT_ADDED
VISIT_DELETED
VISIT_MODIFIED
VISIT_NUM_CHANGED
DMI Events
DMI_ACTION_RESULTED
DMI_CONTAINER_ACTION
DMI_TEST_CANCELLED
DMI_TEST_RESULTED

23. Identifying Issues in MOM
Some issues are process related and can be identified by reviewing the ‘Details’ of the event by expanding the event tree:
The MOM Console will do it’s level best to inform you of the exact problem encountered. If you need help understanding the meaning of an error description, contact your SCC support specialist.

24. Issues that cannot be corrected by setup or other standard maintenance.
Some issues cannot be resolved by performing standard maintenance. If you encounter a ‘SOAPfault’ for instance, SCC will need to address this issue and manually reprocess the message event. Certain errors are related to the interface configuration and ESB/EIS functionality rather than setup data and can only be addressed through your SCC support resources.

25. How to report MOM related problems to SCC
We encourage MOM users to gather certain details of the issue when help is needed. There are key elements that will facilitate the support request process and help provide a speedy resolution. When entering a support task for a MOM related issue, we like to see these references:
Describe the workflow that led up to the issue and what your expectation was. All of these details should be in a document attached to the support task…
MOM message ID
Details of the error
Event Code
and Status

26. Resolving an Issue Yourself…
Many issues that prevent proper message processing in MOM can be resolved by an LIS administrator. For instance, SoftLab setup issues that cause the inability to translate key values often lead to a HOLD status or other status that may prevent further processing. Using the error message given in the ‘Details’ of the MOM message, it is possible to easily identify the cause of the processing failure. Correcting the issue and reprocessing the MOM message should resolve the processing error and deliver the message.

27. Reprocessing a MOM Message
To reprocess a MOM message after manual correction of an issue that caused the message processing error, simply select the message checkbox and the type of reprocessing you wish to use and click “Resend selected”.

28. What is the MOM Problems List?
The MOM Console has the ability to capture and list critical problems in a ‘problems list’. This function is intended to provide MOM users with a way to quickly and routinely identify and reconcile messages that encounter critical errors.

29. The problems list is searchable
The MOM Problems List is searchable using many of the same criteria used to find MOM messages (Attributes, Sender Code, Event Code, Problem Category, Status, and Route).

30. Example Problems List output

31. What is a ‘Problem Code’?
A ‘Problem Code’ is a searchable category that allows a user to filter down problems list results to a specific problem category such as a ‘Timeout Error’. Problem codes typically represent system level events that are not specific to message data elements but instead represent the overall outcome of the problem encountered.

32. What is a ‘Processing Code’?
A processing code identifies a ‘cause’ of the problem. For example, an ‘MISMATCH’ processing code will indicate that the issue is related to a mismatch in patient demographics that is preventing the message from processing. X

33. Identifying Issues using the “Problem Code”
The problem code can be used to identify and resolve issues. From problems list reports to troubleshooting messages related to key identifiers, the MOM console is a valuable tool for interface administrators.
Identifying problems made easy… Users have the opportunity to correct setup issues or other problems and resend the message to resolve the problem.

34. Problems List Actions
Use the actions buttons to mark or process messages that appear in the problems list.
Mark as reviewed (allows flagging of selected messages as reviewed)
Resend selected (provides the option to reprocess a message after manual correction of the issue)
Cancel selected (allows a user to cancel the selected message)
Export selected (provides the option to export the selected messages to a CSV file)
Category (provides the ability to add or update a category for the selected messages)

35. Codes reported in the Problems List.
The Problems List captures and lists MOM messages that have encountered an issue that prevented it from processing or messages that present a warning to the user/administrator. These are the searchable problem codes:
TRANSPORT_ERROR
DATA_ERROR
SKIP_FAILED
TIMEOUT_ERROR
RESOURCE_BUSY
PROCESSING_CODE
WAIT_ACK
TECHNICAL
Processing codes:
ADDHISORDNUM_ERROR
ADJUSTED_VALUE
AMBIGUOUS_HIS_MATCH
BILLING_MERGED
CANCELLATION_ERROR
LAB_SPEC_ERROR
LAB_WS_ERROR
MEDIA_HTTP_ERROR
MISMATCH
MRN_MERGED
NOT_MATCHED_BILLING
CLINIC_ERROR
CONVERSION_ERROR
CONVERSION_WARNING
CRITICAL_MISMATCH
DOCTOR_ERROR
NOT_MATCHED_MRN
NUMBER_ASSIGN_ERROR
RECORD_DELETED
RECORD_DELETE_DENIED
RECORD_REACTIVATION
RELATED_ORDER_NOT_EXIST
DUPLICATE_HISNUM
GENE_WS_ERROR
HISNUM_CHANGED_ATTEMPT
IMPLICIT_MRN_MERGED
INCORRECT_TRANSACTION
RESULT_ERROR
TEST_ERROR
TEST_REJECTION_ERROR
TS_ERROR
VISIT_MOVED
VALIDATION_ERROR

36. We’re Here to Help… Support Tickets Implementation Specialists
HIS Product Specialists
The Knowledge Base
SCC

38. Please remember to take a few moments to fill out the session survey
Please remember to take a few moments to fill out the session survey. You can find the QR code in your Conference Brochure as well as hyperlinks to the survey online at with the SNUG 2019 handouts.