1                                Introduction

MIM 4.2.00

1.1                         Known Issues with MIM 4.2.00

No known issues.

1.2                         Overview

This manual provides information to implementers regarding the use of HL7 v3 messages within the National Programme for Information Technology (NPfIT).

Messages and Data Types are based on the HL7 v3 RIM. Realm specific constraints are applied where appropriate and are identified within the documentation.

Readers are advised to read this guide in conjunction with appropriate elements from the HL7 v3 Standard (Ballot pack 6.November 03) which is the underlying HL7 v3 standard on which these messages have been based. In order to make these messages meet the NPfIT requirements, certain elements of later ballot packs have been pre-adopted. Where there is a discrepancy between the NPfIT messages and the HL7 standard, the NPfIT definitions take precedence  This guide does not reproduce the foundation components of the HL7 v3 Standard.

1.1.1                     Error/Exception Handling

This Message Implementation Manual defines Error/Exception Handling measures for those potential errors that have been identified through the business analysis process. Additional guidance has been included in the Infrastructure domain, section 4.1,  to support the handling of these errors in HL7 messages. 

Where exceptions or errors have not been foreseen and are not supported by the measures defined in this MIM, such errors should be written to the suppliers Dead Letter queue.

The Dead Letter queue will be regularly inspected by the Supplier operations team and prompt action will be taken to identify and resolve the problem, inline with agreed procedures (including where the problem analysis or resolution involves another supplier).

Recurring problems will be reviewed with the Authority on a regular basis; this may result in additional error handling support being introduced to future versions of the MIM.

1.1.2                     Default Values in HL7 Message Payload Instances

All Default Values shall be populated by the sender in all message instances. This includes HL7 structural attributes (e.g. classCode and moodCode) as well as those mandatory and required attributes where a default is specified in the Tabular View.

Not all schemas currently enforce this and some of the examples do not contain these defaults. This will be revised as these artefacts are updated.

1.1.3                     SDS OIDs

Following discussion regarding the identification of SDS Identifiers, it has been agreed that the most sensible and useful approach is to identify each of the SDS code types with a different OID. This will enable the type of the code to be identified without having to reference SDS.

This document is best viewed at a resolution of 1024 x 768 using IE v6.n

Icon Meaning

                 R-MIM

                 Tabular View

             Schema

                 Example Message

            Interaction Schema

             Interaction

             MIF

.