FHIR IG analytics

Resources that use this resource

Resources that this resource uses

No resources found

Narrative

Note: links and images are rebased to the (stated) source

Source1

{
  "resourceType": "CodeSystem",
  "id": "hc-endpoint-payload-type-cs",
  "meta": {
    "profile": [
      "http://hl7.org/fhir/StructureDefinition/shareablecodesystem|4.0.1"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "informative",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://ns.electronichealth.net.au/hc/ImplementationGuide/au.digitalhealth.r4.healthconnect"
          }
        ]
      }
    }
  ],
  "url": "http://ns.electronichealth.net.au/hc/CodeSystem/hc-endpoint-payload-type-cs",
  "version": "0.2.0-preview",
  "name": "AustralianEndpointPayloadTypesCodeSystem",
  "title": "HC Australian Endpoint Payload Types",
  "status": "draft",
  "experimental": true,
  "date": "2026-01-29T05:23:49+00:00",
  "publisher": "Australian Digital Health Agency",
  "contact": [
    {
      "name": "Australian Digital Health Agency",
      "telecom": [
        {
          "system": "url",
          "value": "https://www.digitalhealth.gov.au/"
        },
        {
          "system": "email",
          "value": "help@digitalhealth.gov.au"
        }
      ]
    },
    {
      "name": "Australian Digital Health Agency",
      "telecom": [
        {
          "system": "email",
          "value": "mailto:help@digitalhealth.gov.au",
          "use": "work"
        }
      ]
    }
  ],
  "description": "The Endpoint Payload Types code system defines concepts that identify well known endpoint payload types.",
  "useContext": [
    {
      "code": {
        "system": "http://terminology.hl7.org/CodeSystem/usage-context-type",
        "code": "jurisdiction"
      },
      "valueCodeableConcept": {
        "coding": [
          {
            "system": "urn:iso:std:iso:3166",
            "code": "AU",
            "display": "Australia"
          }
        ]
      }
    }
  ],
  "copyright": "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/](https://creativecommons.org/licenses/by/4.0/)",
  "caseSensitive": true,
  "valueSet": "http://ns.electronichealth.net.au/hc/ValueSet/hc-endpoint-payload-type-vs",
  "compositional": false,
  "versionNeeded": true,
  "content": "complete",
  "count": 13,
  "concept": [
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706",
      "display": "HL7 V2.4 REF message (Level 2)",
      "definition": "Simplified profile on HL7 V2.4 REF message Level 2 profile (HL7AUSD-STD-OO-ADRM-2018.1 Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706-L1",
      "display": "HL7 V2.4 REF message (Level 1)",
      "definition": "Simplified profile on HL7 V2.4 REF message Level 1 profile (HL7AUSD-STD-OO-ADRM-2018.1 Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706/RRI",
      "display": "HL7 V2.4 RRI message",
      "definition": "Profile of referral response for the simplified profile for HL7 v2.4 REF message"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORU-201701",
      "display": "HL7 V2.4 ORU message",
      "definition": "Profile on HL7 V2.4 ORU report message (HL7AUSD-STD-OO-ADRM-2018.1) Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORM-201701",
      "display": "HL7 V2.4 ORM message",
      "definition": "Profile on HL7 V2.4 ORM order message (HL7AUSD-STD-OO-ADRM-2018.1) Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ORR-201701",
      "display": "HL7 V2.4 ORR message",
      "definition": "Profile on HL7 V2.4 ORR order response message (HL7AUSD-STD-OO-ADRM-2018.1) Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-ACK-201701",
      "display": "HL7 V2.4 ACK message",
      "definition": "Profile on HL7 V2.4 ACK general acknowledgement message (HL7AUSD-STD-OO-ADRM-2018.1) Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4)"
    },
    {
      "code": "http://ns.electronichealth.net.au/ack/sc/deliver/hl7Ack/2012",
      "display": "HL7 V2.3.1 Acknowledgement",
      "definition": "Profile for ACK"
    },
    {
      "code": "http://ns.electronichealth.net.au/ds/sc/deliver/hl7Mdm/2012",
      "display": "HL7 V2.3.1 MDM Discharge Summary",
      "definition": "Discharge Summary CDA contained in MDM message"
    },
    {
      "code": "http://ns.electronichealth.net.au/er/sc/deliver/hl7Mdm/2012",
      "display": "HL7 V2.3.1 MDM eReferral",
      "definition": "eReferral CDA contained in MDM message"
    },
    {
      "code": "http://ns.electronichealth.net.au/es/sc/deliver/hl7Mdm/2012",
      "display": "HL7 V2.3.1 MDM Event Summary",
      "definition": "Event Summary CDA contained in MDM message"
    },
    {
      "code": "http://ns.electronichealth.net.au/shs/sc/deliver/hl7Mdm/2012",
      "display": "HL7 V2.3.1 MDM Shared Health Summary",
      "definition": "Shared Health Summary CDA contained in MDM message"
    },
    {
      "code": "http://ns.electronichealth.net.au/sl/sc/deliver/hl7Mdm/2012",
      "display": "HL7 V2.3.1 MDM Specialist Letter",
      "definition": "Specialist Letter CDA contained in MDM message"
    }
  ]
}