These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Pharmacy Management System
- Features
- Care requests
Care requests
A care request carries the requested units, patient reference, assigned owner and provider party through authorization.
OverviewAuthorization review inbox×
Pharmacy Management System · Care requests
New
Authorization review inbox
Care requests
| Record number | Subject | Status | Revision | Requested at | Owner | |
|---|---|---|---|---|---|---|
| CR-18887 | Review cr-394 | Review | 880 | 12 Oct | ||
| CR-47403 | Review cr-282 | Review | 200 | 17 Oct | ||
| CR-10303 | Review cr-286 | Review | 360 | 06 Oct | ||
| CR-44747 | Review cr-571 | Review | 730 | 21 Oct | ||
| CR-61964 | Review cr-393 | Review | 760 | 17 Oct |
6 of 6 records
Review cr-394Care requests · CR-18887
ReviewRevision880
Requested at12 Oct
What you can do
Work from the linked record
A care request carries the requested units, patient reference, assigned owner and provider party through authorization. The coordinator prepares a request under the right pharmacy organization and checks that the provider party is active. The reviewer works from the request revision and the attached evidence. A later edit must be considered against the revision already decided. The authorization desk gives the team a daily queue ordered around requests needing attention, including returned work and blocking reasons.
The request number, owner and requested date give the coordinator a clear starting point. The provider party and patient reference make the request traceable to the case under review. Read the decision reason alongside the request status; a revision made after review calls for another look at the changed record.
How the work is organized
- Assign the request. Choose the pharmacy organization, provider party and responsible team member.
- Collect the evidence. Link clinical evidence and attachments to the request before review.
- Read the decision. Compare the reviewer reason and source revision with the current request.
Open the Care Request Authorization Desk to see requests awaiting action and the reasons they are held. Its rows open the native care request. For returned work, inspect the reviewer decision, correct the linked evidence and preserve the earlier decision when the case goes back for review.
What to agree during setup
Agree who owns a request when it enters the queue, which provider party should be selected, and how the patient reference from the source system is handled. Decide which evidence must accompany each kind of request before the reviewer acts. Keep an assigned coordinator distinct from the reviewer who records the decision.
Rehearse a request under one pharmacy organization with a named coordinator and reviewer. Check the patient reference, clinic and requested units before review. Agree how the coordinator will respond when the reviewer returns the case or when its revision changes.
Check the handoff on an actual case
Take a request for a verified prescription and a specific patient reference. The coordinator enters the requested units and links the clinic. The reviewer checks the clinical evidence and records an approval, rejection or return with a reason. The coordinator then records the corresponding request status and checks that the decision still points to the reviewed revision.
Before the next handoff, the Care Coordinator checks the request owner, provider party and requested units. The Authorized Clinical Reviewer reads the current revision with its evidence and leaves a reason on the decision. If the request is returned, the coordinator can find the specific issue to correct.
What your team sees
- Care request queue — The starting screen for the module’s current work and linked records.
- Care request board — A related screen for checking the neighboring handoff or exception.
Follow the work through
Follow prescription to dispensing and care authorization. Review the data model when mapping source identifiers.
What it keeps track of
Data model- Care requests
- Patient care and dispensing request records
- Provider organizations
- Prescriber clinics and provider parties
- Organizations
- Pharmacy organization master record
- Team members
- Staff membership linking platform users to an organization role
Who uses it
Permissions- Care Coordinator
- , Authorized Clinical Reviewer, App Administrator work from their assigned records and review the related evidence before completing the handoff.
- App Administrator
- Maintains the configuration used by the operating team.
Set up Pharmacy Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.