AU Patient Summary Implementation Guide
0.1.0-cibuild - CI Build
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
Page standards status: Informative |
AU Patient Summary complies with, and leverages, national and international standards, in particular:
Relationships between AU Patient Summary, AU Core, AUCDI, and the above key implementation guides is described in Relationship with other IGs.
Corresponding profiles, conformance requirements, and capability statements included in the key FHIR implementation guides were reviewed and considered during AU Core’s development to ensure alignment, and to facilitate adoption of, this standard.
The below comparison evaluates AU Patient Summary conformance requirements with the key implementation guides identifying where compliance with AU Patient Summary satisfies the expectations established by the referenced implementation guide.
At this time only TBD is available.
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 Patient Summary 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 Patient Summary.
Legend:
Compliant: An AU Core compliant resource meets all requirements of the compared profile.
Additional requirements: An AU Core 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 Core 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.
TBD