Health Connect Australia Provider Directory FHIR Implementation Guide, published by Australian Digital Health Agency. This guide is not an authorized publication; it is the continuous build for version 0.1.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/AuDigitalHealth/HealthConnect/ and changes regularly. See the Directory of published versions
| Official URL: http://ns.electronichealth.net.au/hc/ValueSet/hc-endpoint-payload-type-vs | Version: 0.1.0-preview | |||
| Standards status: Draft | Computable Name: AustralianEndpointPayloadTypesValueSet | |||
Usage:Jurisdiction: Australia |
||||
Copyright/Legal: Copyright © 2025 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ |
||||
The Australian Endpoint Payload Types value set enumerates well known endpoint payload types.
References
Profile: Shareable ValueSet
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs version 📦0.1.0-preview
Expansion performed internally based on codesystem HC Australian Endpoint Payload Types v0.1.0-preview (CodeSystem)
This value set contains 13 concepts
| System | Code | Display (en) | JSON | XML |
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706 | HL7 V2.4 REF message (Level 2) | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706-L1 | HL7 V2.4 REF message (Level 1) | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706/RRI | HL7 V2.4 RRI message | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORU-201701 | HL7 V2.4 ORU message | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORM-201701 | HL7 V2.4 ORM message | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORR-201701 | HL7 V2.4 ORR message | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ACK-201701 | HL7 V2.4 ACK message | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/ack/sc/deliver/hl7Ack/2012 | HL7 V2.3.1 Acknowledgement | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/ds/sc/deliver/hl7Mdm/2012 | HL7 V2.3.1 MDM Discharge Summary | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/er/sc/deliver/hl7Mdm/2012 | HL7 V2.3.1 MDM eReferral | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/es/sc/deliver/hl7Mdm/2012 | HL7 V2.3.1 MDM Event Summary | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/shs/sc/deliver/hl7Mdm/2012 | HL7 V2.3.1 MDM Shared Health Summary | ||
http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs | http://ns.electronichealth.net.au/sl/sc/deliver/hl7Mdm/2012 | HL7 V2.3.1 MDM Specialist Letter |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |