← Back to Work
Process file · Healthcare
Healthcare
What’s inside: connections to your systems · audit trail
Why is the consent form missing when it matters?
The question this file answersWhere is the consent form from last Tuesday, and who is going to find it before the procedure?
Fits: clinics and hospital groups seeing 50–300+ patients a day.
Typical day
What the desk looks like today
Typical, from the healthcare playbook (intake): each of the 50–300+ patients a day signs at least one form, and filing consent is part of that flow. Paper is signed, scanned later and retyped from what is legible; the form is missing the day a clinician or auditor needs it.
What changes
What Monday looks like after
At the pre-op check, the consent is already on the record, indexed to the right episode, and the forms with a missing signature are on the desk's list from yesterday. Reception still explains and witnesses; the scanning pile is what goes.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
How this file is built
Consent-form handling is not benchmarked anywhere we can cite. The McKinsey (2023) intake figure quoted on the registration file describes registration as a whole and is not applied to consent. Not a legal-compliance claim.
What we install
What we put in front of the systems you already run
Nothing replaces the EHR — Epic, Cerner, Allscripts or the one you run. One step of the registration build is lifted out and run on its own:
- the signed form — paper scan, tablet or portal PDF — is captured and read
- the required fields are checked — signature, date, procedure, witness where your policy asks for one
- a complete form is attached to the right patient and episode in the EHR through HL7/FHIR or the document import, while an incomplete or unclear one goes to reception with the missing item named — and back to a conversation.
What stays human — and what this will not do
The explanation. Assessing capacity. Hearing a no. Anything that is not a tick.
Not a legal-compliance claim.
What can go wrong — and what we do about it
A form filed to the wrong patient is worse than a form in a pile — matching uses at least two identifiers, and anything ambiguous is held for a person. Capacity, understanding and refusal are never read from a tick box; the build checks completeness, not validity, and this is not a legal-compliance claim. The McKinsey intake range belongs to registration admin as a whole and lives on the parent file.
What it costs to get there
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
This is about you if…
- Are consent forms still signed on paper and scanned into a folder later?
- Does your EHR accept documents by interface or import, not only by manual attachment?
What does this mean in euros?
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Healthcare.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.
All process files