FHIR Release 3 (STU) CI-Build

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Capabilitystatement-messagedefinition.xml

Example CapabilityStatement/messagedefinition (XML)

Maturity Level : N/A
Responsible Owner: FHIR Infrastructure Work Group Ballot Standards Status : Informative Compartments : Not linked to any No defined compartments

Raw XML ( canonical form ) Jump past Narrative + 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"/> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </extension> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.34.8"/> 
  </identifier> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2012-01-04"/> 
  <publisher value="HL7 International / FHIR Infrastructure"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://www.hl7.org/Special/committees/fiwg"/> 
    </telecom> 
  </contact> 
  <description value="Sample capability statement showing new MessageDefinition structure"/> 
  <kind value="instance"/> 
  <software> 
    <name value="EHR"/> 
  </software> 
  <!--    while the FHIR infrastructure is turning over prior to development, a version
   is  
    required.     -->
  <implementation>     <description value="Acme Message endpoint"/>     <url value="http://acem.com/fhir/message-drop"/>   </implementation>   <fhirVersion value="6.0.0"/>   <!--    this system can do either xml or json. (Listing both implies full support for

   either, with interconversion)    -->
  <format value="xml"/>   <format value="json"/>   <messaging>     <endpoint>       <protocol>         <system value="http://hl7.org/fhir/message-transport"/>         <code value="mllp"/>       </protocol>       <!--   LLP server at 10.1.1.10 on port 9234   -->      <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="http://hl7.org/fhir/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.