On this page ⌄
Resources and contributing
Source repositories, community discussions, and contribution guidelines across the Open Health Stack ecosystem.
Repositories across the stack
Each Open Health Stack component is maintained in its own dedicated repository. The repositories own their build commands, test suites, API details, releases, and issue trackers.
FHIR Foundations repositories
The core libraries and client SDKs provide the multiplatform foundation for working with FHIR data.
| Repository | Role |
|---|---|
| kotlin-fhir | Kotlin Multiplatform FHIR data model and serialization |
| kotlin-fhirpath | FHIRPath expression engine for Kotlin |
| kotlin-fhir-engine | On-device persistence, search, and server synchronization |
| kotlin-fhir-data-capture | Questionnaire rendering and data capture |
OHS Player reference toolkit
The reference implementation demonstrates how to assemble the building blocks into working digital health applications.
| Repository | Role |
|---|---|
| ohs-player | The toolkit definition and entry point |
| player-reference | Frontline health worker multiplatform client app |
| ohs-player-reference-web-portal | Administration portal for workforce and configuration |
| ohs-player-reference-backend | Gateway endpoints and access checkers |
| ohs-player-reference-infrastructure | Shared environment deployment scripts |
| player-client | Configurable multiplatform UI library |
| player-reference-ig | Declarative UI configuration implementation guide |
Documentation and templates
| Repository | Role |
|---|---|
| ohs-docs | Documentation site source, guides, and templates |
Getting help and community
The Open Health Stack community collaborates across public channels and issue trackers.
- OHS Foundation discussions for architecture discussions, questions about the ecosystem, and community support
- The issue tracker of the owning repository for bugs or feature requests specific to that component
Opening an issue directly in the owning repository connects you with the maintainers of that component and keeps the resolution close to the code.
Contributing code
Code contributions follow the workflow of the repository that owns the material.
- Review the contribution guidelines in the target repository before starting work.
- Open an issue or join a discussion thread to discuss proposed changes with the maintainers.
- Submit changes via pull request with tests verifying the new behavior.
Contributing documentation
Clear documentation is essential for developers evaluating and implementing Open Health Stack.
Documentation for individual components lives alongside the code in the respective repository, while cross-stack guides and foundational materials are published here.
The submission pack contains templates for each kind of document.
- Component overviews explaining capabilities and architecture
- Setup guides walking through local execution
- Core concepts explaining system design
- Technical references documenting APIs and parameters
- Configuration recipes showing practical patterns
The wider ecosystem
Open Health Stack components exist independently of any single reference application.
The OHS Foundation projects page is the official catalogue for all projects and the source for their maturity ratings. See The architecture for an explanation of how the reference stack connects them.