Clinical Order Workflows, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-cow-ig/ and changes regularly. See the Directory of published versions
A practitioner orders a diet for an inpatient. The dietary system that assigns the diet and prepares the meals is the Fulfiller.
The Coordination Task is at the Fulfiller: the Placer creates it on the dietary system's FHIR server and subscribes to its updates.
The NutritionOrder remains active while it is being fulfilled. It is temporarily put on hold (for example, while the patient is fasting before a procedure) and later reactivated.
Systems can view the current diet (NutritionOrder) and the fulfillment status (Task) at any time.
The Task.businessStatus values in this example are illustrative.
Transport mechanisms and infrastructure for exchanging data about NutritionOrder and Task are provided.