Built for the back of a moving ambulance.
SnapMedic ePCR
SnapMedic ePCR is the patient-record module inside Enterprise for medical providers, responder organisations and event first-aid teams. Record care offline, bring the clinical account together and hand over a reviewed record to the receiving team.
A patient record, not a clinical decision-maker.
ePCR captures the clinician’s account of care. It has no medicine-dose calculator or dosing decision support. Clinical decisions remain with the clinician, current guidance and local policy.
First touch to
hospital doors.
Bring clinical observations, interventions and review into one record for your crew and receiving team.
Discuss your serviceStart with the incident and patient
Create a record offline or join by an exact incident/CAD reference or record ID. One incident can hold separate records for several patients, each reviewed and locked independently.
Capture observations and care
Record observations, interventions, cardiac arrest events and crew notes. Adult NEWS2 supports review of the observation set; incomplete and paediatric sets show raw values and missing parameters, with pregnancy limitations made explicit.
Record medicines and signatures
Use your organisation’s formulary to record the quantity, unit and route administered. Record separate administration, witness and disposal signatures where required. There is no dose calculator in ePCR.
Review, lock and keep the history
See missing required fields before signing off. Record a reason if you must finish with gaps. After locking, signed updates keep the original account and show what changed and when.
Incident info — the CAD or local job reference and the incident address. Patient information — identity, date of birth and address, or a documented unknown-person reason. History — allergy status, past medical history, last oral intake and the events leading to the call. Dispositions — a running log, where the last entry recorded is the record’s ultimate disposition.
The detail behind
the care.
Explore what your team can record, how the receiving team accesses it, and the controls around each patient record.
Patient & incident
Keep the patient’s identity and the incident context together.
- Patient identity
- Record known identity or an explicit reason for an unknown-person entry.
- Demographics and contacts
- Capture contact details, next of kin with consent to contact, and GP practice.
- Incident reference
- Create or join by an exact incident/CAD reference or record ID, with each lookup audited.
- Multiple patients
- One incident can hold separate patient records, each reviewed and locked independently.
- NHS number
- Validated number entry with encrypted storage and a masked display. No NHS demographic-service lookup.
Two crew.
One record.
A second clinician does not start a second form. They join the same record by its exact reference, add what they saw, and the record keeps track of who wrote what. One clinician locks it at handover.
Step 1
One crew member starts the record
The first responder creates the record on scene and records the presenting complaint. Changes queue on the device, so nothing depends on having signal at the roadside.
Device A records the presenting complaint. Changes sit queued until someone syncs. Step 2
The second device joins by exact reference
A colleague looks up the exact incident reference or record ID. The lookup reveals the incident context only — patient and clinical detail stay hidden until they confirm the join, and every lookup is audited.
Exact lookup, never a browsable list or free-text patient search. Step 3
Every field says who wrote it
Where colleagues write the same field, the record keeps every superseded value, its author and its time. An “Edited by” badge explains a value that changed under you, rather than leaving it a mystery.
Attribution on the field itself, not buried in a separate audit screen. Step 4
One clinician locks it at handover
Locking is a deliberate act by a clinician, and it is never hard-blocked by missing fields: they see exactly what is missing and record a written reason to finish with gaps. Other devices see the lock once they sync.
The second device picks up the lock on its next sync.
Share access
to the record.
A structured ATMIST handover accompanies the record, with crew and receiving signatures captured at the patient’s side. How completed records reach your receiving teams and your reporting is agreed and configured during your rollout.
- Capture the handover.
Record the ATMIST summary, the receiving destination and crew and receiving signatures on the record itself.
- Keep the record reviewable.
A locked record stays available to your organisation, attributed and read-only, for review and audit. Patient reports and organisation exports are configured with your service during rollout.
One app. Your service
decides what is inside.
Configure recording tools for your service. Set up roles, scope of practice and recording requirements around the way your teams work.
Your service.
Your ePCR quote.
Competitive pricing for Enterprise and ePCR, tailored to your team and recording requirements. Tell us about your service and we’ll agree the software, hosting and support scope in a written quote.
Set up for
your service.
- Agree your recording requirements, organisation access and rollout with us. ePCR billing starts at the agreed live-service date, with terms confirmed in writing.
- Record your CAD or job reference. Live dispatch integration and NHS national lookups are not included.
- Use email codes and an authenticator for identifiable recording. Organisation single sign-on is not included.
Common questions.
How do we get started with SnapMedic ePCR?
ePCR is an add-on inside SnapMedic Enterprise, enabled for your organisation and licensed for its recording clinicians. Tell us your member numbers, recording requirements and current workflow so we can agree setup and pricing. It is not part of the personal SnapMedic app.
How does handover to hospital work?
Handover detail travels on the record itself: a structured ATMIST summary, plus crew and receiving signatures captured at the patient’s side. How completed records reach your receiving teams is agreed and configured during your rollout.
Does it work without signal?
Record details offline and synchronise when connectivity returns. Shared editing and crew presence depend on connectivity.
How is pricing handled?
ePCR is an add-on inside SnapMedic Enterprise. We offer competitive pricing tailored to your organisation’s recording clinicians, hosting and support requirements. Enquire for a written quote; billing begins at the agreed live-service start.
Will it integrate with our CAD or NHS systems?
Version one is CAD-agnostic: a CAD number or job reference is recorded as an external reference, with no live dispatch integration. NHS pathways such as CIS2 and national extracts are deliberately out of scope for version one.
Who owns the patient data?
Patient records belong to your organisation. Enterprise clinical data is stored server-side and is readable by the service for authorised synchronisation, audit and support. Organisation isolation, named permissions, encryption and audit logging govern access. Hosting and retention arrangements are agreed with your service. This is separate from the personal app’s intervention log, which is a temporary notepad and must not contain patient information.
Does ePCR calculate medicine doses or make clinical decisions?
No. ePCR records the care and decisions of the clinician. Medicine administration is recorded against your organisation’s formulary; the module has no dose calculator or dosing decision support. Capacity, consent and other clinical fields record your findings, rather than determining authority to treat or a clinical risk category.
Can we change our forms and formulary?
Your organisation can have versioned forms and formularies, with required, optional and conditional fields appropriate to its recording roles. Form publication is a supported configuration process, not a drag-and-drop form builder in Console. Clinical leads can also agree receiving-destination overrides.
What happens after a record is locked?
The original record stays as it was. Clinicians with the right permission can add signed updates afterwards, keeping the original and showing who added what. A record can be locked with missing required fields only after the clinician sees the gaps and records a written reason.