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 at GET /facade/openapi.json (readable as a page at /facade/docs). CDS Hooks discovery stays at GET /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-memory ResourceStore a 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 a d2w fhir forward run 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 --live run: the register (GET /{RegisterType}), one entity's enrollments, and one entity's record at GET /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.

Release files for dhis2w-fhir-serve 1.19.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dhis2w-fhir-serve 1.19.0
File	Size	Uploaded
dhis2w_fhir_serve-1.19.0.tar.gz	1.5 MB	Sep 11, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for dhis2w-fhir-serve 1.19.0
File	Interpreter	ABI	Platform	Reset
dhis2w_fhir_serve-1.19.0-py3-none-any.whl 1.6 MB Sep 11, 2026	Python 3	none	any	Details

Total release size: 3.2 MB

Release files / dhis2w_fhir_serve-1.19.0.tar.gz

Download URL	dhis2w_fhir_serve-1.19.0.tar.gz
Size	1.5 MB
Tags	Source
SHA-256 checksum How to use checksums	`7273d0b559d58e7e56ee37d63c4217404269c3308524e42de0a1046944cc3a6b`
BLAKE2b-256 checksum How to use checksums	`adce2162419b00ede4eb2117a4c9f9739dc5e3dfc0a4760142c52141848ad188`
Upload date	Sep 11, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/winterop-com/dhis2w
Publishing commit: github.com/winterop-com/dhis2w/tree/eb571fee3e7335ecae541fb6346ec1945ee6a4f1

Workflow

Publishing configuration: github.com/winterop-com/dhis2w/blob/eb571fee3e7335ecae541fb6346ec1945ee6a4f1/.github/workflows/pypi-publish.yml
Publishing logs: github.com/winterop-com/dhis2w/actions/runs/34634114607/attempts/1

Artifact

Subject: dhis2w_fhir_serve-1.19.0.tar.gz
SHA-256 checksum: 7273d0b559d58e7e56ee37d63c4217404269c3308524e42de0a1046944cc3a6b Verifying attestations

Release files / dhis2w_fhir_serve-1.19.0-py3-none-any.whl

Download URL	dhis2w_fhir_serve-1.19.0-py3-none-any.whl
Size	1.6 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`a6d57e26166ae4545dda4093b3327561a77d213eec3fc304157a470ed75b00ae`
BLAKE2b-256 checksum How to use checksums	`551bb7946eb02343fecb989adcba5e5ec65a0f37e56cc4ce186bbfa01f889466`
Upload date	Sep 11, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/winterop-com/dhis2w
Publishing commit: github.com/winterop-com/dhis2w/tree/eb571fee3e7335ecae541fb6346ec1945ee6a4f1

Workflow

Publishing configuration: github.com/winterop-com/dhis2w/blob/eb571fee3e7335ecae541fb6346ec1945ee6a4f1/.github/workflows/pypi-publish.yml
Publishing logs: github.com/winterop-com/dhis2w/actions/runs/34634114607/attempts/1

Artifact

Subject: dhis2w_fhir_serve-1.19.0-py3-none-any.whl
SHA-256 checksum: a6d57e26166ae4545dda4093b3327561a77d213eec3fc304157a470ed75b00ae Verifying attestations