MIM & Compatibility Guidance

Transcription

1 Programme NPFIT Document Record ID Key Sub-Prog / Project ETP NPFIT-ETP-EDB Prog. Director Tim Donohoe Status Approved Owner Ian Lowry Version 2.0 Author Rob Gooch Version Date 31 July 2007 Crown Copyright 2012

2 Amendment History: Version Date Amendment History /10/2005 Initial draft for comment /10/2005 Incorporating comments from Ian Lowry /12/2005 Incorporating Comments from Tim Donohoe /12/2005 Approved final version /07/2007 Updated to reference MIM /07/2007 Reviewed by IL, awaiting TD approval /07/2007 Marked as approved Forecast Changes: Anticipated Change When Reviewers: This document must be reviewed by the following: Name Signature Title / Responsibility Date Version Rob Gooch ETP Technical Architect 05/07/ Ian Lowry ETP Programme Manager 06/07/ Approvals: This document must be approved by the following: Name Signature Title / Responsibility Date Version Tim Donohoe ETP Programme Director 12/12/ Tim Donohoe ETP Programme Director 31/07/ Distribution: For issue to LSP and existing system suppliers engaged with the CFH programme Document Status: This is a controlled document. Whilst this document may be printed, the electronic version maintained in FileCM is the controlled copy. Any printed copies of the document are not controlled. Crown Copyright 2012 Page 2 of 11

3 Related Documents: These documents will provide additional information. Ref no Doc Reference Number Title Version 1 NPFIT-SHR-QMS-PRP-0015 Glossary of Terms Consolidated.doc 2 NPFIT-NDA-COM-TZ-0160 MIM N/A 3 NPFIT-FNT-TO-DPM-0602 MIM N/A Glossary of Terms: List any new terms created in this document. Mail the NPO Quality Manager to have these included in the master glossary above [1]. Term Acronym Definition Crown Copyright 2012 Page 3 of 11

4 Contents 1 About this Document Purpose Audience Content Background Forwards Compatibility Backwards Compatibility Prescription Identifiers across MIM Versions Prescribing Interactions Parent Prescription Cancel Request/Response Prescriber Withdraw Dispensing Interactions Patient Prescription Release Request / Response Nominated Prescription Release Request / Response Dispense Proposal Return Dispense Notification Dispense Notification with Claim Information / Dispense Claim Information / Reimbursement Claim Resubmit Dispenser Withdraw Rebuild Dispense History Prescription Pricing Division (PPD) Interactions Dispense Reimbursement Claim / Dispense No Claim Notification Forward Withdraw Notification Dispense Reimbursement Claim Reject 11 Crown Copyright 2012 Page 4 of 11

5 1 About this Document 1.1 Purpose This document provides Message Implementation Manual (MIM) compatibility guidance to suppliers who are providing EPS prescribing, dispensing and reimbursement systems for the introduction of the second functional release of EPS, known as EPS Release Audience This document has been written for system suppliers. 1.3 Content This document comprises of the following sections Section 1 About this document Section 2 Background Section 3 Forwards compatibility Section 4 Backwards compatibility Crown Copyright 2012 Page 5 of 11

6 2 Background Functional aspects of the Electronic Prescription Service (EPS) being delivered by the Electronic Transmission of Prescriptions (ETP) programme are being implemented over two releases. EPS Release 1 became operational during February 2005 and system-to-system messaging interactions are developed using Message Implementation Manual (MIM) This document refers to this version as v1. EPS Release 2 will be developed using MIM This document refers to this version as v2. To enable the transition from v1 to v2, some messaging interactions between these MIM versions are compatible. Other interactions, where no business requirement exists, are not compatible. Note. The guidance document only considers the Medication Management domain within the MIM. Crown Copyright 2012 Page 6 of 11

7 3 Forwards Compatibility The MIM (v1) is not forwards compatible with MIM (v2) therefore the following messaging scenarios are not possible. Prescribing Dispensing Submit a v2 prescription using a v1 Parent Prescription message Cancel a prescription using a v1 prescribing system Request a v2 prescription using a v1 Prescription Release Request message Dispense a v2 prescription using a v1 Dispense Notification message Submit an electronic reimbursement claim using a v1 dispensing system Request nominated prescriptions using a v1 dispensing system Crown Copyright 2012 Page 7 of 11

8 4 Backwards Compatibility For specific message interactions, the MIM (v2) is backwards compatible with MIM (v1). This section details these interactions and provides guidance for the implementation of the Medication Management domain within MIM The primary constraint regarding backwards compatibility is that a v1 dispenser cannot receive and interpret a v2 prescription, thus dispensers must be enabled with v2 functionality before prescribers begin to issue v2 prescriptions (see Figure 1). Figure 1 Prescription Compatibility Overview 4.1 Prescription Identifiers across MIM Versions A key attribute of many EPS messages is the Prescription ID. For MIM (v1) messages the Prescription ID is a 32-character UUID. For MIM (v2) messages the Prescription ID is an 18-character Short Form ID. Where a MIM message only supports v2 Prescription IDs, the tabular view within the MIM will be documented as follow. The 36 character clinical statement DCE UUID of the prescription shall only be used where the Short Form Prescription Identifier does not exist. The Identifier Global datatype flavour is used to carry this information as follows: the root attribute shall contain the value of the DCE UUID Where a MIM message supports both v1 and v2 Prescription IDs, the tabular view within the MIM will be documented as follows. Prescription identifier that is universally unique across all records. This shall be the 18 character Short Form Prescription Identifier where it exists. Crown Copyright 2012 Page 8 of 11

9 The Identifier External datatype flavour is used to carry this information as follows: the root attribute shall contain the value of the Short Form Prescription Identifier OID = the extension attribute shall contain the 18 character Short Form Prescription Identifier The 36 character clinical statement DCE UUID of the prescription shall only be used where the Short Form Prescription Identifier does not exist. The Identifier Global datatype flavour is used to carry this information as follows: the root attribute shall contain the value of the DCE UUID 4.2 Prescribing Interactions Parent Prescription Those running MIM (v1) systems will continue to prescribe using v1 messages. Those running MIM (v2) systems will prescribe using v2 messages. Internally within the PMR, the prescribing system will be required to handle both v1 and v2 data structures as prescriptions will have been created at different times, when different versions of the EPS were in operation. If a v1 prescription is rejected, the rejection message will be a v1 message. If a v2 prescription is rejected, the rejection message will be a v2 message Cancel Request/Response These interactions were not included within EPS v1. A prescribing system cannot cancel a v1 prescription using the v2 Cancel Request message. If this is attempted, the NCRS Spine will respond with the error message Prescription not found Prescriber Withdraw This interaction was not included within EPS v1 and applies only to personal administration messages that are out of scope for EPS v Dispensing Interactions Patient Prescription Release Request / Response The dispensing system can request either a v1 or v2 prescription using the v2 Patient Prescription Release Request message. A successful response will be the v2 Patient Prescription Release Response message. An unsuccessful response will be the v2 Prescription Release Rejection message. Crown Copyright 2012 Page 9 of 11

10 The v2 Patient Prescription Release Response message uses a technique to support the batching of messages of different versions. Refer to documentation contained within the MIM for how this message is implemented. Hence the dispensing system will be required to support both the v1 and v2 Prescription Response messages, as defined within MIM Note. If the NCRS Spine receives a v1 Patient Prescription Release Request it will respond with a v1 Patient Prescription Release Response or the v1 rejection message Nominated Prescription Release Request / Response These interactions were not included within EPS v1. The response interaction uses the same message as the non-nominated interaction, see above Dispense Proposal Return The dispensing system can return either a v1 or v2 prescription using the v2 Dispense Proposal Return message Dispense Notification The dispensing system can record a dispensing event for either a v1 or v2 prescription using the v2 Dispense Notification message Dispense Notification with Claim Information / Dispense Claim Information / Reimbursement Claim Resubmit These interactions were not included within EPS v1. Electronic claims can only be submitted for digitally signed prescriptions, functionality not available in EPS v1. Therefore there are no compatibility issues to consider Dispenser Withdraw This interaction was not included within EPS v1. The dispensing system can withdraw either a v1 or v2 dispensing event using this interaction Rebuild Dispense History This interaction was not included within EPS v1. The dispensing system can rebuild a dispensing history against either a v1 or v2 prescription using this interaction. 4.4 Prescription Pricing Division (PPD) Interactions Dispense Reimbursement Claim / Dispense No Claim Notification The Dispense Reimbursement Claim interaction was not included within EPS v1, while the Dispense No Claim Notification interaction was included within EPS v1. Both these interactions use the v2 Dispense Reimbursement Claim message which uses a technique to support the batching of messages of different versions. Refer to documentation contained within the MIM for how this message is implemented. Crown Copyright 2012 Page 10 of 11

11 Electronic claims can only be submitted for digitally signed prescriptions, functionality not available in EPS v1. Therefore there are no compatibility issues to consider Forward Withdraw Notification This interaction was not included within EPS v Dispense Reimbursement Claim Reject This interaction was not included within EPS v1. Electronic claims can only be submitted for digitally signed prescriptions, functionality not available in EPS v1. Therefore there are no compatibility issues to consider. Crown Copyright 2012 Page 11 of 11