My prior auths
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.”
My prior auths
In plain English
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. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (clinic staff and payer reviewer) that shows only what that role should see, and flat pricing with unlimited clinics.
What it does
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.
A denial usually arrives as a letter quoting a policy number, and the clinic spends an afternoon working 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.
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.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited clinics, flat price.