Electronic Transfer of Prescription 1.1
- These specifications will be updated based on feedback through Standards Australia and are considered “for information only”. A future release expected in Mid 2012 will incorporate the this feedback.
- The documents numbered 10 to 13 in the above list are platform-specific technical documents and have not yet been validated through live implementations in commercial clinical systems. For this reason the documents are identified as “Draft for trial implementation”. NEHTA will work with early implementers to offer support and contribute to validation of these technical documents.
- The release specifies the National Authentication System for Health (NASH) as the mechanism for the provision and management of Public Key Infrastructure (PKI) certificates for mutual authentication and also message encryption and signing. At the time of the release, NASH is still in development, but is scheduled to be available to early implementers.
- The release does not specify the technical mechanisms for document authors to digitally sign Clinical Document Architecture (CDA) documents. NEHTA is closely monitoring current national and international standards efforts to reach consensus on a CDA signing approach. NEHTA will work with Standards Australia and early implementers to finalise this mechanism.
- The release does not specify the credentials used by document authors to digitally sign ETP documents. NEHTA continues to work with clinical stakeholders to reach agreement on and obtain Commonwealth, state and territory approvals of the credentials required for the digital signing of ETP documents. It is expected that the approved credentials will be based upon individual Public Key Infrastructure (PKI) certificates managed by the NASH.
- The release does not specify the technical mechanisms for the submission of electronic prescriptions to Medicare Australia for PBS claim verification and audit, nor the technical mechanism for healthcare recipients to digitally sign for the receipt of PBS medications. NEHTA continues to work with Medicare Australia to specify these mechanisms.
Specification Development and Implementation
Of course we also do have a HL7 V2 spec which is pretty widely used and which is probably also being updated. It is simpler and probably much more useable.
The MSIA have also known for a while the new NEHTA specs were not fit for use and mentioned that in one of their submissions.
I just hope no one has spent any money trying to implement the new one. Clearly NEHTA needs to utterly revamp the way it goes about the delivery of specifications such as this to ensure this sort of nonsense is not repeated. Essentially this is another 14 months wasted in a major and important application area.