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

Example Appointment/2docs (XML)

Patient Administration Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Device, Patient, Practitioner, RelatedPerson

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

Jump past Narrative

Appointment between 2 doctors to discuss MRI results (id = "2docs")

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

<Appointment xmlns="http://hl7.org/fhir">
  <id value="2docs"/> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">Discussion of Peter's ultrasound results to plan ongoing treatment options</div> 
  <status value="booked"/> 
      <system value="http://example.org/service-category"/> 
      <code value="gp"/> 
      <display value="General Practice"/> 
        <code value="52"/> 
        <display value="General Discussion"/> 
      <system value="http://snomed.info/sct"/> 
      <code value="394814009"/> 
      <display value="General practice (specialty)"/> 
      <system value="http://terminology.hl7.org/CodeSystem/v2-0276"/> 
      <code value="FOLLOWUP"/> 
      <display value="A follow up visit from a previous appointment"/> 
  <description value="Discussion about Peter Chalmers ultrasound results"/> 
    <reference value="DiagnosticReport/ultrasound"/> 
  <start value="2013-12-09T09:00:00Z"/> 
  <end value="2013-12-09T11:00:00Z"/> 
    <text value="Clarify the results of the ultrasound to ensure context of test was correct"/> 
    <reference value="Patient/example"/> 
    <display value="Peter James Chalmers"/> 
      <reference value="Practitioner/example"/> 
      <display value="Dr Adam Careful"/> 
    <required value="true"/> 
    <status value="accepted"/> 
      <reference value="Practitioner/f202"/> 
      <display value="Luigi Maas"/> 
    <required value="true"/> 
    <status value="accepted"/> 

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.