AU Patient Summary Implementation Guide
0.5.0-cibuild - CI Build Australia flag

AU Patient Summary Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 0.5.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

Comparison With Other National and International IGs

Page standards status: Informative

AU Patient Summary (AU PS) complies with, and/or leverages, national and international standards, in particular:

Relationships between AU PS, AUCDI, and the above key implementation guides are described in Relationship with other IGs.

Profile Comparison

As part of profile comparison, the requirements, constraints, and standards specified in a particular FHIR profile are evaluated. These requirements can include mandatory elements, Must Support elements, cardinality constraints, data types, terminology bindings, usage rules, extensions, rules on missing or suppressed data.

The table below provides a profile only comparison from AU PS to profiles in key implementation guides. Compliance in the reverse direction is not guaranteed, i.e. a resource that is compliant with an International Patient Summary profile MAY NOT be compliant with AU PS.

Legend:

Compliant: An AU PS compliant resource meets all requirements of the compared profile.

Additional requirements: An AU PS compliant resource is compatible, but additional changes may be needed to meet all requirements of the compared profile. Where additional requirements are identified, more information is provided in the sections below.

Incompatible: An AU PS compliant resource is incompatible with the compared profile. A resource cannot be compliant to both. Where incompatible requirements are identified, more information is provided in the sections below.

No equivalent profile: No equivalent profile for comparison.

AU PS IPA 1.1.0 IPS 2.0.0 AU Core 2.0.0
AU PS AllergyIntolerance
AU PS Bundle
AU PS Composition
AU PS Condition
IPA-problem-list-item
AU PS Encounter
AU PS Immunization
AU PS Medication
AU PS MedicationRequest
AU PS MedicationStatement
AU PS Organization
AU PS Pathology Result Observation
AU PS Patient
AU PS Practitioner
AU PS PractitionerRole
AU PS Procedure
AU PS RelatedPerson
AU PS Smoking Status

IPA Profile Additional Requirements

IPA 1.1.0 describes how an application acting on behalf of a patient can access patient information from a clinical records system using a FHIR-based API.

Additional Requirements

The following IPA profile(s) contain additional requirements. Implementers are advised to note that some code changes may be required to support these profiles.

AU PS Profile IPA 1.1.0 Profile Element IPA Profile Additional requirements
AU PS Condition IPA-problem-list-item Condition.category Requires category of 'problem-list-item'.
AU PS MedicationRequest IPA-MedicationRequest MedicationRequest.reported[x] Must Support element in IPA.
MedicationRequest.doNotPerfom Must Support element in IPA.
AU PS MedicationStatement IPA-MedicationStatement MedicationStatement.statusReason Must Support element in IPA.
MedicationStatement.context Must Support element in IPA.
MedicationStatement.informationSource Must Support element in IPA.
AU PS Patient IPA-Patient Patient.identifier IPA requires all identifiers to have value (1..1), and at least one of system, type or assigner (ipa-pat-1).
Patient.identifier.value Must Support element in IPA.
Patient.active Element SHOULD be present if Patient.link is present (ipa-pat-4). Must Support element in IPA.
Patient.name.text Sub-element SHOULD be present (ipa-pat-3).
Patient.link Must Support element in IPA.
AU PS Practitioner IPA-Practitioner Practitioner.name.text Sub-element SHOULD be present (ipa-pract-1).
Missing and Suppressed Data

AU PS compliant resources are compliant with IPA requirements for Missing Data. IPA does not include requirements for Suppressed Data.

Capability Statement Comparison

No comparison is undertaken. AU PS does not define any FHIR specific interactions - no CapabilityStatement is defined.

Systems implementing AU Patient Summary MAY implement interactions defined in other CapabilityStatements, for example: