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
This page is informative. It lists the artifacts in this guide and the section of TA Workflow each one belongs to. The requirements themselves are in the TA.
| Artifact | Based on | TA section |
|---|---|---|
| Twiin Coordination Task | coordination-task (COW IG 1.0.0-ballot) |
Summary of the profiles → Coordination Task; Coordination Task; Status of the Coordination Task; Patient context and readability; Type of work on the Task; Sharing additional content; Search parameters |
| Twiin Cancellation Request Task | cancellation-request-task (COW IG 1.0.0-ballot) |
Summary of the profiles → Cancellation Request Task; Cancellation Request Task |
| Twiin Authorization Cancellation Request Task | Task (FHIR R4) |
Summary of the profiles → Authorization Cancellation Request Task; Cancellation by the Fulfiller |
| Twiin Workflow ServiceRequest | ServiceRequest (FHIR R4) |
Summary of the profiles → ServiceRequest; Request; Patient context and readability. priority is mustSupport. |
| Twiin Workflow Subscription | twiin-subscription (Twiin Notifications 0.2.0-draft) |
Subscription |
Task.owner and Task.location refer to a HealthcareService and a Location, with the type and a complete identifier (system, value and the identifier of its assigner) required. That they are profiled by GF Addressing is not expressed in the artifacts of this guide (see Requirements not expressed in artifacts). The invariant twiin-aid-1 excludes an assigner identified by a KvK number; the profiles do not fix the system of the assigner. The URA is always identified with the system http://fhir.nl/fhir/NamingSystem/ura, on the assigner as on Task.requester, as in GF Addressing.
COW IG defines no profile for the Authorization Cancellation Request Task. Its requester is the Fulfiller as an organization, identified by its URA, as its owner is the Placer: FHIR R4 does not allow Task.requester to refer to a HealthcareService (TA section Summary of the profiles → Authorization Cancellation Request Task).
Some constraints interpret the TA:
available-resource and available-query on the Coordination Task are optional slices that fix the value type (TA section Sharing additional content). The slice informationRequest (type information-request) does not constrain value[x], since the TA does not fix the form of the request.twiin-wsub-1 checks the form owner:identifier=[system]|[value] or owner-assigner=[system]|[value] of the filter; it cannot check that the identifier is that of a HealthcareService or the URA of an organization.twiin-task-1 (statusReason.text when statusReason is populated) applies to all three Task profiles, as in the three tables of the TA.| Key | Severity | Profile | Rule |
|---|---|---|---|
twiin-ct-1 |
error | Coordination Task | The statuses draft, ready and on-hold are not used |
twiin-ct-2 |
error | Coordination Task | statusReason not-selected only when the status is cancelled |
twiin-ct-3 |
error | Coordination Task | businessStatus selected implies code fulfill |
twiin-ct-5 |
warning | Coordination Task | statusReason when the status is cancelled |
twiin-ct-6 |
warning | Coordination Task | for.identifier is not populated |
twiin-ct-7 |
error | Coordination Task | status in-progress or completed implies code fulfill |
twiin-ct-8 |
error | Coordination Task | statusReason when the status is rejected or failed |
twiin-ct-9 |
error | Coordination Task | statusReason.text when businessStatus is awaiting-information |
twiin-crt-1 |
error | Cancellation Request Task | status requested, accepted, rejected, cancelled or entered-in-error |
twiin-acrt-1 |
error | Authorization Cancellation Request Task | status requested, accepted or rejected |
twiin-task-1 |
warning | all Task profiles | statusReason.text when statusReason is populated |
twiin-aid-1 |
error | Coordination Task, Cancellation Request Task | The assigner of the identifier of a HealthcareService or Location is not a KvK number |
twiin-sr-1 |
error | ServiceRequest | subject is not masked with data-absent-reason |
twiin-wsub-1 |
error | Subscription | Filter of the form owner:identifier=[system]|[value] or owner-assigner=[system]|[value] |
| Artifact | TA section |
|---|---|
| TA Workflow Codes | Codes of this TA |
| TA Workflow Task Code | Codes of this TA |
| Artifact | TA section |
|---|---|
| Task owner-assigner | Search parameters; Subscription |
| Artifact | TA section |
|---|---|
| Twiin Workflow Placer Server | Placer server capabilities; Concurrent writes; Search parameters |
The capability statement imports the Twiin Subscription Server of TA Notifications for Subscription. Support for the modifier :identifier, and that create on Task is only for the Authorization Cancellation Request Task, are stated in documentation, because a CapabilityStatement has no element for them.
| Example | TA section |
|---|---|
| ServiceRequest: transfer of care | Request; Patient context and readability |
| ServiceRequest: no definition | Request; Routing by the Fulfiller |
| Patient | Patient context and readability |
| Coordination Task: candidate invited | Multiple Fulfillers Pattern; Sharing additional content; Patient context and readability |
| Coordination Task: candidate selected | Multiple Fulfillers Pattern; Bidding |
| Coordination Task: candidate not selected | Reason for cancelling a non-selected candidate |
| Coordination Task: single Fulfiller, in progress | Single Fulfiller Pattern; Sharing additional content |
| Coordination Task: single Fulfiller, awaiting information | Single Fulfiller Pattern; Business status |
| Cancellation Request Task | Cancellation Request (After in-progress) |
| Authorization Cancellation Request Task | Cancellation by the Fulfiller |
| Subscription for a HealthcareService | Subscription |
The page Example scenarios shows the main scenarios with their own instances. The page Example: reselection shows one scenario in the Multiple Fulfillers Pattern with its own instances. The page Example: sharing additional content shows how the Placer shares content in Task.input and how a candidate asks for information.
The examples are not taken from the TA, which contains none. Hosts, identifiers, the topic URL and the ActivityDefinition URL are invented; the type of work uses SNOMED CT 308292007, which the TA names as the code of eOverdracht.