You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

During a review of documentation, it has been determined that a couple points of clarification need to be made with regards to the tools used during the development of this release. These are:
  • 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. 
For any questions, please email the Infodesk or call 416-595-3417/1-877-595-3417 (toll-free).

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:

  1. 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.
  2. 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

Please Note: This is a delta release only containing artifacts that were changed as part of the scope of CeRx 4.4.1.
For all other artifacts, please refer to the CeRx 4.4 release under Previous Releases. For details on the scope of the CeRx 4.4.1 delta release, please refer to the Release Notes.

  • No labels