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.
- Telemedicine Platform
- Features
- Care requests
Care requests
Record each care request with its patient and consent references, verify identity, and follow it from intake to attestation.
OverviewReview Queue×
Telemedicine Platform · Care requests
New
Review Queue
Care requests
| Record number | Subject | Patient reference | Consent reference | Counterparty | Requested units | |
|---|---|---|---|---|---|---|
| CR-28271 | Review cr-710 | PR-660 | CR-656 | PO-4290 | 450 | |
| CR-71131 | Review cr-667 | PR-376 | CR-536 | PO-6510 | 780 | |
| CR-73819 | Review cr-491 | PR-837 | CR-822 | PO-8527 | 240 | |
| CR-33371 | Review cr-108 | PR-143 | CR-423 | PO-3830 | 50 | |
| CR-36337 | Review cr-529 | PR-429 | CR-974 | PO-4702 | 870 |
6 of 6 records
Review cr-710Care requests · CR-28271
Patient referencePR-660
Consent referenceCR-656
CounterpartyPO-4290
Requested units450
Revision600
What you can do
Start every consult from a verified request
A care request is the authority for a piece of remote care: a teleconsultation, a specialist review, a series of follow-up sessions. The Care Coordinator records it with a record number, a subject, the patient reference and consent reference from your clinical system, the date requested, the number of units requested, and the provider organization that will deliver it. The coordinator owns the request and answers for its paperwork.
Before anything clinical happens, the coordinator verifies who the patient is, which provider will deliver the care and that consent is on file. The request then goes to review. Coordinators prepare and route requests; they never make the clinical decision. The request moves through Requested, Review, Authorized, Scheduled and Attested, or ends as Declined or Cancelled. Every change raises its revision.
How the work is organized
- Intake with references. Patient and consent references point to your clinical system, so personal health information stays where it is held.
- Verify before review. Identity and consent are checked before the request reaches a clinical reviewer.
- One owner, one revision. The coordinator owns the request. A change after authorization creates a new revision that needs a new decision.
What to agree during setup
Agree the format of patient and consent references from your clinical system. Agree what counts as a unit: one consult, one 30-minute session or one episode of care. Agree how identity is verified and what the coordinator records as proof. Decide which supporting documents are attached as Internal and which may be Shared with the provider. Agree how quickly new requests must reach review.
Check the handoff on an actual case
A primary care clinic asks for a dermatology teleconsult for a patient with a persistent rash. The coordinator records the request: subject “Dermatology teleconsult”, the clinic’s patient reference, the signed telehealth consent reference, two units requested and the partner dermatology group as provider. She attaches the referral letter as Shared and the clinic’s internal notes as Internal, checks the patient’s identity against the referral and moves the request to Review.
The reviewer returns it: the consent covers one consult, not two. The coordinator obtains an updated consent reference, which raises the revision, and sends it back. The reviewer authorizes it, and the coordinator schedules the first session with the dermatology group.
What your team sees
- Lifecycle Board — Open requests grouped by Requested, Review, Authorized and Scheduled, with provider, owner and revision.
- My Care Requests — The signed-in coordinator’s own requests and where each one stands.
- Request Register — Every request with patient reference, units, authorization and attestation dates.
Follow the work through
- Request to clinical authorization: Verify the request and take it through clinical review.
- Correction and cancellation: Cancel or correct a request with its history kept.
Review the data model before importing open requests.
What it keeps track of
Data model- Care requests
- Scoped care requests with lifecycle, consent, authorization and attestation evidence.
- Record attachments
- Uploaded evidence files with visibility scope attached to a care request.
- Provider organizations
- Eligible provider organizations that receive care requests and return encounter evidence.
- Team members
- Authenticated platform identities with an organization membership and role scope.
Who uses it
Permissions- Care Coordinator
- Records, verifies and routes requests.
- Clinical Reviewer
- Decides on requests in review.
- Operations Analyst
- Reads the register when reconciling receipts.
- Admin
- Corrects records and access.
Set up Telemedicine Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.