Repository navigation
v1.30.0
FHIR is now a plugin pack in a repository of its own, dhis2w-fhir, with its history, the way the browser automation and the MCP server became packs in 1.29.0. The host is now the DHIS2 client, the core plugins and the d2w CLI.
Installing FHIR support
dhis2w-cli no longer installs FHIR by itself. Ask for it with the [fhir] extra, and add [serve] for the capture server:
uv tool install "dhis2w-cli[fhir]"
uv tool install "dhis2w-cli[fhir,serve]"Without the pack, d2w fhir prints that install command instead of "No such command". d2w browser and d2w security do the same.
A FHIR project scaffolded by d2w fhir init lists dhis2w-fhir and dhis2w-fhir-serve among its own dependencies, so make update keeps working unchanged.
What moved
| Package | Repository | Documentation |
|---|---|---|
dhis2w-fhir, dhis2w-fhir-engine, dhis2w-fhir-serve |
dhis2w-fhir | site |
The package names, d2w fhir and its commands, the capture UI and the engine's API are unchanged. The FHIR pages redirect to the pack's site. The canonical OperationDefinition pages that FHIR artifacts cite stay published where they are.
dhis2w-fhir 1.30.0 releases from its own repository after this release. Until then, [fhir] installs 1.29.0.