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 lists the changes per published version, newest first. The requirements are in TA Workflow; where this guide and the TA differ, the TA applies.
Technical specification of TA Workflow 0.4. Changes since 0.3.0-draft:
supplemental-resource and supplemental-query renamed to available-resource and available-query (slices availableResource, availableQuery). A standard dataset (the Library of the ActivityDefinition or PlanDefinition in ServiceRequest.instantiatesCanonical) is a guideline, not a requirement: the Placer states per Request what it makes available in these entries, and its server supports the reads and searches behind them, not the searches of the dataset itself.information-request (nine codes in ta-workflow) and slice informationRequest (0..*) on the Coordination Task. The Fulfiller may add and remove such entries; the type is reserved for the Fulfiller.owner-assigner (Task.owner.identifier.assigner.identifier), in the CapabilityStatement of the Placer's server. Subscriptions per organization: filter owner-assigner=[system]|[value] next to owner:identifier, channel.endpoint 1..1 and from Organization.endpoint for such a Subscription; twiin-wsub-1 accepts both forms.cancelled instead of failed; the Fulfiller sets it. The Placer sets cancelled only before in-progress.statusReason: new invariant twiin-ct-9 (statusReason.text when businessStatus is awaiting-information), next to twiin-ct-8 (rejected, failed) and twiin-ct-5 (SHOULD on cancelled). executionPeriod.end is set when the status leaves in-progress.ServiceRequest.priority mustSupport with guidance; Task.priority is not used.fulfill, not businessStatus selected.reasonCode for the requesting party's reason (1..1 on the latter); statusReason carries only the answering party's reason. The existing Authorization Cancellation Request Task example moves the Fulfiller's reason to reasonCode.text.twiin-ct-8 (statusReason required when the status is rejected or failed); twiin-ct-5 now covers the status cancelled only.twiin.base.template 0.1.7 (was 0.1.6). 0.3.0-draft is published unchanged and keeps its template.hl7.terminology 7.5.0; hl7.fhir.uv.extensions.r4 pinned to 5.3.0, as TA Workflow names it as a base specification (see known-issues.md in the source repository).request-fulfillment) is removed from Requirements not expressed in artifacts. The page no longer mentions an atomic update at selection: the Placer updates its own Tasks in a way it chooses, based on their current version.for 1..1, for.reference 1..1) and refers to the Patient of ServiceRequest.subject; the selection no longer sets it. twiin-ct-3 now only requires code fulfill with businessStatus selected.http://fhir.nl/fhir/NamingSystem/ura everywhere, also on the assigner of the identifiers of HealthcareService and Location (as GF Addressing does) and in the owner-assigner Subscription example. The examples and test fixtures used the OID urn:oid:2.16.528.1.1007.3.3 for the assigner. Republished as 0.4.0-draft.Fourth draft publication, technical specification of TA Workflow 0.3.
awaiting-information and visit-scheduled in the code system and the businessStatus value set; the Coordination Task and the page Requirements not expressed in artifacts aligned with the TA sections Business status and Write access; an example added.Third draft publication, technical specification of TA Workflow 0.3.
twiin-ct-4 removed.Second draft publication, technical specification of TA Workflow 0.3, in the Twiin house style.
First draft publication, technical specification of TA Workflow 0.3. Removed from the site after 0.1.1-draft was published.