Public Projects are personal open-source projects by Joel Parker Henderson, built in the author’s own time. They are not products of, or endorsed by, any employer or health organization. Any use in a live clinical setting needs your own organization’s clinical safety assessment, such as under DCB0129 and DCB0160 in the UK.

Where these projects can help

Common needs and the projects that can help with each
NeedHow it helpsProjects
Patient identityValidate and format NHS Numbers consistently, including the check digit, in any Rust service.
Integration and messagingParse, validate, and transform HL7 v2 and FHIR messages; validate clinical XML documents with Schematron.
Clinical terminology and classificationWork with SNOMED CT releases and the WHO classifications in tested, open code.
Shared care recordsExplore openEHR building blocks and explain the International Patient Summary to colleagues and partners.
Business cases and benefitsUse open methods and calculations for public value, cost-benefit, social return on investment, and health economics.
Architecture governanceRecord and share technology decisions with architecture decision records, used by organizations worldwide.
SecuritySet up a clear route for researchers to report vulnerabilities, with example policies to adapt.
Accessible user interfacesBuild accessible interfaces with the Lily Design System, which includes themes for public-sector and health service design systems.
Delivery and ways of workingAdapt open guides for agile delivery, service management, engineering metrics, and teamwork.

Why open source fits public health services

Public-sector guidance in many countries asks digital teams to work in the open. For example, the UK Service Standard asks teams to make new source code open, and the Technology Code of Practice asks them to be open and use open source. Open, reusable building blocks help health organizations reduce duplicated effort, avoid supplier lock-in, and share what works with health systems in other regions and countries.

How to get involved

  1. Try one: pick a project from the table and read its documentation. Most Rust crates install with one line.
  2. Tell us what you need: open an issue on the project’s GitHub repository with a use case, a bug, or a question.
  3. Contribute: improvements to code, documentation, tests, and translations are all welcome, including translations into more languages.
  4. Share it: use the share button at the top of this page to send it to a colleague who might benefit.

Questions are welcome on GitHub or LinkedIn.