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 evidence and attestation
Clinical evidence and attestation
Receive evidence lines from the provider's clinical system, verify them, and attest a service only on verified evidence.
OverviewEvidence Awaiting Verification×
Telemedicine Platform · Clinical evidence and attestation
New
Evidence Awaiting Verification
Approval conditions
| Parent | Evidence type | Occurred at | External record ID | Provider | Clinical system | |
|---|---|---|---|---|---|---|
| CR-89823 | ET-628 | 13 Oct | ERI-604 | PRV-296 | CS-636 | |
| CR-39809 | ET-887 | 14 Oct | ERI-845 | PRV-413 | CS-732 | |
| CR-93592 | ET-693 | 22 Oct | ERI-374 | PRV-742 | CS-799 | |
| CR-31779 | ET-772 | 14 Oct | ERI-644 | PRV-854 | CS-316 | |
| CR-46374 | ET-953 | 04 Oct | ERI-907 | PRV-274 | CS-380 |
6 of 6 records
ET-628Clinical evidence · CE-22222
ParentCR-89823
Occurred at13 Oct
External record IDERI-604
ProviderPRV-296
Clinical systemCS-636
What you can do
Attest only what the provider's record shows
Clinical evidence comes from the provider that delivered the care. Each line records its number, the revision, the evidence type, when it occurred, the external record identifier in the provider’s system, the provider, the clinical system it came from and its verification status: Pending, Verified or Rejected. The evidence stays linked to its source; the clinical record itself stays in the provider’s system.
A request moves to Attested only on verified evidence from the authoritative provider. When the evidence arrives, the request’s identity and revision are checked again, and the attestation date is recorded. Rejected or missing evidence leaves the request unresolved, visible on the exception queue, until the provider supplies what is needed.
How the work is organized
- Evidence from the source. Each line names the external record and clinical system it came from.
- Verify before attesting. Only verified lines can support attestation. Pending lines wait; rejected lines stay on record with the request unresolved.
- Re-check identity. Attestation re-checks the request’s identity and revision against the evidence.
What to agree during setup
Agree with each provider how evidence is sent and which clinical systems it comes from. Agree what makes a line verified, such as a matching patient reference and encounter date. Agree who follows up rejected or missing evidence and how quickly. Agree evidence types, such as encounter note, lab result or imaging report.
Check the handoff on an actual case
After the June 4 dermatology session, the provider’s system sends an encounter note with external record ID ENC-77120 from its clinical system. The line arrives Pending. The Provider Network Manager checks the patient reference and date, and it becomes Verified. The request’s identity and revision are re-checked and it moves to Attested with June 5 as the attestation date.
For another patient, the provider sends an encounter note dated a day before the consult. The line is Rejected. The request stays unresolved and appears on the exception queue. The manager contacts the provider, a corrected note arrives and is verified, and the request is attested.
What your team sees
- Evidence Awaiting Verification — Pending evidence lines with type, date, external record and clinical system.
- Evidence Lines — All evidence by verification status.
- Attachment Register — Uploaded files with their visibility and evidence type.
Follow the work through
- Session to attested service: Verify the evidence and attest the service.
Connect your providers’ clinical systems before go-live.
What it keeps track of
Data model- Clinical evidence
- Provider-supplied clinical evidence lines attached to a care request.
- 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.
Who uses it
Permissions- Provider Network Manager
- Receives and follows up evidence.
- Clinical Reviewer
- Reads evidence before deciding.
- Care Coordinator
- Reads it when chasing unresolved requests.
- 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.