AU Patient Summary Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 0.1.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-ps/ and changes regularly. See the Directory of published versions

Relationship with other IGs

This guide is built on top of the FHIR standard and, where available, AU Base. It is compliant with the profile conformance requirements in AU Core and IPS.

The context of AU Patient Summary within the set of HL7 AU standards is shown in the figure below:

• the FHIR standard is the foundation, which creates a common platform or foundation on which a variety of different solutions are implemented.
• AU Base defines local concepts for use in an Australian context introducing relevant identifiers, terminology, extensions.
• AU Core defines a set of conformance requirements that enforce a set of ‘minimum requirements’ on the local concepts from AU Base, specifying the elements, extensions, vocabularies, and value sets that SHALL be present and how they SHALL be used, along with the RESTful API interactions.
• Use case IGs (AU eRequesting and AU Patient Summary) build on AU Core to address specific use cases, defining a set of conformance requirements on top of AU Core, using additional building blocks from AU Base as needed.

This layering of IGs balances relative adoption and implementation maturity of FHIR and requirements of the use cases involved.

Figure 2: Context of AU Patient Summary within the set of HL7 AU standards

Relationship to AUCDI and other IGs

The primary intent of the Australian Core Data for Interoperability (AUCDI) is to design and govern a collection of coherent, reusable building blocks known as ‘data groups’. These data groups specify “what” the clinical requirements of the clinical information that should be included for data entry, data use, and sharing of information supporting healthcare delivery. However, it does not specify “how” the data is exchanged; this is the role fulfilled by the FHIR standard. AUCDI is not required to be implemented as a whole single product. Parts can be implemented as required for specific use cases.

AUCDI is focused on an agreement of “the core of the core” common data elements; minimum data required to support standardised clinical information capture at the point of care as well as enable the safe and meaningful exchange of information to other care providers. AUCDI Release 2 (R2) will identify a set of core data groups and elements considered important for a minimal patient summary.

With AUCDI defining clinical data requirements, AU Core defining the minimum core digital health and administrative FHIR-based profiles, and AU Patient Summary providing detailed FHIR-based profiles for meeting patient summary requirements, an interpretation of AUCDI is necessary which is undertaken through the community.

Updates to AU Patient Summary depend upon community input and we encourage our audience to submit questions and feedback to AU Patient Summary specifications by clicking on the Propose a change link in the footer of every page. In addition, we encourage requesting any necessary clarifications to AUCDI through the AUCDI process that helps inform future updates to AU Patient Summary.

See AUCDI for the relationship between the AUCDI data groups, elements, AU Core profiles, and AU Patient Summary profiles.

The relationship of AU Patient Summary to AUCDI and other implementation guides is shown in the figure below.

Figure 3: Relationship to AUCDI and Other IGs