Where do PSP enrollments actually start?
At prescribing?
Where clinical decisions happen.
At intake?
Too late. Forms arrive incomplete.
In the Portal?
Workflow friction. Portal fatigue
Enrollment should start at the moment a prescriber decides to treat.
Not at intake. Not in the portal. At the source.
Scene 01 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
The Landscape
The Starting Point Matters
Most PSP enrollment methods are disconnected from the prescribing moment. FastPass™ by zPaper starts with it.
Rx Handling
PEF Handling
PEF Enrollment Methods
Closest to Prescribing Moment
FastPass
eRx issued at Submit — same event
PEF completed inside the eRx system
VS. The Six Alternatives
eRx to Intake Pharmacy
eRx sent to Intake Pharmacy
PEF primarily for consents / attestations
eRx Platform
PEF replaced by platform workflow
eRx issued inside the platform
Manufacturer Portal
PEF logic in manufacturer portal
Rx requested after enrollment
Hub / PSP Portal
PEF recreated in portal fields
Rx sent via separate channel
Split Fax
PEF sent to pharmacy, shared with Hub
Rx faxed to pharmacy
Traditional Fax
Rx written separately
PEF faxed
Furthest from Prescribing Moment
Scene 02 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
Why FastPass Wins
PSP Intake Teams Receive Complete Enrollment.
Day 1, not day 14. Here's what good looks like:
Valid ePrescription
Real eRx, signed in workflow, attached to enrollment.
Verified Prescriber
Identity and prescribing authority confirmed at the moment of signing.
No Missing Information
Required fields assigned through persona-based configuration.
Complete from Day 1
Every required field, attachment, and signature arrives together. Nothing to chase down.
All Required Attachments
Captured at the source, not requested later.
Structured Data
FHIR-ready data fields mapped to your system of record.
Real eRx using NCPDP Script protocol. Routed to intake pharmacy. Full audit trail from first click to final signature.
Scene 03 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
See how FastPass accelerates access to therapy.
A guided walkthrough of how ePrescribing and enrollment happen in one unified workflow
Your journey:
Configure
Initiate
Med Staff
Patient
Prescriber
PSP Intake
Scene 04 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
The Journey
Configure the Document Journey in DocJS
Configure once. Run anywhere.
Map enrollment form fields
eRx initiation area on form
Add program prescription choice(s)
Assign personas by fields and/or form sections
Generate the digital workflow link
Create workflow actions
Journey Editor
Click on an image thumbnail to expand the view
Scene 05 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Enrollment Initiation
One URL. A simple, frictionless starting point.
FastPass gives you a single branded URL for a digitized version of your approved PEF. Drop it on any site or portal, or share it as a link. No IT integration to get started. No form reconstruction. When the prescriber's office clicks the enrollment form, they land directly in the workflow.
Click on an image thumbnail to expand the view
Scene 06 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
One Form. Multiple Personas. One Workflow.
Med Staff
Patient
Prescriber
The Patient reviews, adds details, and provides eSignature for consent.
The Prescriber reviews the form and attaches a valid eRx.
The Med Staff completes patient and provider information.
Each persona sees only what they need. Field-level permissions are controlled without changing the legally approved template.
Scene 07 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Med Staff Workflow
Simplified form completion. Learn and fill capabilities. Easy next-step kickoff.
Insight
The form remembers prior information and stores it securely within your browser, removing the need to re-type previous information.
The med staff enters prescriber details once and clicks "Learn". That information is stored locally in the browser, not in the cloud. On the next enrollment, one click on "Fill" populates everything. Less typing. Less data exposure. Faster adoption.
The med staff enters what they know: patient name, date of birth, and contact information. Required fields are enforced by the system, so nothing gets missed.
Click on an image thumbnail above to expand the view
Scene 08 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Med Staff Workflow
One action. Three signers. Zero manual follow-up.
Med staff enters recipient details for the patient and prescriber. The NPI is verified in real time. Email and SMS notifications go out automatically, in sequence. The workflow runs itself. No manual chasing. No "did you get my fax?" calls.
Click on an image thumbnail above to expand the view
Scene 09 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Patient Workflow
Add additional information, sign eConsent. Starting with a familiar notification.
Patient Completed Signed Completed form with consent, attachments, and signature captured
They enter address and insurance details and upload an insurance card directly into the form. Required fields and attachments are enforced by the system, so nothing arrives incomplete.
The patient receives hyperlink to complete their portion of your PEF. Your consent requirements. No portal account. No login friction. Branded to your program.
Click on an image thumbnail above to expand the view
Scene 10 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Patient Workflow
Consents Authorized and Documented.
The patient reviews consent language and signs electronically. Date-stamped. Audit-tracked. Using the consent statements your legal team approved.
Insight
Consent, attachments, and eSignature all live inside one form experience.
Click on an image thumbnail above to expand the view
Scene 11 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Prescriber Workflow
The Prescription. Inside the Form.
The prescriber receives an email notification. They click through and land directly on the form. No separate portal. No new login.
After authentication, the prescriber sees everything the patient filled out but cannot edit those fields. Field-level permissions are controlled without changing the legally approved template.
The prescriber's identity and prescribing authority are verified before they can access the ePrescribing system of record.
Click on an image thumbnail above to expand the view
Scene 12 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Prescriber Workflow
The Prescription. Inside the Form.
Insight
The eRx is the real eRx. Not a simulation. Not a paper version. It runs on certified infrastructure, in the same workflow, in the same session. The prescription a hub receives is the prescription the pharmacy fills.
The prescription section now opens a certified ePrescribing experience directly within the form. The prescriber stays in workflow. The eRx runs in parallel, in the same session, on a familiar clinical workflow.
Patient info flows directly into the ePrescribing workflow. The prescriber searches the medication, sets quantity and instructions, and adds it to the draft. Medication history loads when the network returns it. Same clinical flow they'd use in any certified prescribing platform.
Electronic signature built to 21 CFR Part 11 standards. A digital seal helps prevent duplicate prescriptions, and a QR code opens the full audit trail. Who signed, what, when, and from which profile.
Click on an image thumbnail above to expand the view
Scene 13 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
After Submission
Patient
Prescriber
Everyone gets a confirmed copy.
Med Staff
At submit, a copy of the completed Patient Enrollment Form is delivered to every participant: patient, medical staff, prescriber, and the hub or designated intake pharmacy. No more uncertainty about what was sent or when. Every party has a verified record of what was submitted, when, and by whom.
Submitted Day 1. Acted on Day 1.
Click on an image thumbnail above to expand the view
Scene 14 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
After Submission
Behind every submission is a full audit trail.
A signed audit document captures every participant, every action, every timestamp. Signatures, prescription details, attachments, and IP addresses are all preserved. If a payer, auditor, or compliance team ever needs proof, it's already there. Who signed. What was signed. When. From which profile. From which IP.
Click on an image thumbnail above to expand the view
Scene 15 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
What Your Team Receives
Structured data, mapped to your system of record.
Beyond the documents, the form data flows directly into your system of record or is delivered as a structured data package. Patient name, date of birth, prescriber NPI, drug, quantity, signature status, timestamps. Every field is structured metadata, not text extracted from a scanned image.
Your team can automate, route, and act on the record the moment it arrives.
Click on an image thumbnail above to expand the view
Scene 16 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Outcome
Day 1.
Not Day 14.
When a complete enrollment arrives with every required field, attachment, eSignature, and a valid ePrescription, your intake team stops chasing and starts acting.
That's faster access to therapy for the patient. From the start.
All required information on Day 1
Eliminated missing-info loops
A valid eRx on Day 1
Faster time to therapy
Scene 17 of 18
The Outcome
The Journey
The Approach
Next Steps
The Problem
Talk to us
Dive Deeper
We'll show you what a complete Day 1 enrollment with existing forms looks like.
Schedule a Demo →
FastPass by zPaper
zpaper.com | sales@zpaper.com
Complete Enrollments. Smarter Documents. Valid eRx. Faster Access. At the Start
Scene 18 of 18
The Outcome
The Approach
The Journey
Next Steps
The Problem
DocJS-FastPass Journey Walkthrough
Corey Washington
Created on May 15, 2026
Start designing with a free template
Discover more than 1500 professional designs like these:
View
Practical Microsite
View
Essential Microsite
View
Akihabara Microsite
View
Essential CV
View
Akihabara Resume
View
Momentum: Manager Guide
View
Momentum: First Operational Steps
Explore all templates
Transcript
Where do PSP enrollments actually start?
At prescribing?
Where clinical decisions happen.
At intake?
Too late. Forms arrive incomplete.
In the Portal?
Workflow friction. Portal fatigue
Enrollment should start at the moment a prescriber decides to treat.
Not at intake. Not in the portal. At the source.
Scene 01 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
The Landscape
The Starting Point Matters
Most PSP enrollment methods are disconnected from the prescribing moment. FastPass™ by zPaper starts with it.
Rx Handling
PEF Handling
PEF Enrollment Methods
Closest to Prescribing Moment
FastPass
eRx issued at Submit — same event
PEF completed inside the eRx system
VS. The Six Alternatives
eRx to Intake Pharmacy
eRx sent to Intake Pharmacy
PEF primarily for consents / attestations
eRx Platform
PEF replaced by platform workflow
eRx issued inside the platform
Manufacturer Portal
PEF logic in manufacturer portal
Rx requested after enrollment
Hub / PSP Portal
PEF recreated in portal fields
Rx sent via separate channel
Split Fax
PEF sent to pharmacy, shared with Hub
Rx faxed to pharmacy
Traditional Fax
Rx written separately
PEF faxed
Furthest from Prescribing Moment
Scene 02 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
Why FastPass Wins
PSP Intake Teams Receive Complete Enrollment.
Day 1, not day 14. Here's what good looks like:
Valid ePrescription
Real eRx, signed in workflow, attached to enrollment.
Verified Prescriber
Identity and prescribing authority confirmed at the moment of signing.
No Missing Information
Required fields assigned through persona-based configuration.
Complete from Day 1
Every required field, attachment, and signature arrives together. Nothing to chase down.
All Required Attachments
Captured at the source, not requested later.
Structured Data
FHIR-ready data fields mapped to your system of record.
Real eRx using NCPDP Script protocol. Routed to intake pharmacy. Full audit trail from first click to final signature.
Scene 03 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
See how FastPass accelerates access to therapy.
A guided walkthrough of how ePrescribing and enrollment happen in one unified workflow
Your journey:
Configure
Initiate
Med Staff
Patient
Prescriber
PSP Intake
Scene 04 of 18
The Approach
The Journey
The Outcome
The Problem
Next Steps
The Journey
Configure the Document Journey in DocJS
Configure once. Run anywhere.
Map enrollment form fields
eRx initiation area on form
Add program prescription choice(s)
Assign personas by fields and/or form sections
Generate the digital workflow link
Create workflow actions
Journey Editor
Click on an image thumbnail to expand the view
Scene 05 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Enrollment Initiation
One URL. A simple, frictionless starting point.
FastPass gives you a single branded URL for a digitized version of your approved PEF. Drop it on any site or portal, or share it as a link. No IT integration to get started. No form reconstruction. When the prescriber's office clicks the enrollment form, they land directly in the workflow.
Click on an image thumbnail to expand the view
Scene 06 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
One Form. Multiple Personas. One Workflow.
Med Staff
Patient
Prescriber
The Patient reviews, adds details, and provides eSignature for consent.
The Prescriber reviews the form and attaches a valid eRx.
The Med Staff completes patient and provider information.
Each persona sees only what they need. Field-level permissions are controlled without changing the legally approved template.
Scene 07 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Med Staff Workflow
Simplified form completion. Learn and fill capabilities. Easy next-step kickoff.
Insight
The form remembers prior information and stores it securely within your browser, removing the need to re-type previous information.
The med staff enters prescriber details once and clicks "Learn". That information is stored locally in the browser, not in the cloud. On the next enrollment, one click on "Fill" populates everything. Less typing. Less data exposure. Faster adoption.
The med staff enters what they know: patient name, date of birth, and contact information. Required fields are enforced by the system, so nothing gets missed.
Click on an image thumbnail above to expand the view
Scene 08 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Med Staff Workflow
One action. Three signers. Zero manual follow-up.
Med staff enters recipient details for the patient and prescriber. The NPI is verified in real time. Email and SMS notifications go out automatically, in sequence. The workflow runs itself. No manual chasing. No "did you get my fax?" calls.
Click on an image thumbnail above to expand the view
Scene 09 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Patient Workflow
Add additional information, sign eConsent. Starting with a familiar notification.
Patient Completed Signed Completed form with consent, attachments, and signature captured
They enter address and insurance details and upload an insurance card directly into the form. Required fields and attachments are enforced by the system, so nothing arrives incomplete.
The patient receives hyperlink to complete their portion of your PEF. Your consent requirements. No portal account. No login friction. Branded to your program.
Click on an image thumbnail above to expand the view
Scene 10 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Patient Workflow
Consents Authorized and Documented.
The patient reviews consent language and signs electronically. Date-stamped. Audit-tracked. Using the consent statements your legal team approved.
Insight
Consent, attachments, and eSignature all live inside one form experience.
Click on an image thumbnail above to expand the view
Scene 11 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Prescriber Workflow
The Prescription. Inside the Form.
The prescriber receives an email notification. They click through and land directly on the form. No separate portal. No new login.
After authentication, the prescriber sees everything the patient filled out but cannot edit those fields. Field-level permissions are controlled without changing the legally approved template.
The prescriber's identity and prescribing authority are verified before they can access the ePrescribing system of record.
Click on an image thumbnail above to expand the view
Scene 12 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
Prescriber Workflow
The Prescription. Inside the Form.
Insight
The eRx is the real eRx. Not a simulation. Not a paper version. It runs on certified infrastructure, in the same workflow, in the same session. The prescription a hub receives is the prescription the pharmacy fills.
The prescription section now opens a certified ePrescribing experience directly within the form. The prescriber stays in workflow. The eRx runs in parallel, in the same session, on a familiar clinical workflow.
Patient info flows directly into the ePrescribing workflow. The prescriber searches the medication, sets quantity and instructions, and adds it to the draft. Medication history loads when the network returns it. Same clinical flow they'd use in any certified prescribing platform.
Electronic signature built to 21 CFR Part 11 standards. A digital seal helps prevent duplicate prescriptions, and a QR code opens the full audit trail. Who signed, what, when, and from which profile.
Click on an image thumbnail above to expand the view
Scene 13 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
After Submission
Patient
Prescriber
Everyone gets a confirmed copy.
Med Staff
At submit, a copy of the completed Patient Enrollment Form is delivered to every participant: patient, medical staff, prescriber, and the hub or designated intake pharmacy. No more uncertainty about what was sent or when. Every party has a verified record of what was submitted, when, and by whom.
Submitted Day 1. Acted on Day 1.
Click on an image thumbnail above to expand the view
Scene 14 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
After Submission
Behind every submission is a full audit trail.
A signed audit document captures every participant, every action, every timestamp. Signatures, prescription details, attachments, and IP addresses are all preserved. If a payer, auditor, or compliance team ever needs proof, it's already there. Who signed. What was signed. When. From which profile. From which IP.
Click on an image thumbnail above to expand the view
Scene 15 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Journey
What Your Team Receives
Structured data, mapped to your system of record.
Beyond the documents, the form data flows directly into your system of record or is delivered as a structured data package. Patient name, date of birth, prescriber NPI, drug, quantity, signature status, timestamps. Every field is structured metadata, not text extracted from a scanned image.
Your team can automate, route, and act on the record the moment it arrives.
Click on an image thumbnail above to expand the view
Scene 16 of 18
The Journey
The Outcome
The Approach
The Problem
Next Steps
The Outcome
Day 1.
Not Day 14.
When a complete enrollment arrives with every required field, attachment, eSignature, and a valid ePrescription, your intake team stops chasing and starts acting.
That's faster access to therapy for the patient. From the start.
All required information on Day 1
Eliminated missing-info loops
A valid eRx on Day 1
Faster time to therapy
Scene 17 of 18
The Outcome
The Journey
The Approach
Next Steps
The Problem
Talk to us
Dive Deeper
We'll show you what a complete Day 1 enrollment with existing forms looks like.
Schedule a Demo →
FastPass by zPaper
zpaper.com | sales@zpaper.com
Complete Enrollments. Smarter Documents. Valid eRx. Faster Access. At the Start
Scene 18 of 18
The Outcome
The Approach
The Journey
Next Steps
The Problem