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

Messagedefinition-example.xml

Example MessageDefinition/example (XML)

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

Raw XML ( canonical form + also see XML Format Specification )

Jump past Narrative

A typical message definition (id = "example") 

<?xml version="1.0" encoding="UTF-8"?>

<MessageDefinition xmlns="http://hl7.org/fhir">  <id value="example"/>   <text>     <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">Message definition base example</div>   </text>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">    <valueCode value="inm"/>   </extension>   <url value="http://hl7.org/fhir/MessageDefinition/example"/>   <identifier>     <system value="urn:ietf:rfc:3986"/>     <value value="urn:oid:2.16.840.1.113883.4.642.15.3"/>   </identifier>   <name value="EXAMPLE"/>   <title value="Message definition base example"/>   <status value="draft"/>   <experimental value="true"/>   <date value="2016-11-09"/>   <publisher value="HL7 International / Infrastructure And Messaging"/>   <contact>     <telecom>       <system value="url"/>       <value value="http://www.hl7.org/Special/committees/inm"/>     </telecom>   </contact>   <description value="Message definition base example"/>   <purpose value="Defines a base example for other MessageDefinition instances."/>   <eventCoding>     <system value="http://example.org/fhir/message-events"/>     <code value="admin-notify"/>   </eventCoding>   <category value="notification"/> 


</

MessageDefinition

>

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.