About
Project background, working practices and how to contribute.
The project aims to produce a patient record whose behaviour is specified, tested and documented, including what has not been done.
Not for clinical use
Do not use this software to care for anyone, and do not enter real patient data. It has no clinical safety sign-off, no named Clinical Safety Officer, no clinical review and no regulatory approval of any kind. The project makes no claim to meet any regulation or standard.
How the work is done
- Spec first. A behavioural change is one commit with a spec edit, a code edit and a test edit.
- Stated limitations. Every changelog entry states what was not done or not verified.
- Clinical risk goes in the hazard log. Only a Clinical Safety Officer may accept or close a hazard.
- International design. National rules are held in packs, not in the core.
Much of the work is done with AI coding agents. The AI statement and the agent instructions are public.
How to contribute
The project has open needs for clinicians, a Clinical Safety Officer, and reviewers for its privacy and access work.
- Start with the open questions.
- Read how to contribute.
- Open an issue.
Licence
Available under any one of MIT, Apache-2.0, BSD-3-Clause, GPL-2.0-only or GPL-3.0-only, at your choice. See the licence.