Task (/Requests)
| Type | Use Cases | Suggested Standards |
|---|---|---|
| Resource | How do we ask for another person, device or system to do something? | FHIR Workflow |
Common use cases include:
- laboratory orders
- social insurance and prescription claims
- referrals
- prescriptions
- administrative requests
Event Notifications is often used with Requests, together they form a workflow interaction and are naturally related. For example:
- Following a referral, a referrer would be sent admission and discharge notifications.
- Following a prescription, the prescriber would be sent dispense and/or medication admission notifications.
The interactions used in Requests are the same as the methods described for Events in the previous section.
FHIR Workflow
In FHIR Workflow it is assumed patient care records are shared. So neither the Request or Event notification will contain patient care records (except in certain circumstances).
A receiver of a request (filler) will use Sharing Patient Care Data API's (or clinical portals, summary records, etc applications) to view the patients record. When the request is actioned, the filler will issue event notifications to inform other care provider of important events.
Invocations
[base]/ClaimResponse?request=Claim/[id]
Details
| Resource | Code | Type | FhirPath | Xpath (Normal) |
| ClaimResponse | request | reference | ClaimResponse.request | f:ClaimResponse/f:request |
Similarly, the receiver of events with use Sharing Patient Care Data API's (or sharing applications) to view details on the received events.