Go to top of page

High Level Scope

The software will enable the upload of pathology or diagnostic imaging reports to the My Health Record system, and the viewing of the My Health Record system by authorised representatives of the diagnostic services organisations. This means that the software should:

  • Integrate to the HI Service for the purpose of sourcing and validating healthcare identifiers;
  • Support the use of NASH digital credentials for the purpose of authentication to the My Health Record system;
  • Generate eHealth Pathology or Diagnostic Imaging Reports in the Clinical Document Architecture (CDA) format with PDF attachment;
  • Upload these reports to the My Health Record system;
  • Enable the viewing of clinical documents in a patients' My Health Record.

Detailed Functionality

To enable the uploading of clinical documents and the viewing of a patient's My Health Record, the following functionality is recommended.

Functionality
Supporting material for development and testing

Integrate to the My Health Record system via the PCEHR B2B Gateway to check whether the patient has a My Health Record and load a clinical document.

Implement the following web services:

  • doesPCEHRExist (Record Access Service)
  • gainPCEHRAccess (Record Access Service)
  • getView (View Service)
  • ITI – 43 retrieveDocumentSet (Document Exchange Service)
  • ITI - 18  registryStoredQuery (Document Exchange Service)
  • ITI – 41 provideAndRegisterDocumentSet-b (Document Exchange Service)
  • removeDocument (Document Exchange Service)

Implement the following use cases:

  • UC.CIS.001 – Check if an advertised PCEHR exists
  • UC.CIS.002 – Gain access to PCEHR
  • UC.CIS.201 – Upload a clinical document
  • UC.CIS.202 – Supersede a clinical document
  • UC.CIS.203 – Remove a clinical document
  • UC.CIS.204 – Download a clinical document
  • UC.CIS.301 – Access a view service

Download and view My Health Record information via:

  • a document list
  • the Diagnostic Imaging Report View or Pathology Report View (as appropriate)
  • and using prominently displayed user interface elements that allow the user to navigate to the patient's latest Shared Health Summary and Discharge Summary

Unpack and render a CDA document

  • The rendering system should be capable of rendering any Level 1a to 3b CDA document, including packaged attachments
  • CDA documents can be rendered in systems that apply an XSL transform (style-sheet) over the root CDA document contained in the document package
  • Where the root CDA document references packaged attachments, it may be necessary to integrate additional software and/or application logic in order to view these attachments
  • The rendering system should also provide the facility for users to view Level 1a CDA documents, where the document body is contained within a packaged attachment, referenced from the root CDA document
  • The list of supported formats are contained in the Common Conformance Profile for Clinical Documents

Generate eHealth Diagnostic Imaging Reports or eHealth Pathology Reports as appropriate in CDA format, package them, and upload them directly to the My Health Record system.

PCEHR B2B Gateway Services v1.7 available at 
https://developer.digitalhealth.gov.au/specifications/national-infrastructure/ep-2933-2019

  • Record Access Service – Logical Service Specification
  • Record Access Service – Technical Service Specification
  • Document Exchange Service – Logical Service Specification
  • Document Exchange Service – Technical Service Specification
  • View Service – Technical Service Specification
  • View Service – Logical Service Specification

PCEHR Connecting Systems - Conformance Requirements v1.4 available at 
https://developer.digitalhealth.gov.au/specifications/national-infrastructure/EP-2156-2015

My Health Record Integration Toolkit v1.2.21 available at 
https://developer.digitalhealth.gov.au/specifications/ehealth-reference-platform/ep-2603-2018

  • My Health Record B2B Client Library - .NET Sample Code
  • PCEHR B2B Client Library - Java Sample Code
  • My Health Record B2B Client Library - Schema WSDL

Clinical Documents Integration Toolkit v1.7 available at 
https://developer.digitalhealth.gov.au/specifications/ehealth-reference-platform/ep-2588-2018

  • Clinical Document Library - .NET Sample Code
  • Clinical Document Packaging Library - .NET Sample Code
  • Clinical Document Packaging Library - Java Sample Code
  • Generic Clinical Document Style Sheet - Style Sheet No CSS
  • Generic Clinical Document Style Sheet - Style Sheet With CSS
  • Prescription and Dispense View Stylesheet – Stylesheet No CSS
  • Prescription and Dispense View Stylesheet – Stylesheet With CSS