- The majority of the changes to the models were made with Visio 2002 in combination RMIM Designer 4.5.11
- In order to overcome a known issue with the above-mentioned applications, Visio 2007 and RMIM Designer 4.7.8 was used for certain model changes.
This delta release defines the functionality around the major use cases for Revise Prescription. Revise Prescription is defined as the act of changing a prescription order without replacing it on the DIS. The major use cases defined for Revise Prescription are:
- Error Correction - This is the act of revising a prescription order in order to mitigate a clerical error or errors made by the user on a given prescription order.
- Clinical Modification - The is the act of revising a prescription order based on a clinical decision and/or an interaction with a patient by the original author of the prescription.
This work was requested by Alberta as they have plans to implement the Clinical Modification use case. Quebec supported development of the work as they have already implemented the error correction use case using the MR 2009 message set. Other interested parties include Pharmacy software vendors and the Canadian Association of Chain Drug Stores (CACDS) who requested that Revise Prescription functionality be developed as part of their presentation to jurisdictional CIOs in February of 2013.
Alberta has received these artifacts as a pre-release to meet their development time lines and now this delta release has been officially published.
Standards
Delta release
HL7 Explorer 1.0: Browse Pan-Canadian Standards Online
The HL7 Explorer view provides an easy to navigate web based rendering of the pan-Canadian standards. The HL7 Explorer is now considered stable for release and will continue to evolve over time based on stakeholder feedback.
Downloadable Artifacts
| Name | Artifact |
Release Notes, Change Log, Storyboards and Diagrams document, and Business Rules and Informational Requirements document | |
This is a zip of the entire CeRx 4.4.1 Release | |
General guidance and specifications on data type usage. | |
MTW is an artifact that specifies the pan-Canadian terminologies developed to support the electronic communication in pan-Canadian standards. | |
| Vocabulary Model Interchange Format Files (MIFs) CeRx4.4.1 - 20141020 | Vocabulary MIFs represent the MTW in a computable format which allows computer systems to consume the content. |
This file provides information on linkage from concept domains and value sets contained in the Master Terminology Worksheet to where they are referenced in the model attributes within the pan-Canadian static models included in this release. A XML editor/viewing is strongly recommended to be used when viewing this information. | |
This spreadsheet is a pivotal document in that it ties together the scope of the pan-Canadian HL7 v3 Specifications from a transaction perspective, through to interactions and finally to messages. | |
This file contains message models in MIF(Model Interchange Format) version 1 format generated from the V3 generator legacy tools. | |
This file contains message models in MIF(Model Interchange Format) version 2 format generated from the V3 legacy tools. | |
This file contains all XML schemas for message types and interactions as well as the core schema files (narrative block, infrastructure root, vocab schema and datatype schema) | |
This file contains all message models in Excel (XLS) format | |
This file contains all message models in Table View format. | |
This file contains all message models in Visio format | |
This file contains a business rendering of the message models in Word format |