Request Header
Identify the requesting organization, date of request, and intended recipient. Include contact details and a clear purpose for the record request to avoid ambiguity during fulfillment.
A well-formed request reduces processing delays, ensures legally valid authorization for PHI exchange, and documents patient consent. Proper format and signatures support auditability under ESIGN and UETA and help meet HIPAA requirements for disclosure and recordkeeping.
Common users include healthcare staff, school administrators, public health officials, and patients or guardians who must authorize release.
Each user follows specific role-based steps for completing, signing, and storing the request to meet legal and operational requirements.
Identify the requesting organization, date of request, and intended recipient. Include contact details and a clear purpose for the record request to avoid ambiguity during fulfillment.
Collect full legal name, date of birth, medical record number, and address so records can be matched accurately and mismatches are minimized during retrieval.
Specify vaccine names, lot numbers if known, and date ranges. Use clear phrasing like 'All immunizations from birth to present' or list specific vaccines and dates.
Include explicit release language that names the party authorized to receive records, any limits on disclosure, and a statement about revocation rights consistent with HIPAA rules.
Provide signer name, relationship if signing for a minor or legal representative, signature, date, and a parent/guardian checkbox when applicable.
Space for the releasing provider to note how records were verified, the source system, date of release, and an attesting signature or initials for audit trails.
| Field | Configuration |
|---|---|
| Authentication Method | Email link | SMS or ID verification |
| Conditional Fields | Show parental consent for minors |
| Routing Rules | Route to records clerk then clinician |
| Retention Setting | Archive signed PDF per policy |
Use secure eSignature workflows that capture intent, attribution, and a reliable audit trail compatible with ESIGN and UETA.
Ensure the chosen platform supports HIPAA (BAA available), audit logs, and secure exports so signed requests can be stored alongside clinical records and produced for audits.
Often within 7–14 business days
Proof required before first attendance
Timelines vary by state and disease
Process within 24–72 hours if urgent
Allow 30 days for verification and corrections
| Criteria | Immunization Request | Vaccination Consent |
|---|---|---|
| Primary Purpose | obtain records | authorize vaccination |
| Who Signs | patient/guardian | patient/guardian |
| PHI Disclosure | yes, release to recipient | limited clinical use |
| Use Case | record transfer | clinical treatment authorization |
| 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 free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |