A cross-stack reference toolkit for the Open Health Stack that enables implementors to plug, play, and deploy OHS components with minimal effort. Covering the full stack from KMP mobile client to analytics pipeline.
6
Workstreams
5 / 6
On track
~85%
Overall progress
Jul 10
Alpha target
Target release: v1.0.0-alpha | July 10, 2026
Dependency layer
OHS Foundational Components (KMP Libraries)
The core Kotlin Multiplatform libraries being migrated from the original Android FHIR SDK to support Android, iOS, desktop, and web. These underpin the OHS Player client app and are tracked separately by the OHS Foundation.
OHS Player v1.0.0-alpha uses available snapshots and pre-release builds. Some library releases are still in progress and will be finalised in July alongside the player release.
kotlin-fhirv1.0.0-beta05
kotlin-fhirpathv1.0.0-beta03
kotlin-fhir-data-capturev2.0.0-alpha02
kotlin-fhir-enginebeta July
v1.0.0-alpha delivery
Workstream Status
Click any workstream to see the delivery details, epics, and what is planned for v2.
Done In progress Pending
📱
Client App
Kotlin Multiplatform reference app | Android, iOS, Desktop, Web
90%
On track
v1 goal: A configurable reference app where UI, data elements, and simple workflows can be set via configuration files based on a FHIR Implementation Guide. Covers FHIR SDC data capture and template-based extraction across Android, iOS, Desktop, and Web from a single Kotlin source tree. The app renders healthcare UI from configuration rather than hand-written mapping code.
v1 epics
Data Transformation — FHIR resources projected into typed view-state via declarative configDone
Configuration Engine — config parsing and workflow mapping from a FHIR IG, including views and registersDone
Data Capture & Extraction — FHIR SDC questionnaire rendering and template-based extractionDone
CI/CD and platform targets — Android, iOS, Desktop, Web buildsDone
Reference use case — community health / immunization end-to-end scenarioIn progress
Documentation and packagingIn progress
Sync with the FHIR Gateway is planned for v2 and depends on the upcoming kotlin-fhir-engine beta release in July.
FHIR Information Gateway | access control and custom endpoints
90%
On track
v1 goal: A fully extensible FHIR Gateway layer that brings together the FHIR Information Gateway, Keycloak, and any FHIR server (HAPI, Smile, Google Health API) to provide authentication, access control, and all backend APIs required by both the Web Admin portal and the KMP client app. Enables healthcare organisations to manage users, roles, and organisational hierarchies that form the foundation for patient data access control. Implementors can extend the gateway with custom endpoints and access checkers without modifying core code.
v1 epics
Plugin Architecture — custom endpoints and access checkers loaded into FHIR Gateway at runtimeDone
OIDC / Keycloak integration — auth flows and token handlingDone
User Management API — transactional Practitioner and Keycloak account creationDone
Web Admin APIs — user, role, organisation, and CareTeam management endpointsDone
Location hierarchy API — location CRUD and hierarchy management endpointIn progress
End-to-end setup — multi-level setup support via existing APIsDone
FHIR Resource Browser API — backend support for patient data browsingPending
FHIR Resource Browser API is pending but on track for July 10. Location hierarchy completion unblocks both this and the Web Portal location management feature.
Browser-based admin and programme management interface
85%
On track
v1 goal: A web-based administration interface for programme administrators and officials. Administrators manage user accounts, team structure, and location hierarchies with role assignments and organisational relationships reflected immediately in mobile sync scoping. Programme officials can navigate structured patient records via an integrated FHIR resource browser, with clinical resources organised by programme and date providing longitudinal programme-level visibility.
FHIR Browser — patient data timeline and clinical resources via Cinder integrationPending
FHIR Browser reuses the Cinder implementation and is on track for July 10. Sync scoping for mobile is driven by the user assignments configured here, not by the web portal itself.
Planned for v2
Adoptable UI widgets and configurable layoutRole-based access and approval workflowsBulk CSV/Excel import (users, locations, orgs)District-level admin scoping
FHIR Data Pipes pipeline | PostgreSQL | Apache Superset
75%
On track
v1 goal: A reference analytics pipeline built on FHIR Data Pipes that automatically flattens FHIR resources from both the OHS Player client app and the Web Admin into analytics-ready tables. Gives programme officials ready-made dashboards and indicator views without writing FHIR queries, and serves as a starting point for implementors to build programme-specific analytics. Pipeline: OHS Player app and Web Admin → HAPI FHIR → FHIR Data Pipes → PostgreSQL → Apache Superset.
v1 epics
Test data — 10k patients across 11 resource types (community health use case)Done
Reference deployment scripts and Docker Compose configuration
80%
On track
v1 goal: Reference deployment scripts and Docker Compose configuration enabling any implementor to spin up the complete OHS Player stack in a local environment with a single command. Covers HAPI FHIR, FHIR Information Gateway, Keycloak, Web Admin, and Analytics pipeline. The fastest path from zero to a running OHS reference demo for development, testing, and evaluation.
v1 epics
Core local environment — Docker Compose bundle with HAPI FHIR, Keycloak, FHIR Info GatewayDone
App build and signing — KMP build pipeline, Android and iOS signingDone
Extended stack — Data Pipes, Web Admin, and Analytics containers (pending analytics)90%
Documentation and deployment guides — end-to-end setup instructionsIn progress
Public demo instance — hosted environment for evaluation (pending client and web use cases)Pending
Overall progress is dependent on completion of the client app use case and Web Admin. Both are on track, keeping infrastructure on schedule for July 10.
Docusaurus docs site | release packaging | community landing page
40%
In progress
v1 goal: Everything a programme implementor, product owner, or engineer needs to go from zero to running the OHS Player reference stack in the least time possible. Covers setup, configuration, and deployment across all workstreams. Includes a community-facing landing page for the OHS Player project and versioned release artefacts.
v1 epics
Documentation site — end-to-end guides hosted on DocusaurusIn progress
OHS Player landing page — community-facing overview and getting startedIn progress
Test plan — post-release validation plan (kicks off 2 weeks after July 10)Post-release
Documentation is a cross-cutting workstream and is being written in parallel with each workstream reaching completion. Packaging and release notes are finalised at release time.
Notes
Sync dependency
Client sync with the FHIR Gateway depends on the kotlin-fhir-engine beta release, expected July 2026. OHS Player v1 uses available snapshots. Sync is planned for v2 and is not a blocker for the July 10 alpha.
Post-release
A structured test plan kicks off approximately two weeks after the July 10 release. Community feedback and issue triage will run in parallel through the OHS Foundation channels.
Overall confidence
All six workstreams are on track for the July 10 target. The main cross-workstream dependency is the client app use case and Web Admin completing, which unblocks the analytics dev instance and the public demo.
What comes next
v2 and beyond
See the full delivery roadmap covering v1.1.0-beta (Interoperability and Workflows), v1.2.0-GA (Production Blueprints), and the longer-term vision for the OHS Player platform.