My referrals
A referral management portal is where referring doctors send referrals and follow their status, the specialist clinic accepts or declines each one with a reason, and the consult report goes back to the doctor who sent it.
Pattern: RequestsDescribe it to Pory
“Our orthopedic clinic wants referring doctors to send referrals with a letter attached, our intake team to accept or decline them, and our specialists to send the consult report back.”
My referrals
In plain English
A referral management portal is where referring doctors send referrals and follow their status, the specialist clinic accepts or declines each one with a reason, and the consult report goes back to the doctor who sent it. 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 (referring doctor, intake coordinator and specialist) that shows only what that role should see, and flat pricing with unlimited referring doctors.
What it does
Referrals still arrive by fax, by mail, or as a phone call to a receptionist with a pen. The referring doctor signs in, enters the patient, the reason and how urgent it is, and attaches their letter. The clinic gets a legible, complete referral in one queue, and nobody asks the fax machine to try again.
A declined referral used to mean a letter weeks later, or silence, while the patient waited by the phone. The intake coordinator opens the referral, reads the letter, and accepts it or declines it with a note, like a better-suited clinic. The referring doctor sees the answer and the reason, so the patient isn't left wondering.
Referring offices call the clinic to ask whether a patient was ever seen, and the receptionist goes digging through a paper tray. Each referring doctor sees their own referrals as a progress bar: Sent, Accepted, Seen, Report sent. When a patient asks whether the specialist got their referral, the answer is on screen during the consult.
The loop closes with a consult letter mailed back, if it closes at all, and the referring doctor hears the outcome from the patient first. The specialist uploads the consult letter or imaging report against the referral, and the referring doctor opens it from their own list. No chasing, and no "we never received 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 referring doctors, flat price.