Extract the patient, procedure, provider, risks, benefits, alternatives, and the signature and date fields from a medical informed consent form PDF.
The full guide: Procedure, risks, and signatures on a consent form
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The document number and date, patient name, identifier, birth date, gender, address, and contact, the procedure description and its clinical indication, the provider name and title, the facility name, and the encounter the consent belongs to. It reads the fields present on the form; it does not assess whether the consent is valid.
Yes. The procedure risks table returns each risk with its description, severity, and frequency, the procedure benefits table returns each expected benefit with its likelihood, and the alternative procedures table returns each alternative with its description and a comparison of pros and cons.
The patient, witness, and provider signature booleans, the signature date, and the witness name come back as fields, and a consent signatures table returns each signer role, name, signature date, and whether a signature is present, so you can see at a glance which boxes are filled.
Whether capacity was assessed, an interpreter was used, and comprehension was confirmed each come back as booleans, alongside the consent status, the effective and expiration dates, and the revocation clause text. The field set follows the HL7 FHIR R4 Consent resource, and the tool reports these values as written rather than judging them.
The form is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Redact identifiers where possible; for BAA-covered work, ask about the Talonic platform. Uploads are PDF only, up to 10MB and 100 pages.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for clinical and billing teams, or the extraction API if you are building it in.