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
- Clinical review
Clinical review
An authorized clinical reviewer records an independent approve, reject or return decision against the exact revision of each request and session.
OverviewDecision Register×
Telemedicine Platform · Clinical review
New
Decision Register
Review decisions
| Parent | Source revision | Decision | Reason | Reviewer | Decided at | |
|---|---|---|---|---|---|---|
| CR-24811 | 500 | Approve | Approve rd-574 | 06 Oct | ||
| CR-72238 | 240 | Return | Reject rd-470 | 04 Oct | ||
| CR-76055 | 140 | Approve | Return rd-258 | 15 Oct | ||
| CR-50255 | 240 | Return | Approve rd-287 | 04 Oct | ||
| CR-55660 | 780 | Approve | Reject rd-451 | 16 Oct |
6 of 6 records
Approve rd-574Review decisions · RD-31232
ApproveParentCR-24811
Source revision500
Decided at06 Oct
What you can do
A clinician decides, against the evidence
Care is authorized by a clinician, not by the person who prepared the paperwork. The Clinical Reviewer is an active team member in the same organization who did not prepare the request. The reviewer reads the request, the verified evidence and the attachments, then records Approve, Reject or Return with a written reason. The decision names the revision it was made on and the exact verified evidence reference it relied on.
Approval authorizes the request and records the authorization date. Rejection declines it. Return sends it back to the coordinator with a reason, such as consent that does not cover the requested units. The reviewer also approves the close of each consultation session, checking the provider, timing, duration and encounter reference against verified evidence.
How the work is organized
- Independent reviewer. The person who prepared the request cannot approve it. The reviewer is named on the decision.
- Decision tied to evidence. Each decision records the revision and the verified external evidence reference.
- A reason every time. Approve, Reject and Return all carry a written reason the coordinator can act on.
What to agree during setup
Agree who holds clinical review authority in each organization and the specialties they cover. Agree what the reviewer must see before deciding: the referral, the consent and any prior results. Agree when to return and when to reject. Set a turnaround target for requests in review, especially for urgent consults. Agree how a reviewer records that they hold no conflict with the provider.
Check the handoff on an actual case
A request for a cardiology follow-up reaches review at revision 3. The attached ECG report is listed as evidence, but its verification is still pending. The reviewer returns the request with the reason “ECG evidence not yet verified by the provider”. Two hours later the provider’s system verifies the ECG line. The coordinator re-routes the request, and the reviewer approves revision 3 with the ECG’s external record reference.
After the consultation, the cardiologist’s session is submitted for close. The reviewer checks that the provider, start date and 30-minute duration match the encounter evidence and approves the close. A coordinator who tried to approve the request herself would have been refused.
What your team sees
- Review Queue — Requests in review with patient and consent references, provider, units and revision.
- Sessions Awaiting Review — Submitted sessions with provider, start date and duration.
- Decision Register — Every decision with revision, outcome, reason, reviewer and date.
Follow the work through
- Request to clinical authorization: The decision that authorizes care.
- Session to attested service: The decision that closes a session.
Check roles and permissions before naming reviewers.
What it keeps track of
Data model- Review decisions
- Independent professional review decisions recorded against a source revision.
- Care requests
- Scoped care requests with lifecycle, consent, authorization and attestation evidence.
- Consultation sessions
- Provider-attested consultation sessions closed through guarded review.
- Clinical evidence
- Provider-supplied clinical evidence lines attached to a care request.
- Team members
- Authenticated platform identities with an organization membership and role scope.
Who uses it
Permissions- Clinical Reviewer
- Records decisions on requests and session closes they did not prepare.
- Care Coordinator
- Acts on returned requests.
- Operations Analyst
- Reads decisions when reconciling.
- Admin
- Manages who holds review authority.
Set up Telemedicine Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.