About this work

Purpose
Record one clinical note against an admission episode. A single schema covers all eight note types a ward team produces — admission clerking, progress, consult, event, bedside procedure, handover, transfer, and discharge planning — across twelve components: note header, interval history, observations and NEWS2, examination, investigations reviewed, problem list, medications, risk assessments, impression, plan and jobs, escalation, and communication.
Two engines
The completeness engine grades the record Complete, Partial, or Incomplete against the components required for the note type chosen, and reports a percentage; an explicit negative such as "no medication changes" counts as documented. The acuity engine assigns a Stable, Watch, Escalate, or Critical band by taking the worst finding across NEWS2 and the deterioration markers. Safety flags fire independently of both. The acuity band is overridable by the author with a recorded reason; the completeness status is not, because it is a mechanical property of the record.
Specification
Spec-driven: the living domain spec defines the data model, both engines, and the flag rules. The same engine grades the form, the report, and the dashboard.
Documentation
Grounded in GMC Good Medical Practice record-keeping, the AoMRC record standards, RCP NEWS2 (2017), and NICE NG89 (VTE), NG51 (sepsis), CG103 (delirium), CG179 (pressure ulcers), and NG15 (antimicrobial stewardship). A documentation and escalation-prompting aid — not a diagnosis, not a deterioration prediction, and not a substitute for clinical judgement. A Complete grade means the record is well documented for handover, not that the clinical care itself was correct.