Snapshot 3: Connectathon 32 Base

This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.

Example Schedule/example (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

Example of an Schedule resource (id = "example")

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

<Schedule xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      Burgers UMC, South Wing, second floor Physiotherapy Schedule
    </div> 
  </text> 
  <identifier> 
    <use value="usual"/> 
    <system value="http://example.org/scheduleid"/> 
    <value value="45"/> 
  </identifier> 
  <active value="true"/> 
  <serviceCategory> 
    <coding> 
      <system value="http://terminology.hl7.org/CodeSystem/service-category"/> 
      <code value="17"/> 
      <display value="General Practice"/> 
    </coding> 
  </serviceCategory> 
  <serviceType> 
    <concept> 
      <coding> 
        <system value="http://terminology.hl7.org/CodeSystem/service-type"/> 
        <code value="57"/> 
        <display value="Immunization"/> 
      </coding> 
    </concept> 
  </serviceType> 
  <specialty> 
    <coding> 
      <system value="http://snomed.info/sct"/> 
      <code value="408480009"/> 
      <display value="Clinical immunology"/> 
    </coding> 
  </specialty> 
  <actor> 
    <reference value="Location/1"/> 
    <display value="Burgers UMC, South Wing, second floor"/> 
  </actor> 
  <planningHorizon> 
    <start value="2013-12-25T09:15:00Z"/> 
    <end value="2013-12-25T09:30:00Z"/> 
  </planningHorizon> 
  <comment value="The slots attached to this schedule should be specialized to cover immunizations
   within the clinic"/> 
</Schedule> 

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.