Twiin Workflow
0.4.0-draft - Draft – normative only when referenced by the Twiin afsprakenstelsel

This page is part of the Twiin Workflow (v0.4.0-draft: Release 1 Draft) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Example: sharing additional content

This page is informative. It shows how the Placer shares additional content in Task.input, before and after selection, and how a candidate asks for information. The requirements are in the TA: Sharing additional content; Business status; Patient context and readability.

One Placer, one Patient, one Request and one candidate, the HealthcareService wondzorg-thuis. The type of work is SNOMED CT 308292007 (eOverdracht).

Steps

Step What happens Instance
1 Before selection the Placer invites the candidate and adds an entry to input with its content inline, not as a reference, since before selection a candidate may read the Request but not the Patient or other resources at the Placer. The content does not identify the patient. Content shared
2 The candidate accepts, sets businessStatus awaiting-information and states in statusReason.text what it needs. Awaits information
3 The Placer answers by updating input: it adds an entry, again with its content inline. Placer answers
4 The candidate removes businessStatus and statusReason. Has the information
5 The Placer selects the candidate and, in the same update, adds an entry with type available-resource that refers to a resource at the Placer, here an updated wound assessment. Selected

Reading the instances

  • Instances with the same Task.identifier are the same Coordination Task in successive states. The TA requires ids to be stable (TA section Identifiers of Tasks and Subscriptions): in reality the id of the Task does not change. The ids differ here only because the IG holds one instance per id.
  • The types Dressing type and Dressing change interval of the entries before selection are fictitious. They are not codes of the TA: the care domain defines the type of such entries, and the use case defines the type and states why the content is not identifying (TA section Patient context and readability). The TA defines the types available-resource and available-query, which the Placer adds at selection (at creation in the Single Fulfiller Pattern, or where the use case makes the Patient readable before selection), and information-request, which only the Fulfiller sets; see scenario 7 on Example scenarios.
  • The Placer sets the entries of Task.input, except entries with type information-request, which the Fulfiller may add and remove; the Fulfiller changes businessStatus and statusReason (TA section Write access). In step 2 the candidate could also have stated its question in an information-request entry.
  • In step 5 the Placer sets selected, which is reserved for the Placer (TA section Write access).