Schedule Mappings

• Schedule: rim=n/a; ical=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); w5=workflow.scheduling
• Schedule.identifier: w5=FiveWs.identifier; ical=UID
• Schedule.active: w5=FiveWs.status
• Schedule.serviceCategory: w5=FiveWs.class
• Schedule.serviceType: w5=FiveWs.class; ical=n/a
• Schedule.specialty: w5=FiveWs.class
• Schedule.actor: w5=FiveWs.subject; ical=ATTENDEE:MAILTO:john_public@host2.com This can be populated with a value from the referenced resource
• Schedule.planningHorizon: w5=FiveWs.planned; ical=DTSTART:20131201T003000Z DTEND:2014030101T003000Z
• Schedule.comment: ical=COMMENT:(comment) If there is no comment, then the line can be excluded from the iCalendar entry