This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example MessageHeader/1cbdfb97-5859-48a4-8301-d54eab818d68 (XML)

Infrastructure And Messaging Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Device, Practitioner

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

Jump past Narrative

A typical message header (id = "1cbdfb97-5859-48a4-8301-d54eab818d68")

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

<MessageHeader xmlns="http://hl7.org/fhir">
  <id value="1cbdfb97-5859-48a4-8301-d54eab818d68"/> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Update Person resource for Peter James CHALMERS (Jim), MRN: 12345 (Acme Healthcare)</p> 
    <system value="http://example.org/fhir/message-events"/> 
    <code value="admin-notify"/> 
    <endpointUrl value="llp:"/> 
    <name value="Acme Message Gateway"/> 
      <!--   this is to indicate to the Acme Message Gateway that this particular message
       is intended for Practitioner "xcda"   -->
      <reference value="http://acme.com/ehr/fhir/Practitioner/2323-33-4"/> 
    <reference value="Organization/1"/> 
    <!--     <timestamp value="2012-01-04T09:10:14Z"/>   -->
    <reference value="Practitioner/example"/> 
    <endpointUrl value="llp:"/> 
    <name value="Acme Central Patient Registry"/> 
    <software value="FooBar Patient Manager"/> 
    <version value="3.1.45.AABB"/> 
      <system value="phone"/> 
      <value value="+1 (555) 123 4567"/> 
      <system value="http://terminology.hl7.org/CodeSystem/message-reasons-encounter"/> 
      <code value="admit"/> 
      <value value="5015fe84-8e76-4526-89d8-44b322e8d4fb"/> 
    <code value="ok"/> 
    <!--   Here's the payload, the resource that this admin-update concerns   -->
    <reference value="Patient/example"/> 
  <definition value="http:////acme.com/ehr/fhir/messagedefinition/patientrequest"/> 

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.