On this page ⌄
Current capabilities and maturity
Current runnable features across reference components and development roadmap areas.
Overview
OHS Player is an open source reference toolkit under active development. This page provides a transparent inventory of current software capabilities and active engineering roadmap areas.
Current runnable capabilities
| Component area | Current capabilities |
|---|---|
| Reference Infrastructure | Turnkey Docker Compose topology spinning up PostgreSQL, Keycloak, HAPI FHIR, and Info Gateway with health checks |
| Reference Backend | Custom gateway endpoints for users, groups, roles, location hierarchies, practitioner details, and bulk CSV ingestion |
| Web Admin Portal | OpenID Connect sign-in, user and role management, facility hierarchy configuration, and FHIR resource browsing |
| Client Application | Cross-platform builds on Android, iOS, desktop, and web rendering screens dynamically from FHIR configurations |
| Sync and Offline Persistence | On-device SQLite storage through the multiplatform FHIR engine, with sign-in over OAuth 2.0 with PKCE and FHIR sync through the Info Gateway |
| Form Data Capture | Rendering Structured Data Capture (SDC) questionnaires with real-time FHIRPath evaluation and template-based extraction |
| Streaming Analytics | Continuous extraction of transactional FHIR records into PostgreSQL via SQL-on-FHIR pipelines with Superset dashboards |
Active development areas
- Complex clinical workflow including automated
$applyoperations for PlanDefinitions and CarePlan generation is transitioning from the original Android FHIR SDK into the multiplatform libraries. - StructureMap extraction for advanced FHIR mapping alongside existing template-based extraction.
- Scoped synchronisation filtering what a device receives by location, care team, and organisation, enforced by the gateway access checkers, alongside benchmarking and performance work on sync itself.
- Enhanced portal management for visual questionnaire validation and direct audit event inspection.
Evaluation criteria
- Strong fit for teams building new FHIR-native health software, requiring offline-first frontline tools across mobile and desktop, or seeking to eliminate proprietary vendor lock-in.
- Implementation considerations include planning for production infrastructure provisioning, organizational access policies, and clinical content authoring tailored to local health guidelines.
Where to go next
- Get started launches the local reference environment with Docker Compose.
- What to know first provides technical background on FHIR specifications and tools.