Bcbs Formulary Exception Form

Use a Bcbs Formulary Exception Form template to make your document workflow more streamlined.

What the formulary exception form does

The Bcbs Formulary Exception Form is a healthcare request used to ask a health plan to cover a prescribed medication that falls outside its formulary. The request typically records the patient’s identifying information, insurance details, requested drug, diagnosis, prior treatment or clinical rationale, prescriber information, and signature. With signNow, a healthcare organization can upload the form, auto-detect fillable fields, add missing fields, route it to the authorized prescriber, and retain the completed request with an audit trail. Payer-specific instructions still control submission, supporting evidence, and approval decisions.

Healthcare providers

Healthcare providers use the Bcbs Formulary Exception Form to document why a prescribed medication requires coverage outside the plan formulary, attach clinical support, and obtain the authorized prescriber’s signature before payer submission.

Pharmacy teams

Pharmacy and benefits teams review completed exception requests, verify medication and coverage details, and retain the signed form with supporting records according to organizational policy and applicable HIPAA obligations.

Complete the formulary exception request

Prepare the patient, prescriber, medication, diagnosis, and coverage details before sending the exception request for signature and payer review.

Upload documents:
Upload the current form and supporting clinical documentation.
Complete fields:
Review detected fields and complete patient and prescriber information.
Set signers:
Assign the appropriate signer and delivery order.
Send request:
Send the request and monitor completion status.
Store records:
Download the signed form and retain its audit trail.

Field placement

Upload the Bcbs Formulary Exception Form and place fields for patient, prescriber, medication, diagnosis, and signature information without rebuilding the request manually.

Signer routing

Route the exception request to a prescriber or authorized healthcare professional, reducing delays caused by missing signature assignments or unclear delivery order.

Mobile signing

Collect signatures from desktop or mobile devices when clinical and administrative teams work across separate locations or schedules.

Supporting records

Attach supporting clinical documentation to the same signing workflow, helping reviewers associate evidence with the specific medication exception request.

Audit evidence

Preserve timestamps, signer activity, and document history in an audit trail that authorized staff can review alongside the completed request.

HIPAA workflow

Use HIPAA-compliant signNow workflows with a business associate agreement when the form contains protected health information.

Mobile options for formulary requests

Use the signNow iOS or Android app to complete Bcbs Formulary Exception Form fields, capture supporting pages, and continue signing when connectivity is limited.

Mobile apps iOS 16 and Android 11 supported
Offline signing Sign offline in signNow mobile
Camera capture Capture paper pages with camera

For healthcare staff handling patient information, use managed iPhone or Android devices, restrict local copies, and confirm the health plan’s submission process after signing. Mobile capture can digitize supporting documents, while the completed request remains subject to organizational HIPAA policies and applicable payer requirements.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Security for formulary exception records

Data in transit:

TLS 1.2/1.3 encryption

Stored data:

AES-256 encryption at rest

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified controls

Health information:

HIPAA compliant with BAA

Electronic signatures:

ESIGN and UETA compliant

Authenticate signer:

Records the signer’s email, authentication event, and access details.

Timestamp actions:

Captures the exact time for each form action.

Hash document:

Associates the completed file with document integrity data.

Seal record:

Seals completed content against undetected changes.

Track events:

Logs signatures, field edits, and delivery events.

Export trail:

Allows authorized users to retrieve or export evidence.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Electronic signature with signer intent
Audit trail	Enable completion history and export
Document retention	Six years when HIPAA records apply
Encryption	TLS 1.2/1.3 and AES-256 encryption

Connect formulary exception workflows

Connect the Bcbs Formulary Exception Form workflow with healthcare operations, document storage, and enterprise systems that manage patient and authorization records.

Privacy challenges in exception workflows

Patient names, member IDs, medication details, and diagnoses can expose protected health information when sent to an incorrect recipient or downloaded to an unmanaged device.
A missing prescriber signature or incomplete clinical rationale can cause the payer to return the Bcbs Formulary Exception Form for correction.
Unrestricted workspace permissions can allow staff without a treatment or authorization role to view the completed exception request and supporting records.
Attaching unrelated clinical documents can disclose additional patient information beyond what the payer needs to evaluate the requested medication exception.

Best practices for exception requests

Accurate clinical details, limited disclosure, authorized signatures, and controlled retention help keep the Bcbs Formulary Exception Form usable for payer review.

Verify every patient and medication field

Before sending, compare the patient name, member ID, medication name, dosage, diagnosis, and prescriber details against the clinical and insurance records. Correcting mismatches before signature prevents the payer from treating the request as incomplete or returning it for clarification.

Attach only relevant clinical support

Attach the clinical notes, prior-authorization history, or treatment rationale requested by the plan, and keep each attachment associated with the same signed exception request. Do not include unrelated patient information that increases disclosure risk.

Route approval to the authorized prescriber

Use a signer role that matches the prescriber or authorized healthcare professional responsible for the exception request. Capture signer identity and consent through the configured signNow workflow rather than relying on an email footer or an unsigned approval message.

Archive the signed record securely

Export the completed form and audit trail, then store them in the organization’s controlled record system. HIPAA-covered records generally require six years from creation or the last effective date under 45 CFR 164.530(j).

Legal standing of electronic signatures

A completed Bcbs Formulary Exception Form may provide electronic evidence when the signer demonstrates intent, consents to electronic records, can be identified, and the record remains reproducible. ESIGN, 15 U.S.C. ch. 96, and applicable state law support electronic transactions, but wills, court orders, and certain family-law documents are excluded.

Why teams look for DocuSign alternatives

Prepare documents

Upload the current form, confirm payer instructions, and attach required clinical support.

Deliver to signer

Send the completed request to the assigned prescriber or authorized healthcare professional.

Signer review

The signer reviews patient, medication, diagnosis, and coverage details before applying intent.

Complete and archive

Download the signed form and audit trail, then archive them under policy.

Troubleshoot formulary exception signing

Resolve field, signer, payer-submission, PHI, plan, and retention questions before treating the Bcbs Formulary Exception Form as complete.

Upload the current Bcbs Formulary Exception Form as a PDF, then use signNow’s field detection and review every detected field manually. Add missing patient, prescriber, medication, diagnosis, date, and signature fields before sending.

Use signNow’s routing controls to assign the request to the prescriber or authorized healthcare professional. A recipient can often sign without a signNow account, but the sender must configure the correct role and signing order.

A signature workflow does not decide whether Blue Cross Blue Shield or another plan approves coverage. Confirm the payer’s submission channel, required clinical documentation, and authorization rules after the signed form is completed.

For protected health information, use signNow’s HIPAA-compliant configuration and execute a business associate agreement where required. Apply organizational access controls and avoid sending the completed form to unauthorized recipients.

The Business plan is listed at $8 per user per month with annual billing and includes audit trails and templates. Business Premium adds bulk send, while Enterprise adds advanced signer authentication.

Download the completed form and its audit trail from the authorized signNow workspace, then store both in the organization’s controlled record system. HIPAA-covered records generally require six years under 45 CFR 164.530(j).

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.