The Field That Tells You Everything Before the Patient Does
The SPO2 Reading on toggle — Air versus O2 — is the kind of field that gets built by someone who has been burned. Record a 96% saturation without noting the patient is on 15 litres via non-rebreather, and that number is functionally meaningless. Worse, it creates a false sense of reassurance in whoever picks up the PRF next. That radio button exists because of jobs where the handover narrative fell apart at the hospital door.
The same logic runs through the BP position field: Sitting, Lying, Standing. Orthostatic hypotension doesn't show itself in a single reading. It shows in the delta. If your first obs set was taken lying, your second was taken sitting after the crew rolled the patient for loading, and you never captured that distinction, you've lost the clinical story. The position field is not bureaucratic housekeeping. It's the context that makes the numbers mean something.
These are the fields that separate a documentation system built by someone who works the job from one built by someone who has only read about it.
The Obs Set as a Living Document During Patient Contact
The architecture here links each observation set directly to a PRF via an entries relationship. That linkage is the operational core of the system. One PRF per patient. Multiple obs sets per PRF, each timestamped. When your GCS at scene is 14 and your GCS at handover is 11, that trend is visible in the linked record chain — not buried in free text notes that depend on whoever happened to be holding the tablet.
Serial AVPU recording deserves attention here. AVPU is faster than GCS for rapid reassessment — less cognitive load when you are managing a deteriorating airway and trying to maintain a mental picture simultaneously. Logging AVPU at each obs interval and reserving full GCS scoring (Eyes, Verbal, Motor) for initial assessment and any step-change allows the attending medic to triage documentation effort without losing clinical fidelity. A patient who drops from Alert to Responds-to-Voice between the first and third obs set has told you something urgent, and the timestamp on those entries tells you how fast.
The BM field sitting alongside the neurological assessment is not accidental. Hypoglycaemia presenting as altered consciousness is one of the most reliably misread presentations in pre-hospital work. Having BM in the same obs record as GCS and AVPU means you are not reconstructing the clinical picture from two separate entries when you write up post-job. The data was captured together because the clinical assessment happened together.
What the Audit Trail Shows After Thirty Jobs
After a month of consistent use — assuming the PRF link discipline holds — you have a queryable dataset across every job the crew attended. Resolution field in the PRF library (Treated on scene, Treated at med post, Hospital — ambulance, Hospital — self conveyance) combined with job type (Minor/Major Injury/Medical) gives you a triage accuracy picture that most event medical operations never bother to generate.
Thirty jobs in, the patterns emerge: which job types most frequently escalate to ambulance conveyance, what the presenting GCS distribution looks like for major medical calls versus minor medical calls, how often the most qualified medic consulted is actually on scene versus contacted remotely. None of that analysis requires extra work at the point of capture. It requires only that the fields were filled consistently.
The PRF number integer field is worth maintaining sequentially across events. Cross-referenced with the SCAS job log entry link, it gives you an external audit trail that can be reconciled against service records. That reconciliation matters when a patient complaint surfaces six months later and your only defence is the contemporaneous record.