Twiin Workflow
0.3.0-draft - Draft – normative only when referenced by the Twiin afsprakenstelsel
Twiin Workflow
0.3.0-draft - Draft – normative only when referenced by the Twiin afsprakenstelsel
This page is part of the Twiin Workflow (v0.3.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
One dependency of this implementation guide is not on the FHIR package registry (packages.fhir.org), so SUSHI, the IG Publisher and the validator cannot download it:
| Package | URL | sha-256 |
|---|---|---|
nl.twiin.fhir.r4.notifications#0.2.0-draft |
https://fhir.twiin.nl/ig/notifications/0.2.0-draft/package.tgz | 041cb3d7b5f4fad02d46dec47c1f6e350a9441f522c394776269ff6fddc1f995 |
This is the URL and checksum used in the CI of this guide.
The tools read packages from the local FHIR package cache, <home directory>/.fhir/packages. A package sits in a folder <id>#<version>, with the contents of the tarball in a subfolder package. For the package:
curl -sSfL -o package.tgz <URL>
echo "<sha-256> package.tgz" | shasum -a 256 -c -
mkdir -p ~/.fhir/packages/<id>#<version>
tar xzf package.tgz -C ~/.fhir/packages/<id>#<version>
For example, for nl.twiin.fhir.r4.notifications#0.2.0-draft the result is ~/.fhir/packages/nl.twiin.fhir.r4.notifications#0.2.0-draft/package/package.json. Do not continue when the checksum differs.
SUSHI, the IG Publisher and the validator find the packages in the cache without further configuration, as long as the version in the dependency of the guide equals the folder name.
The source repository of this guide has a script that does this, including the checksum check: .github/scripts/install-packages.sh.
| IG | Package | FHIR | Comment |
|---|---|---|---|
  Twiin Workflow | nl.twiin.fhir.r4.workflow#0.3.0-draft | R4 | |
 HL7 Terminology (THO) | hl7.terminology.r4#7.4.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
| FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.3.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack |
 Clinical Order Workflows | hl7.fhir.uv.cow#1.0.0-ballot | R4 | |
 HL7 Terminology (THO) | hl7.terminology.r4#6.2.0 | R4 | |
| FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.2.0 | R4 | |
 Subscriptions R5 Backport | hl7.fhir.uv.subscriptions-backport.r4#1.1.0 | R4 | |
  HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 | |
| Twiin Notifications | nl.twiin.fhir.r4.notifications#0.2.0-draft | R4 | |
 FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#1.3.0 | R4 | for example references |
Package hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.uv.subscriptions-backport.r4#1.1.0 The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Jan 11, 2023 15:34+1100+11:00) |
Package hl7.fhir.uv.cow#1.0.0-ballot An Implementation Guide providing the foundational guidance for order-based workflow FHIR interoperability (built Mon, Apr 7, 2025 15:35+0000+00:00) |
Package nl.twiin.fhir.r4.notifications#0.2.0-draft Technical specification of TA Notifications, part of the technical core of the Twiin Afsprakenstelsel. Based on the HL7 FHIR Subscriptions R5 Backport IG. (built Thu, Oct 15, 2026 14:58+0000+00:00) |
Package hl7.fhir.uv.tools.r4#1.3.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Oct 6, 2026 15:55+1100+11:00) |
This publication includes IP covered under the following statements.
There are no Global profiles defined
$USER_HOME/.fhir/packages)"; for the IG Publisher and validator, FilesystemPackageCacheManager in hapifhir/org.hl7.fhir.core (user.home, .fhir, packages; folder <id>#<version>). The specification only says that tools may use a common local cache (FHIR packages, FHIR Package Caching).package subfolder follows from the layout of the tarballs and was checked against the cache of a working local build.