Healthcare template
Referral intake
Agents read faxed and portal referrals, check insurance and find what is missing. Your patient access team works one board from the first page to the scheduled visit.
The handoff
Give every referral a clear next step.
Before: the work is in the inbox.
The access team opens each fax, copies the details and works out what is missing. The next person has to read it again to know where it stands.
After: the work has an owner.
Agents read the pages and check for missing information. The board shows the follow-up, its owner and the source, so staff can move the referral forward.
New routing rule
Coverage active. Prior authorization is required for the requested service. Authorization status: not received.
The app
A board built around patient access.
See what arrived, what needs a follow-up and what is ready to schedule. Ask for a new column or routing rule as your process changes.
Illustrative app. All companies, people and figures are sample data.
What it reads
- Faxed and portal referral documents
- Patient and referring office details
- Insurance and authorization responses
- Orders and supporting attachments
What your team sees
- A board from received to scheduled
- Missing information on each referral
- Insurance and authorization status
- The owner of each next step
What you set
- The fields and required attachments
- Who owns each follow-up
- Rules for moving between columns
- When a referral is ready to schedule
Questions
What people ask about referral intake.
Can we add a column for our own intake process?
Yes. Describe the change to the Assistant. It can change your workflows and apps, and every change is shown for your approval.
Can staff check what was read from a referral?
Yes. Extracted values are cited to their pages. Review queues can put each value beside its source passage so a person can approve or edit it.
Can you set up the board for our team?
Yes. We can map your process with you, build the workflows and the app, and hand your team something ready to use.
Is our data used to train models?
No. Your documents and results are never used to train a model, and a data processing addendum backs that.
Can it run in our own environment?
Yes. Strive runs in our cloud, or in your own VPC on AWS, Google Cloud or Oracle Cloud, or on your own Kubernetes cluster.
Which document-heavy job would you hand over first?
Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.
Contact SalesAn hour of your time and a process you know well. That's all it takes.