Patient Records Built to NHS Standards
Patient records structured the way the NHS expects — so the system can plug into NHS tools later.
Workflow moment
From manual step to owned workflow.
Before this step
Clinical software built on a sloppy records structure can't talk to NHS systems and won't pass review. Getting this right first is the hardest, most important call — fix it later and you rebuild everything.
Now it runs as a system
A records foundation that fits NHS systems and holds up under review — built once, correctly, before any screens. Everything else in FlapTrack is built on top of it.
System detail
How the system works
Patient records covering the whole flap-surgery journey, built to the standard the NHS uses. Safety checks live inside the records themselves, so bad data can't sneak in. Each hospital only sees its own patients — that separation is locked in by the structure, not left to app code to remember.
Proof
Proof it is real
- Schema tables
- 33
- Enum types
- 42
- Stored functions
- 16
- Triggers
- 33
- Per-hospital access rules
- 58
- Tables locked to each hospital
- 27
- 33-table records structure built to the NHS standard — ready to connect to NHS tools.
- Each hospital sees only its own patients, enforced 58 ways across 27 tables — not left to app code.
- Safety checks built into the records themselves, so bad data can't get in.
- Clinical logic lives next to the data, where it's hardest to break.