Prepare consent and capture signatures
Form subject, patient/customer selection, preview, and capture states.
Platform · Last verified:
Consent manages catalog-based preparation, preview, and signature/file capture. Preparation alone does not prove signature capture or a finished PDF.
Select the correct form
Choose an offered form from Consent → Records. Data-processing consent uses a customer subject; other documents use a patient. Anesthesia and operation consent are different forms.
Opening from an existing surgery can lock procedure/patient selection. Search existing documents before creating duplicates for the same event.
Available forms cover anesthesia, operation, treatment fees, treatment refusal, data processing, fitness to travel and euthanasia. Match the form to the actual procedure rather than selecting it for a similar name.
Prepare and preview
- Select the correct patient/customer and veterinarian.
- Complete offered procedure-note/document-language fields.
- Review subject, veterinarian, date, and text in preview.
- Review access/selection for any veterinarian-signature option.
- Open Consent document details after creation.
Interface and document language can differ for some forms. Review the server-authored preview; an independent text/template is not the same document.
Capture signature or signed files
Use an offered on-screen signature flow for the correct document/signer. For a wet-signature scan, select the correct supported files and wait for upload completion.
Check document state, signature channel, and available file/PDF separately. If capture exists but the PDF is not ready, inspect the current record and error guidance rather than blindly submitting another signature.
Bind to a procedure
When binding an existing document to surgery is available, choose the same patient and correct form/procedure. Read confirmation; selecting a candidate does not complete binding. Verify relationships in both records afterwards.
Cancel and verify
Review reason/effect when cancellation is permitted. Issued, captured, and cancelled states differ. A care-flow consent warning also differs from PDF readiness.
This guide describes the software workspace; it does not replace an authorized legal/clinical assessment of document sufficiency.
Form-specific conditions and two signatures
General Operation consent creation requires selecting the related non-cancelled surgery; its patient comes from that operation. If absent, use the offered surgery creation before returning. Data-processing consent uses a customer; other forms use their patient/procedure context.
The veterinarian-signature option uses that clinician's saved personal signature; complete signature settings if missing/invalid. A veterinarian signature is not owner consent. Owner screen signature or wet-signed scan is captured separately.
Fit-to-travel document language is independent of interface language. Read missing-fact warnings; unavailable verification is not confirmation. Created wording/procedure notes are frozen; editing a clinical note does not update an earlier signed document.
Complete and bind
Read issued document, captured owner signature, PDF readiness and cancellation separately. Preview wet-signed images/PDFs within detail; filename alone does not prove the document. On PDF errors, inspect the existing record before creating another signature.
Surgery without consent offers new/existing binding; issued/captured consent continues through its existing record. Confirmation compares consent and target surgery patient, name/date and frozen note. Loading more candidates or selecting a row does not bind it. Recheck stale-consent feedback in procedure detail.