As mentioned a day or so ago, NEHTA have just released their first attempt at ETP (Electronic Transfer of Prescriptions) documentation.
These can be found here:
http://www.nehta.gov.au/e-communications-in-practice/emedication-management
The summary release document has the file name:
NEHTA_0544_2009 Electronic Transfer of Prescription Draft Release 1 0 - Release Notification v0 6
And the most interesting document I find is the one named:
ETP Concept of Operations_Release_1_v1 Draft
Some of the more interesting things found in this document are the following:
“NEHTA’s e-Medication Management program has been tasked to develop key specifications required for software vendors, GPs and Pharmacists to establish a national environment for standardised electronic prescription exchange, one where prescriptions can be sent securely and reliably to community pharmacists, while maintaining the consumer's right to their own choice of pharmacy.”
Release Notification Page 1.
What this actually says is that we are working on a system that won’t allow the patient to direct the prescription to where they want (as is done elsewhere). We want to create a central infrastructure where all prescription data will flow through. Of course this will also be where we (the Pharmacy Guild) can collect a fee for each prescription that flows through.
The proposed design also responds to the paranoia held by community pharmacy regarding doctors being able to suggest one pharmacist in preference to another – something pharmacists have always been able to do regarding doctors.
At present is fails also to note how consumers would also like to be able to arrange delivery of their medicine from their doctors surgery and other even more consumer friendly ideas (Thanks Heather Grain for pointing this out)
Of course point to point transmission can be made simpler and more secure but we won’t do that – we are going for a complex SOA based store and forward approach.
Next we have:
“The following will be released shortly:
• e-Prescribing Structured Document Template
• Dispensing Record Structured Document Template
• Secure Messaging End Point Specification “
Release Notification Page 2.
Opps! We have not quite worked out the structure of the prescriptions we plan to send or their content!. One would think that was pretty basic!
Actually it seems to be worse than even that.
Page 19 of the Concept of Operations Document we find.
“The components of the goal-state architecture are:
• Prescription Exchange Service (PES): The PES may require additional interfaces, beyond those specified in ETP Release 1, in order to support integration with potential national IEHR repositories, research repositories and (possibly) Medicare Australia systems. The interfaces used by an Electronic Prescribing System or an Electronic Dispensing System to manage the prescribing-dispensing processes, however, will not require any changes.
• Electronic Prescribing Systems (EPS): ETP Release 1 supports the optional use of national standard clinical terminologies including SNOMED-CT and the Australian Medications Terminology (AMT) in e- Prescriptions. The goal-state is, however, to make the use of standard clinical terminologies mandatory.
• Electronic Dispensing Systems (EDS): ETP Release 1 supports the optional use of national standard clinical terminologies including SNOMED-CT and the Australian Medications Terminology (AMT) in Dispense Records. The goal-state is, however, to make the use of standard clinical terminologies mandatory.”
Translated the Australian Medicines Terminology and SNOMED are, and will be for a while, optional. Just how long have we been waiting – only to be now told:
Page 18 of Information Model
ePrescriptionItem.MedicationItem
- MedicationItem
This class is the entry point that contains a detailed description of a single, unique good that is listed as an item within an ePrescription.
MedicationItem.Description
The description of the prescribed item as defined by the prescriber. This text representation encapsulates all relevant concepts associated with describing an item, i.e. brand/trade or generic name, strength, form, etc.
When prescribers are describing a medication, they may do so at differing levels of specificity, depending upon the clinical context, the healthcare setting, the type of medication being prescribed, their knowledge of specific drugs, the functionality of their prescribing system and other factors.”
So the guts of NEHTA’s ETP system is the sharing of free text. Just amazing and symptomatic of the leadership we are getting from NEHTA.
More interesting is the scope of what these 5 documents are about (Page 9 of Concept document):
“NEHTA has identified five distinct capabilities for comprehensive eMM:
1. Exchange of electronic prescribing and dispensing messages:
this capability is concerned with the generation and exchange of electronic records that represent prescriptions and their associated dispensing records.
2. Adherence monitoring: this capability supports the ability to inform authorised healthcare providers and individuals when deviations from the expected sequence of dispensing events are detected. Adherence monitoring requires records of an individual’s prescribed and dispensed medications – it will make use of the electronic prescribing and dispensing records described in the previous paragraph.
3. Current Medication Lists: this capability supports the storage of medication reviews that are performed by healthcare providers. The documents produced by these medications reviews are referred to as “current medication lists” (CMLs). CMLs are either stored in dedicated CML repositories or are stored, along with other types of individual electronic healthcare records, in general purpose IEHR repositories. In either case the repositories make CMLs available to the individual, their authorised representatives and to authorised healthcare providers.
4. Medication History Lists: this capability supports the storage of a chronological record of an individual’s prescribed and dispensed medications. These records comprise a Medication History List (MHL) for each individual. MHLs are either stored in dedicated MHL repositories or are stored, along with other types of individual electronic healthcare records, in general purpose IEHR repositories. In either case the repositories make MHLs available to the individual and their authorised representatives and to the healthcare providers who require this information to service the individual and are authorised to do so by the individual.
5. Medication Decision Support and Secondary Uses: It is intended that medications management processes are supported by prescribing and dispensing decision support tools (integrated into prescribing dispensing and administration applications) that implement best practices based on evidence. This capability therefore includes the collection, storage and analysis of more complete and more detailed consumer medications data than is currently possible and the use of this data to derive appropriate rules for decision support tools.
The above five capabilities reflect various stages in the evolution of eMM and are not to be taken directly as a roadmap for national implementation across all the various different healthcare communities. Different communities will evolve to support these capabilities at different rates depending on the rate at which they can implement changes to existing policies and practices and on the rate at which the necessary underpinning e-health foundation services become available to them.”
NEHTA then goes on to say it is only point 1 they are addressing for now, the rest needs a whole heap of other things to happen and they haven’t yet.
Equally amazing is that if you look at ETP Context Diagram you find Decision Support is the last thing to be concerned with, where this is what a lot of the E-Prescribing Business Case is built on.
Second last I note this (Page 13)
“NEHTA has focused to date on specifying an ETP service that is targeted at adoption in the primary care community, and, with the expectations of this community in mind, Release 1 of the ETP service will continue to support the existing paper based processes. The goal-state of the ETP service is, however, for paperless processes to be widely available nationally.”
The detail is that what this is actually all about is basically adding a barcode to printed prescriptions to that the prescription text can be pulled down from some third party ‘cloud’ to a dispensing computer. This is just as is being already being done by eRX.
Last we have this (Page 16):
3.1 Governance and Privacy
A Governance and Privacy Management Framework will underpin the operations of the eMM services (including ETP) within the Australian healthcare sector.
This framework will be supported by legislation, participation agreements, security controls, audit and secondary uses. There are three levels of governance required:
• Strategic governance is required to provide oversight of the operation of the future directions of the eMM services (e.g. Ministerial council)
• Program management is required to provide oversight of the day to day activities of the eMM services (until an operational e-health entity is more formally established, NEHTA will provide overall program management with program management for specific implementation projects being the responsibility of the project principal).
• Regulatory oversight is required to provide legal authority, ensure privacy compliance and regulate operations in terms of complaints handling, dispute resolution and enforcement functions (e.g. Privacy Commissioner/s and jurisdictional health regulators).
ETP Release 1 has been restricted in scope in order for it to comply with the governance and privacy management framework that is already in place for community prescribing and dispensing. Similarly it is expected that implementations of the Current Medications List service within specific communities (e.g. Aged Care) can also be constrained to comply with existing governance and privacy management frameworks.
It is expected that Commonwealth Department of Health and Ageing will determine the preferred governance and privacy model for subsequent implementation initiatives. Interim arrangements for pilot projects will likely be required – these will be tailored to address specific local constraints.”
It is important to pay attention here as what we are told that we need governance we don’t have and an operational e-Health entity Minister Roxon (and Ms Halton) is not planning to pay for.
Talk about pie in the sky!
David.
