dhis2w-fhir-serve
FHIR facade server over a generated IG project, mounted as d2w fhir serve.
- Serves two APIs in one process: FHIR at the base URL, whose contract is the CapabilityStatement at
GET /metadata, and everything the facade answers about itself under/facade, whose contract is its own OpenAPI document atGET /facade/openapi.json(readable as a page at/facade/docs). CDS Hooks discovery stays atGET /cds-services, where that specification fixes it. - Reads a project's compiled IG (
ig/fsh-generated/resources) plus its predefined resource trees (ig/input/resources) into an in-memoryResourceStorea FHIR client can read and search. - Receives QuestionnaireResponse captures into a
ResponseSpool: atomic writes to<project>/.serve/responses/received, and reads that re-read the directory so ad2w fhir forwardrun beside the server is visible immediately. - Lists the whole spool with its lifecycle state at
GET /facade/spool- received, forwarded, or rejected beside the DHIS2 import report that says why. - Answers about the instance itself on a
--liverun: the register (GET /{RegisterType}), one entity's enrollments, and one entity's record atGET /facade/tracked-entities/{uid}/events- every event of its enrollments as the QuestionnaireResponse its programme stage's published form describes, read per request under the credentials of whoever asked. - Answers the aggregate half beside it:
GET /facade/data-sets/{uid}/responses?orgUnit=&period=- what the instance holds for one data set, at one organisation unit, over the periods the request names, one QuestionnaireResponse per reporting key in the shape that data set's published form describes.
The store is byte-faithful: a resource is served exactly as SUSHI emitted it. A stored response is the submission as received - a receipt, never a live view of DHIS2 data; the record at /facade/tracked-entities/{uid}/events and the reported forms at /facade/data-sets/{uid}/responses are the live view, and they are different addresses.
1 maintainer
Metadata
1 maintainer
Release files for dhis2w-fhir-serve 1.32.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dhis2w_fhir_serve-1.32.0.tar.gz | 1.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dhis2w_fhir_serve-1.32.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 MB
Release files / dhis2w_fhir_serve-1.32.0.tar.gz
| Download URL | dhis2w_fhir_serve-1.32.0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa99e04879bda128af7b2cdd107c3e235364f74377136000f037b59a2b9d425b
|
|
BLAKE2b-256 checksum How to use checksums |
d44aa526d36d5deb9875cf14723e995254eeb7eff0b9897a0c0e415a2d14e1a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dhis2w_fhir_serve-1.32.0-py3-none-any.whl
| Download URL | dhis2w_fhir_serve-1.32.0-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1bbd035843692f029094cc9bf6085fd046c60508b0cc7a905f1373ff86534cd5
|
|
BLAKE2b-256 checksum How to use checksums |
3f6baf8f1d64765373b880c6c1cd1f74a595e1a5bcf50f8397f10690bc72dd7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log
