Healthcare · Intake & routing
Referral Intake and Status Updates
Starts when: A new referral is received
Free plan · Outcome verification included · You approve every connection
How it runs
Six stages, from the moment it starts to the checks that keep running afterwards.
It starts
A new referral is received
Awish plans it and asks for each app
The apps it needs are connected one at a time, with your permission, before anything runs.
It does the work
Exactly as the request below describes, across the connected apps.
It stops where a person should decide
Verify patient identity and authorisation, and never disclose patient health information to an unverified recipient.
It verifies the outcome
After each run, Awish checks that the intake, referral or claim reached the right queue with its documents.
It keeps monitoring
Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.
The request it runs
This is what opens in chat when you use the template. Change any part of it before anything connects.
“Create an automation that manages referral intake, the document check and the status updates end to end. Start it whenever a new referral is received. It should extract the referring provider, the patient and the service, check the required documents, request the missing items, create the referral record, route it to the specialty queue and send status updates to the authorised parties. Connect it with Microsoft Teams, SharePoint and Asana, alongside the referral system and the patient messaging channel. Verify patient identity and authorisation, and never disclose patient health information to an unverified recipient.”
- Microsoft Teams
- SharePoint
- Asana
Monitoring included
What Awish watches once this template is running.
- Outcome verificationEvery plan
- Silent-failure detectionEvery plan
- Connection healthEvery plan
- Hours saved and ROIEvery plan
- Anomaly detectionOn Business
- Root-cause explanationOn Business
- Recovery recommendationOn Business
Questions about this template
Can I change where it stops for approval?
Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.
What if one of these apps is not connected yet?
Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.
How does Awish know this workflow worked?
After each run it checks that the intake, referral or claim reached the right queue with its documents, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.
Run it on your own apps
It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.
Free plan · No credit card required