Patient Identification
Full legal name, date of birth, medical record number, and contact details to ensure the consent is attributable to the correct individual and to avoid mismatches in EHRs.
A correctly completed ITNA form documents informed consent, reduces clinical and legal ambiguity, supports billing and audit readiness, and preserves the patient’s rights; it also demonstrates compliance with HIPAA privacy and ESIGN/UETA e-signature rules when executed electronically.
The ITNA form is completed and used by several distinct roles in clinical settings.
Each role has distinct responsibilities: clinicians for content, administrators for storage and audit, and patients for authorization and signatures.
Primary signer when competent. The patient must provide consent, date the form, and confirm understanding of risks and alternatives in plain language; an unsigned or incomplete patient block can invalidate consent.
When a patient lacks capacity, a legally authorized representative may sign. Document authority (power of attorney, guardian order) and relationship, and include supporting ID to validate representative status.
Full legal name, date of birth, medical record number, and contact details to ensure the consent is attributable to the correct individual and to avoid mismatches in EHRs.
Clear description of the proposed treatment or procedure, expected benefits, common risks, and reasonable alternatives, enabling informed decision-making by the patient.
Concise enumeration of material risks and viable alternatives, including the option to refuse treatment and any consequences of refusal.
Specify whether consent is for a single procedure, a course of treatment, or ongoing care, and note any expiration or review intervals for continued consent.
Instructions for situations where immediate action is required, including authority for emergent interventions if the patient becomes incapacitated.
Designated signature blocks with date/time, printed names, witness lines if required, and an audit trail for electronic signatures to support legal and regulatory review.
| Field | Configuration |
|---|---|
| Patient ID field | Required, auto-validated against EHR |
| Conditional fields | Show alternatives only when selected treatment requires them |
| Authentication | Use email+SMS or stronger KBA for high-risk consent |
| Retention policy | Auto-retain per HIPAA and facility rules |
Electronic handling requires secure platforms that support HIPAA protections, audit trails, and file compatibility with EHRs.
Confirm the vendor supports a HIPAA BAA if PHI is processed, that documents preserve audit metadata (timestamps, IP), and that the platform can export signed PDFs compatible with your EHR.
Obtain immediately; document time and rationale in chart
Complete before procedure scheduling and prior to authorizations
Submit authorizations within payer-specific preauthorization windows
Attach signed form to EHR within 24–72 hours
Provide copies on request per facility SLA, usually within 5–10 business days
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Yes | Yes | Yes | Yes |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |