How to change Mirth Connect Custom Metadata

1. HL7 STARTER SCHOOL
MIRTH CONNECT
HOW TO CHANGE CUSTOM METADATA
www.HL7StarterSchool.com

2. MIRTH CONNECT – WHAT IS CUSTOM METADATA?
• Built into each Mirth channel.
• Used to speed up message searches.
• By default, when you create a channel – the following metadata is created:
• mirth_source
• mirth_type

3. MIRTH CONNECT – WHAT IS CUSTOM METADATA?
• When you run the channel, that metadata is quickly visible in the message view
section.
• Mirth uses the MSH header to retrieve that data for us.
• MSH-4 (sending facility)
• MSH-9 (message type)

4. PROBLEM
• The downstream system, ONLY accepts MDM^T11 messages.
• Our Mirth interface currently:
• Takes whatever is in MSH-9 and maps it to the mirth_type metadata.
• Takes whatever is in MSH-9 and send that to the downstream system.
• Demo…

5. SOLUTION
• Modify the Mirth interface channel to ignore whatever is in the mirth_type
custom metadata and hard code MDM^T11.
• Demo…

6. BONUS: WHAT IS MDM?
• An HL7 message :
• MDM – Medical Document Management – used to manage medical records by
transmitting new or updated documents, or by transmitting important status
information and/or updates for the record.
• Types
• MDM^T11: Document Cancel Notification
• MDM^T02: Document Creation
• TXA: the segment that contains the most important information about the document.
Document Type, etc.
MSH|^~&||Facility1|Facility2||20171121104800||MDM^T02||T|2.3
PID|||E3964^^^EPIC^MRN||ZZTEST^VIVIAN||||||||||||
TXA|||||115445157322^SMIRTH^SARAH^A^^^^^NPI^^^^NPI||||1154451573^SMIRTH^SARAH^A^^^^^NPI^
^^^NPI|||^^|||||||||||
OBX||RP||||
NTE||||