Clinic staff
Sees only their own prior auths.
- Pages
- Home, My prior auths, Information requests, Letters, Submission guide
- Can start
- New prior auth, Upload information
My prior auths
Prior authorization portal for clinics & payers
A prior authorization portal is where clinics submit requests with their supporting documents, the payer approves or denies each one with a reason, and clinic staff see where every request stands without calling.
Pattern: RequestsDescribe it to Pory
“We're a health plan and want clinics to submit prior authorization requests with supporting documents, our reviewers to approve or deny them, and clinics to see the status.”
Viewing as
In plain English
How Pory sets it up
Pory gives every clinic staff and payer reviewer a sign-in of their own. Each clinic staff sees only their own prior auths. It covers submit → payer review → approve/deny. Prior auths, information requests, letters and review team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Clinic staff file a prior authorization with the evidence attached
Prior auths go out by fax with a cover sheet, and half come back asking for a note that was on page four. Clinic staff enter the service, the patient and the code, and upload the clinical notes and imaging reports in the same form. The payer gets one complete request instead of a fax and two follow-up calls.
Forms to submit a recordDone by: Clinic staff
Payer reviewers approve or deny with the missing criteria spelled out
A denial usually arrives as a letter quoting a policy number, and the clinic spends an afternoon figuring out what was missing. The reviewer opens the request, reads the attached notes, and approves or denies it with a note saying exactly why, or asks for more information. The clinic can fix a denial the same day instead of starting over.
Approve / reject with a reasonDone by: Payer reviewer
Clinics see where each prior auth stands without calling the payer
Tracking prior auths means a spreadsheet of reference numbers and a daily round of hold music. Clinic staff see each request they've filed move from Submitted to In review to Approved, or stop at More info needed with the reviewer's note. Patients get a straight answer about their MRI date, and nobody has to call to get it.
Status tracker for the submitterDone by: Clinic staff
Who sees what in a prior authorization requests portal
Every person signs in to their own view. This is what each role in the demo gets.
Payer reviewer
Sees every prior auth in the portal.
- Pages
- Home, Prior auths, Information requests, Decisions due, Letters, Submission guide
- Can start
- Ask a clinic for information, Send a letter
- Decides
- Marks prior auths Approved or Denied, with a reason
What’s in the prior authorization requests portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Prior auths
- Service requested (text)
- Patient (text)
- CPT / HCPCS code (text)
- Supporting documents (file)
- Urgency (choice: Standard, Expedited)
- Practice (text)
- Submitted by (link)
- Submitted (date)
- Decision due (date)
- Status (choice: Submitted, In review, More info needed, Approved, Denied)
- Auth number (text)
- Approved until (date)
- Reviewer's note (long text)
Information requests
- What we need (text)
- Prior auth (link)
- Needed by (date)
- File (file)
- Clinic contact (link)
- Status (choice: Requested, Uploaded, Checked)
Letters
- Letter (text)
- Prior auth (link)
- Sent (date)
- Kind (choice: Approval letter, Denial letter, Request for information)
- File (file)
- Clinic contact (link)
Review team
- Name (text)
- Role (text)
- Direct line (text)
The parts behind this portal
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Collect
1 partForms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decide
2 partsApprove / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Control
3 partsWho sees which records
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A clinic staff signs in with a link sent to their email and lands on Home. They see Home, My prior auths, Information requests, Letters and Submission guide, and only the prior auths that are theirs. From there they can use “New prior auth” and “Upload information”.
Payer reviewer decide: they mark each one Approved or Denied and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.
You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.
More health portals
All health portalsPatient intake portalForms, insurance, historyTherapy & counseling portalSessions, notes, homeworkPhysical therapy portalExercise plans & progress logsDental treatment plans portalProposed → accepted → doneVeterinary clinic portalPet records & visit historyNutrition & health coaching portalMeal logs & check-insHome-care agency portalCaregiver visits & care plansReferral management portalRefer → accept → seen → report back
Build your prior authorization requests portal with Pory
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited clinics.