Delivery roadmap

Three horizons of
OHS Player

From the foundational MVP sandbox in July 2026 through to production-ready cloud blueprints. Each horizon builds on the previous, progressively enabling more of the OHS stack for real-world digital health deployments.

v1.0.0-alpha
Horizon 1: The MVP Sandbox
Establishing the foundational boilerplate and core OHS SDK functionality in a local environment. A fully working reference stack that any team can spin up and evaluate.
In progress Target: July 10, 2026
Overall status: on track. Five of six workstreams are above 80% complete. The cross-workstream dependency is the client app reference use case and Web Admin completing, which unblocks the analytics dev instance and the public demo. All workstreams remain on schedule for July 10.
Configurable reference app from FHIR IG
Data Transformation (FHIR resources to view-state)
FHIR SDC data capture and template-based extraction
Authentication (PKCE online, PIN offline)
Android, iOS, Desktop and Web builds
Reference use case (community health)
Plugin architecture (custom endpoints and access checkers)
OIDC / Keycloak integration
User management API (Practitioner and Keycloak)
Web Admin APIs (user, org, CareTeam)
Location hierarchy API
FHIR Resource Browser API
Foundational components and design system
User and role management
Organisation and CareTeam management
Location hierarchy UI
End-to-end setup wizard
FHIR Browser (Cinder integration)
ViewDefinitions (11 resource types)
Reference indicator SQLs (12 indicators)
Test data (10k patients, community health)
Reference Superset dashboard and audit trail view
Dev instance deployment
Core Docker Compose bundle (HAPI FHIR, Keycloak, Gateway)
App build and signing pipeline
Extended stack (Data Pipes, Web Admin, Analytics)
Docusaurus documentation site
Public demo instance
v1.1.0-beta
Horizon 2: Interoperability and Workflows
Transitioning to remote orchestration, advanced data filtering and synchronisation, and automated administrative workflows across all workstreams.
Planned 3 to 4 months post-alpha
Sync with FHIR Gateway (location / CareTeam / Org scoped)
StructureMap-based extraction for complex form data
$Apply Lite for CarePlan and task generation from PlanDefinition
Workflow scheduling (due, overdue, expired task cues)
In-app reports
Remote config ingestion
Sync depends on the kotlin-fhir-engine beta release, expected July 2026. Once available, this unblocks the full sync and workflow capabilities.
Sync filtering (location / CareTeam / Org scoped data access)
Bulk upload APIs (users, locations, orgs via CSV/Excel)
Role-scoped admin endpoints (district-level permission boundaries)
Approval workflows
Adoptable UI widgets and configurable layout
Bulk CSV/Excel import (users, locations, orgs)
Role-based access and approval workflows
District-level admin scoping
Dashboard SSO
Programme-specific indicator packs
Synthetic data seeding tooling
Data seeding for bulk workforce and location imports
v1.2.0-GA
Horizon 3: Production Blueprints
Scaling for global production with cloud-native architecture, fully remote application orchestration, and advanced analytical capabilities for large-scale deployments.
Future 6+ months post-beta
The GA horizon is directional. Priorities will be refined based on community feedback from v1 alpha and v2 beta.
Fully remote app orchestration (no app store update required)
Full platform parity (Android, iOS, Desktop, Web)
Advanced workflows (CQL / FHIRPath execution)
Advanced CQL/FHIRPath workflow logic
Custom data science views and analytics notebooks
Cloud deployment templates (AWS and GCP)
High-volume ETL pipelines to SQL data warehouses
Custom ViewDefinition editor
Infrastructure-as-code for production on cloud platforms
See where we are today. Check the live workstream status and progress for v1.0.0-alpha.
Back to status