Clinical Order Workflows
1.0.0-ballot - STU 1 Ballot

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

## IG Artifacts

Page standards status: Informative

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

ActivityResource | Search on the resources that are linked to a RequestGroup - important to allow for example _revInclude
GroupOrIdentifier | Single search that incides on both request.identifier or groupIdentifier

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

COW Message Header | Minimum expectations for a MessageHeader resource when used for Clinical Order Workflow. This profile is used to describe the use of FHIR Messaging when RESTful-based exchange is not possible between the Placer and the Fulfiller. The purpose of the constraints for the MessageHeader resource is to make sure that the rest of the Clinical Workflow requirements that may be relevant to a particular implementation or national/regional implementation guides are compatible with the RESTful-based exchange patterns.
COW Subscription Notification | The backported SubscriptionNotification bundle shall contain the backported SubscriptionStatus resource
COW Subscription Status | Minimum expectations for a SubscriptionStatus resource when used for Clinical Order Workflow. This profile is used to describe the use of administrative (pre-coordinated) subscription notifications for RESTful-based exchange between the Placer and the Fulfiller. The purpose of the constraints for the SubscriptionStatus resource is to make sure that additional requirements, which may be relevant to a particular implementation or national/regional implementation guides, are compatible with the RESTful-based exchange patterns.
Cancellation Request Task | A task to indicate a Placer-initiated cancellation of a request fulfillment.
Coordination Task | Minimum expectations for a Task resource when created or updated for the purpose of managing the workflow for performing a request. This profile is used to describe the 'please fulfill' request from either a known performer, or by one who is yet to be determined. The information is obtained RESTfully by the recipient either via polling, or as the result of a subscription notification about the existence of the Task resource

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Clinical Orders Workflow - Message Header Event Codes | Value Set containing the codes from the COW Business Status code system.
Clinical Orders Workflow Business Status Codes | This value set is the full expansion of the COW Business Status code system.
Order Notification Status Type | The type of notification represented by the status message.

### Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Subscription Notification Type | The type of notification represented by the status message.
Temp Clinical Order Workflow Example Codes | This code system contains codes for Task.businessStatus and MessageHeader event code. These are example codes, not intended to be used as is

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

COW Authorization Cancellation Task | Example of a COW cancellation task created by the Fulfiller in order to request from the Placer that the authorized service is cancelled.
COW Coordination Task | Example of a COW 'please fulfill' coordination task
COW Fulfillment Cancellation Task | Example of a COW cancellation task created by the Placer in order to indicate to the Fulfiller that their execution of the request needs to be cancelled.
COW MessageHeader Example | COW example of a message header for an order update
COW Notification Status | Example of a COW subscription notification status
COW Notification: Status with Focus only | COW example of a Subscription Notification, where the status only points to the focal Task
COW Service Request | Example of a COW ServiceRequest for a Glucose lab test designated by https://loinc.org/2345-7
Fulfiller | COW Filler Actor - generic actor representing the party that is fulfilling an order
Placer | Order Placer Actor - generic actor representing the party that is placing an order