A large commercial system
Suitable where a proven, supported system with a clinical record and an accountable supplier is required.
This page compares this project with three other types of system, based on typical characteristics. Pages for named products are listed below. Details should be confirmed with suppliers.
The main difference is maturity: the alternatives are in live use, and this project is not. It is not ready for use with real patients.
| This project | Large commercial system | Reminder-only service | Spreadsheets and phone calls | |
|---|---|---|---|---|
| In use with real patients | Not yet | Yes | Yes | Yes |
| Safety and security assurance | Not yet complete | Usually in place | Usually in place | Depends on local practice |
| Support contract | None yet | Yes | Yes | None |
| Software licence fee | None | Usually | Usually | None or low |
| Can read and change the code | Yes | Usually not | Usually not | Not applicable |
| Reminders that escalate to a person | Yes | Varies | Varies | By hand |
| Patient replies change the booking | Yes | Varies | Varies | By hand |
| Fairness measures built in | Yes | Varies | Rarely | By hand |
| Holds clinical records | No, by design | Often | No | No |
| Waiting lists and RTT clocks | Yes | Yes | No | By hand |
Each page lists the public sources used.
Suitable where a proven, supported system with a clinical record and an accountable supplier is required.
Adds reminders to existing systems at low effort. It does not usually change waiting list or staff task processes.
Workable for a small service. It scales poorly and makes access difficult to measure.
Relevant to organisations that want to review the code, influence its design, research access, or contribute. It is not suitable for live use.
person-service and worker-service alongside it.The tutorial covers local setup, and the safety and trust page lists outstanding work.