Slide 1

Yorkshire Centre for Health Informatics Detailed Walkthrough of the NHS MIM, and Message Implementation Manual for Discharge Yorkshire Centre for Health Informatics

Slide 2

Acknowledgements This presentation was created by the Yorkshire Centre for Health Informatics (YCHI) with supporting materials from NHS Connecting for Health and HL7 UK.

Slide 3

Learning Objectives To be able to navigate the MIM, and use it as a support tool for developing future eHealth systems

Slide 4

Presentation Outline What are the definitions of HL7 roles, trigger events, and interactions? What data types are in the MIM? What artifacts are available for each message? What do the MIM version numbers represent? What do each of the sections of the MIM look like? What domains does the MIM cover and not cover?

Slide 5

What are the definitions of HL7 roles, trigger events, and interactions? Application Roles The role of application and systems in the sending and receiving of messages. Trigger Events Determine what causes a message to be sent an explicit set of conditions that initiates the transfer of information. For example: receipt of another message; end of a care event; or, completion of a report. Interactions Details the data flows, trigger events and rules, what information goes where and when, and who sends what.

Slide 6

Map of Data Types in HL7 V3 Tim Benson (2010)

Slide 7

Data Types in HL7 V3 A larger version can be found in the Resources for this RLO.

Slide 8

What data types are in the MIM? Simple Types Boolean Integer Text and Encapsulated Data Demographics Person Name Postal Address Codes Identifiers Quantities Dates and Times Point In Time Mr John Smith

Slide 9

What artifacts are available for each message? An R-MIM provides a diagrammatic view of the model that underpins a message. Tabular View provides additional details about the various classes and attribute that are contained within a message model. Interaction definitions specify the links between a number of other components and artefacts that support the sending of an actual communication.

Slide 10

What do the MIM version numbers represent? Ian Townend

Slide 11

What domains does the MIM cover, and not cover? Common Administrative Alerts Choose and Book Common P2P GP2GP Legitimate Relationships Personal Demographics Service Health and Clinical Management GP Summary Pathology Medication Management PSIS Query PSIS CDA Admissions Ambulance Messaging Diagnostic Image Reporting Discharge Emergency Department Health and Social Care Integration HealthSpace Mental Health NHS Direct Nullification Out Of Hours Outpatients Sealed Envelopes Generic CDA Documentation

Slide 12

What do each of the sections of the MIM look like? Refer to the Message Implementation Manual Walkthrough for Discharge.

Slide 13

Conclusions The MIM uses HL7 V3 to map out roles, trigger events, interactions, and other resources Several data types are supported within the MIM, and examples are given of each for you to reference The MIM covers four main domains: common; administrative; health and clinical management; and, PSIS CDA Several versions of the MIM exist, and software suppliers may be supporting any number of versions.

Slide 14

Further Resources Web Sites HL7 UK http://www.hl7.org.ukhttp://www.hl7.org.uk NHS Connecting for Health Data Services http://www.connectingforhealth.nhs.uk/systemsandservices/data http://www.connectingforhealth.nhs.uk/systemsandservices/data TRUD https://www.uktcregistration.nss.cfh.nhs.uk/trud/https://www.uktcregistration.nss.cfh.nhs.uk/trud/ Books Benson, T. (2009) Principles of Health Interoperability HL7 and SNOMED. Hinchley, A. (2007) Understanding HL7 - A Primer on the HL7 Version 3 Interoperability Standard.

Slide 15

Yorkshire Centre for Health Informatics Leeds Institute of Health Sciences Faculty of Medicine and Health Charles Thackrah Building 101 Clarendon Road Leeds, United Kingdom LS2 9LJ Tel. +44 (0) 113 343 4961 www.ychi.leeds.ac.uk