Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3 R2

12.16.8 12.15.9 Resource Schedule - Mappings

Maturity Level : N/A
Responsible Owner: Patient Administration icon Work Group Standards Status : Informative Security Category : Business Compartments : Device , Patient , Practitioner , RelatedPerson

Mappings:

FiveWs Pattern Mapping

RIM Mapping

iCalendar

Mappings for the schedule Schedule resource (see Mappings to Other Standards for further information & status).

12.16.8.1 12.15.9.1 FiveWs Pattern Mapping ( http://hl7.org/fhir/fivews icon )

Schedule workflow.scheduling
    identifier FiveWs.identifier
    active FiveWs.status
    serviceCategory FiveWs.class
    serviceType FiveWs.class
    specialty FiveWs.class
    actor FiveWs.subject[x] FiveWs.subject
    planningHorizon FiveWs.planned

12.16.8.2 12.15.9.2 RIM Mapping ( http://hl7.org/v3 icon )

Schedule n/a

12.16.8.3 12.15.9.3 iCalendar ( http://ietf.org/rfc/2445 icon )

Schedule BEGIN:VFREEBUSY ??? END:VFREEBUSY (If your fhir server provides this information via calDAV, then you may want to include addressing information in a URL section, and with the search, a DTSTART and DTEND component can be included to indicate the range of time that has been covered in the collection of slots, where these overlap the resources period values. For all slots that reference this resource, include a FREEBUSY row for each slot)
    identifier UID
    active
    serviceCategory
    serviceType n/a
    specialty
    name
    actor ATTENDEE:MAILTO:john_public@host2.com This can be populated with a value from the referenced resource
    planningHorizon DTSTART:20131201T003000Z DTEND:2014030101T003000Z
    comment COMMENT:(comment) If there is no comment, then the line can be excluded from the iCalendar entry