Referral intake
Find what is missing before the handoff.
Read incoming referrals, check the required documents and route missing-information requests. Patient access staff review the packet before the scheduling handoff.
Discuss your use casePatient: A. Whitfield.
Requested service: Cardiology consultation.
- Patient
- A. Whitfield p. 1
- Requested service
- Cardiology consultation p. 1
- Referral date
- October 6, 2026 p. 1
What it handles
Find what is missing before the handoff.
Read incoming referrals, check the required documents and route missing-information requests. Patient access staff review the packet before the scheduling handoff.
Check completeness against the intake checklist. Clinical decisions stay with clinicians.
Referral IntakeReferral R-2041 - Intake packetNeeds reviewExtracted4 fields- Patient
- A. Whitfield p. 1
- Requested service
- Cardiology consultation p. 1
- Referral date
- October 6, 2026 p. 1
- Required imaging
- Not attached p. 2
Checks- Required attachments presentRequest the imaging report before handoff
- Patient details agree
Approve reviewOpen source
How it fits
From source documents to a reviewed decision.
Connect the sources, set the checks and keep the review with the people responsible for the decision.
Comes in from
- Source documentsReferral forms, uploaded records, insurance documents and your intake checklist.
- Your records and rulesCriteria, thresholds and prior decisions
- 01ReadDocuments and records with sources retained
- 02CheckAgainst your criteria and agreed terms
- 03ReviewPeople approve the findings and next action
Goes out to
- A review appA referral board with document checks, missing items and review status.
- Approved resultsExport or write back after review
What you can do.
Read the sources
Referral forms, uploaded records, insurance documents and your intake checklist.
Apply your checks
Classify attachments, match patient details, check completeness and route follow-ups.
Review in one app
A referral board with document checks, missing items and review status.
Keep the decision with your team
Staff work the incomplete packets with the source documents beside them.
Apps for this work
Security
Security your IT team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.
Security
SOC 2 Type II
Independently audited security controls, tested over time.
Europe
GDPR
Personal data handled under the EU's data protection rules.
California
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
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.