Wednesday, January 20, 2021

We Really Seem To Have Been At This For A Very Long Time!

This appeared in my inbox a few days ago!


Software Developer Community Announcement

Clinical Package Validator v3.2 - Released

The Australian Digital Health Agency has released version 3.2 of the Clinical Package Validator.

This version of the Validator introduces validation capabilities for Secure Message Delivery (SMD) messages and HL7 v2 messages:

Validation of HL7 v2 messages

  • Referral messages (REF_I12) 
  • Order messages (ORM_O01)
  • Observation result messages (ORU_R01)
  • MDM messages (MDM_T02)
  • Referral acknowledgement messages (ACK_I12)
  • Referral response messages (RRI_I12)
  • Order acknowledgement messages (ACK_O01)
  • Order response messages (ORR_O02)
  • Observation result acknowledgement messages (ACK_R01)
  • MDM acknowledgement messages (ACK_T02)
  • MDM messages (MDM_T02)

For a more detailed description of the changes, please refer to the Release Note.

Who does this affect?

  • Developers of systems sending or receiving SMD messages
  • Developers of systems generating or consuming HL7 v2 messages
  • System integrators

More Information

Clinical Package Validator v3.2 is available for download from:

Disclaimer

Before formally declaring conformity to the System Operator of the My Health Record system, developers need to perform additional tests to ensure full coverage of all requirements.

Please refer to the Product Data Sheet for more detailed information about the Validator’s coverage of requirements and conformance test cases.

Feedback and questions

We value your feedback and encourage questions, comments or suggestions about our products. Please email help@digitalhealth.gov.au or call 1300 901 001.

Thank you for your continued support.

Regards,
Australian Digital Health Agency


Additional resources

Other Agency products with related resources, FAQs, webinars, specifications, events and news are available from the Developer Centre.


You or your colleagues can join the Australian Digital Health Agency Software Development Community by registering on the Developer Centre Website.

This email is being sent to you as a member of the Australian Digital Health Agency Software Development Community. The email address davidgm@optusnet.com.au has been registered to receive updates or has been used to downloaded specifications from one of the Agency websites. Please click here to unsubscribe or to change your subscription preferences.

For more information on how the Agency handles your personal information, how you can access and seek correction of the information, how privacy complaints can be made and how the Agency deals with such complaints, please see the Privacy Policy.

Here is the link:

https://developer.digitalhealth.gov.au/specifications/ehealth-reference-platform/ep-3408-2020/dh-3352-2020

I read this and thought to myself just how long can all this go on and not be either stably fixed or superseded.

This product – according to the release note – has been under development and improvement since May 2012 – first supporting the PCEHR and then the myHealthRecord messages which were sent/received via HL7 V2.

Reading through the release note one really gets the feeling that there may be simpler and more modern ways of accessing and recording data in the myHealthRecord (and other applications) and that message validation was something that should have been well and truly sorted by now! Maintenance of tools like this is hardly cost free!

Of course going further back efforts in improving clinical messages have a history going back at least as far as 2008 with the Australian Health Messaging Lab (AHML) which I believe is long since defunct.

One really wonders just how long it will be before secure clinical messaging has become a totally standardised non-problem that is just used – a medical equivalent of WhatsApp, Telegram or Signal anyone? Or am I just to naive?

David.

 

No comments:

Post a Comment