This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
Raw XML (canonical form + also see XML Format Specification)
Showing new message definition structure (id = "messagedefinition")
<?xml version="1.0" encoding="UTF-8"?> <CapabilityStatement xmlns="http://hl7.org/fhir"> <id value="messagedefinition"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2/> <div> <p> Sample capability statement showing new MessageDefinition structure</p> </div> </div> </text> <status value="draft"/> <experimental value="true"/> <date value="2012-01-04"/> <publisher value="ACME Corporation"/> <contact> <name value="System Administrator"/> <telecom> <system value="email"/> <value value="wile@acme.org"/> </telecom> </contact> <description value="Sample capability statement showing new MessageDefinition structure"/> <kind value="instance"/> <software> <name value="EHR"/> </software> <implementation> <description value="Acme Message endpoint"/> <url value="http://acem.com/fhir/message-drop"/> </implementation> <fhirVersion value="4.0.1"/> <format value="xml"/> <format value="json"/> <messaging> <endpoint> <protocol> <system value="http://terminology.hl7.org/CodeSystem/message-transport"/> <code value="mllp"/> </protocol> <address value="mllp:10.1.1.10:9234"/> </endpoint> <reliableCache value="30"/> <documentation value="ADT A08 equivalent for external system notifications"/> <supportedMessage> <mode value="receiver"/> <definition value="MessageDefinition/example"/> </supportedMessage> </messaging> </CapabilityStatement>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.