FHIR Workflow

Ad Hoc Workflow Patterns

The simplest form of FHIR Workflow involves the POST of a Request, Events relating to the request are posted back.

For Lab Results or Referrals this would be a POST /ServiceRequest for the request and POST /DiagnosticReport for the response.

For more details see FHIR Ad-Hoc Workflow Communication Patterns

Supporting information for the ServiceRequest or Observations relating to the DiagnosticReport would be shared via a Query API framework.

Standards in this guide to be used with this pattern are:

• HL7 v2 Events and Ad Hoc FHIR RESTful Events
• Command 'pagelink' could not render: Page not found.

Workflow Management Patterns

Ad Hoc workflow Patterns lack support for clinical coordination and communication (see also Workflow Events. Workflow Management Patterns do and this includes direct activities relating to a referral such as rejection or referral acceptance, sub tasks such as booking an appointment relating to a referral.

For more details see FHIR Workflow Mangement Patterns

The following is an extract of the complete set of options.

Task Exchanges between Placer and Filler

• Option F: Creation of Task on placer's system
• Option G: POST of Task to fulfiller's system

FOR Care Coordination elaboration (No broker)

Task Exchanges via a Workflow Broker

• Option H: POST of Task to a workflow broker

NHS England Systems which follow this pattern are:

• Electronic Prescription Service (EPS) (HL7 FHIR Message R4)
• Electronic Referral System (eRS)