Express Scripts Form
What the Express Scripts Form Is and when it’s used
Why completing the form correctly matters
Accurate completion reduces processing delays, supports clinical review, and documents consent and clinical necessity. Properly formatted submissions help avoid denials, support audit readiness, and must align with e-signature laws such as ESIGN (15 U.S.C. §7001) and HIPAA privacy and security obligations.
Who typically completes or signs this form
Typical users include prescribers, pharmacy staff, and patients submitting benefit or prior authorization requests.
- Prescribers and clinical staff — complete diagnosis, clinical rationale, and prescriber signature or authorized delegate information.
- Pharmacy staff and technicians — submit transfer requests, confirm member details, and attach prescription data for processing.
- Patients and caregivers — provide member ID, consent, and signatures when patient authorization is required for benefits or releases.
Step-by-step: complete and submit the form
-
01Gather documents: Collect member ID, insurance card, and relevant clinical notes.
-
02Enter patient data: Complete full legal name, DOB, and member/group ID exactly.
-
03Provide clinical detail: Add ICD-10 diagnosis, medication name, dosage, and clinical justification.
-
04Sign and submit: Obtain required signature and send via the selected secure route.
Configure an online workflow for electronic completion
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS code, or higher-assurance KBA |
| Template Fields | Pre-fill patient and prescriber fields from EHR |
| Routing Order | Prescriber → Pharmacy → Payer/Clinical review |
| Notifications | Email and SMS alerts on status changes |
Where completed forms are sent and how routing works
-
Provider portal: Upload to provider portal for direct ingestion.
-
Secure upload: Use encrypted uploads if available to protect PHI.
-
Pharmacy fax: Fax to the pharmacy when portal upload is unavailable.
-
Payer submission: Route authorizations to payer clinical review teams.
Technical requirements for eSubmission and integrations
Electronic submissions require secure transport, accepted file formats, and signer authentication compatible with payer intake systems.
- File Formats: PDF, DOCX accepted
- Authentication: Email link or SMS code
- Integrations: EHR, Google Workspace, Microsoft 365
Typical timelines and processing expectations
Acknowledgement:
Receipt acknowledgements are often provided within one business day.
Triage and assignment:
Intake teams assign for clinical review based on request complexity.
Clinical review window:
Complex specialty requests may require additional documentation and time.
Decision communication:
Outcomes are communicated to provider and pharmacy once decision is made.
Appeals timing:
Appeal or resubmission timelines vary by payer and plan.
Key milestones from submission to resolution
Prepare form
Collect and verify member and clinical information before starting.
Submit to intake
Send via the chosen secure channel or portal.
Clinical review
Reviewer confirms medical necessity and coverage criteria.
Decision & notify
Outcome communicated to prescriber, pharmacy, and patient.
Common mistakes that delay processing
- Incomplete member identifiers such as missing member or group ID often prevent claims matching and require re-submission.
- Illegible handwriting or scanned images with low resolution cause transcription errors and slow adjudication.
- Missing clinical justification or vague diagnosis entries frequently trigger peer-review requests and extend review timelines.
- Unsigned or incorrectly signed forms are rejected by intake teams and returned for completion, delaying treatment access.
Risks and consequences of incorrect or incomplete forms
Comparison: common eSignature vendor pricing and capabilities
| 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 | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Real-world examples of electronic form use
Fertility Centers of Illinois
A clinic digitized patient consents and enrollment for specialty therapy to streamline intake.
- Result: faster turnaround and consistent records.
- John Butler said: "The airSlate SignNow team has been exceptional, responsive, the API has been great, and we're extremely happy that we chose airSlate SignNow as a company."
Optica Ventures LLC
A small company replaced paper approvals with signed digital forms to reduce processing steps.
- Result: fewer manual handoffs and clearer audit trails.
- Brian Fitzgibbons noted the interface is simple and easy-to-use for their team and customers.
Frequently asked questions and troubleshooting
-
Are electronic signatures valid for this form?
Yes. In the United States, electronic signatures are generally legally valid under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Ensure intent, consent, attribution, and reliable retention are documented to meet legal tests.
-
How should I protect patient health information?
Transmit PHI only over encrypted channels, limit access with role-based controls, and use a platform that supports a Business Associate Agreement. HIPAA requires administrative, physical, and technical safeguards to protect PHI.
-
What happens if I submitted incorrect data?
If errors are discovered, correct and re-submit promptly with a clear change history or amendment. Document the correction and maintain the original and corrected records for audit purposes.
-
When is notarization required for these forms?
Most routine benefit and prior authorization forms do not require notarization, but state or payer rules can differ. Verify jurisdictional and payer requirements before assuming notarization is unnecessary.
-
How do I verify the signer's identity?
Use available authentication levels—email verification, SMS code, or knowledge-based authentication for higher assurance—then capture the audit trail including IP, timestamp, and authentication method.
-
Why was my submission rejected?
Rejections commonly occur due to missing member identifiers, incorrect prescriber credentials, absent clinical justification, illegible attachments, or unsigned sections. Review rejection reasons, correct issues, and resubmit according to payer guidance.