- Get Started with Digital Health
- Using the My Health Record system
- For Implementers
- News and Events
About the Agency
- Tenders and Offers
- Digital Health Space Blogs
- Australian Digital Health Agency Board
- Australian Digital Health Agency Executive Team
- Freedom of Information (FOI)
- Board Advisory Committees
- Photo Gallery
- Contact Us
- Help Centre
- Useful Links
- Website Accessibility
- Senate Order Reporting
- Corporate Plan
- Digital Health Cyber Security Centre
- Reporting fraud
- Public Interest Disclosure
- Agency Clinical Reference Leads
News and Events
- Events Calendar
- #Share: Issue 1, April 2019
- #Share: December 2018
- #Share: October/November 2018
- #Share: September 2018
- #Share: August 2018
- #Share: July 2018
- #Share: June 2018
- #Share: May 2018
- #Share: April 2018
- #Share: March 2018
- #Share: February 2018
- #Share: January 2018
- #Share: December 2017
- 2020 vision of the future – the National Health Genomics Policy Framework
- Engaging with Primary Health Networks (PHNs) to support My Health Record Expansion
- Dispense records go live in NSW
- Health Care Homes must be registered for My Health Record
- Improved HPV test will save lives and reduce GP visits
- Live tests of electronic discharge summaries are underway
- Solving healthcare challenges through interoperability and artificial intelligence
- My Health Record – coming to a Men’s Shed near you
- Making new connections at the 2017 Connectathons
- #Share: November 2017
Making new connections at the 2017 Connectathons
If you’re a seasoned digital health developer, you probably know what a “connectathon” is, and might even have been involved in one already. For the rest of our readers, a connectathon is an opportunity for developers to check that their implementations connect to other systems as intended. An additional benefit of connectathons is that they help to confirm that the specifications governing the connections are complete.
The Australian Digital Health Agency hosted simultaneous connectathons for secure messaging and clinical terminologies this year, the latter in collaboration with the CSIRO. At the secure messaging event, software vendors validated their HL7 profiles and checked that the FHIR® Provider Directory API is ready for adoption in their solutions. The first implementations will be through the two secure messaging proof of concept projects that will deliver discharge summaries and referrals.
The 2017 Connectathon in progress in Melbourne, Victoria.
The HL7 FHIR® standard also played a prominent role in the National Clinical Terminology Service (NCTS) event, where developers explored the NCTS’s FHIR STU3 upgrade, advanced medication use cases, and use of NCTS services in general. Another stream provided education for both technical and non-technical users.
Great progress was made in both connectathons, with participants commenting on the value of collaborating in the room, with different vendors participating and validating the end-to-end process of sending messages real time, including utilising different vendors’ implementations of the new FHIR Provider Directory API.
“The value of these type of connectathon sessions is being able to work side by side with other vendors, testing the products in real time against the actual software used by our customers.”
-- Brian, Telstra Health.
These events are free and open to all registered developers, but they are proving to be increasingly popular, so we encourage anyone with an interest to register via the above links. This can be your chance to make some great connections!