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
- Data model and import order
The tables behind Telemedicine Platform
Telemedicine Platform ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 10
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Care requests:
Care requests, record attachments. Status Requested, Review, Authorized, Scheduled, Attested, Declined or Cancelled, with a Revision.
Clinical review:
Review decisions. Decision Approve, Reject or Return with Reason and source revision.
Consultation sessions:
Consultation sessions. Status Draft, Submitted, Approved, Rejected or Completed, with Provider, starts at and duration minutes.
Clinical evidence and attestation:
Clinical evidence. Verification status Pending, Verified or Rejected, with external record ID and clinical system.
Provider network:
Provider organizations, Organizations, team members, Users.
Operation receipts:
Operation receipts. Result state Pending, Completed, Failed or needs review.
Every table, by feature
- Care requests4
- Clinical review5
- Consultation sessions3
- Clinical evidence and attestation3
- Provider network4
- Operation receipts2
- Care requests
Scoped care requests with lifecycle, consent, authorization and attestation evidence.
Linked to Organizations, Team members, Provider organizations - Record attachments
Uploaded evidence files with visibility scope attached to a care request.
Linked to Care requests, Team members - Provider organizations
Eligible provider organizations that receive care requests and return encounter evidence.
Linked to Organizations - Team members
Authenticated platform identities with an organization membership and role scope.
Linked to Organizations, Users
- Review decisions
Independent professional review decisions recorded against a source revision.
Linked to Care requests, Team members - Care requests
Scoped care requests with lifecycle, consent, authorization and attestation evidence.
Linked to Organizations, Team members, Provider organizations - Consultation sessions
Provider-attested consultation sessions closed through guarded review.
Linked to Care requests, Organizations - Clinical evidence
Provider-supplied clinical evidence lines attached to a care request.
Linked to Care requests - Team members
Authenticated platform identities with an organization membership and role scope.
Linked to Organizations, Users
- Consultation sessions
Provider-attested consultation sessions closed through guarded review.
Linked to Care requests, Organizations - Care requests
Scoped care requests with lifecycle, consent, authorization and attestation evidence.
Linked to Organizations, Team members, Provider organizations - Organizations
Tenant organizations that own care requests, provider relationships and team membership.
- Clinical evidence
Provider-supplied clinical evidence lines attached to a care request.
Linked to Care requests - Care requests
Scoped care requests with lifecycle, consent, authorization and attestation evidence.
Linked to Organizations, Team members, Provider organizations - Record attachments
Uploaded evidence files with visibility scope attached to a care request.
Linked to Care requests, Team members
- Provider organizations
Eligible provider organizations that receive care requests and return encounter evidence.
Linked to Organizations - Organizations
Tenant organizations that own care requests, provider relationships and team membership.
- Team members
Authenticated platform identities with an organization membership and role scope.
Linked to Organizations, Users - Users
Users
Linked to Users
- Operation receipts
Durable receipts for guarded operations with stable operation keys and result state.
Linked to Care requests - Care requests
Scoped care requests with lifecycle, consent, authorization and attestation evidence.
Linked to Organizations, Team members, Provider organizations
Keys and references
A care request references its organization, owner and provider organization. Sessions, evidence lines, attachments, decisions and receipts each reference one care request as Parent. Decisions and attachments also reference a team member. Provider organizations and team members belong to one organization.
Patient and consent are held as references to your clinical system. Import providers by Code and requests by record number. Keep revisions and operation keys as recorded.
Migration order
- Load Organizations, Users and team members.
- Load provider organizations with eligibility notes.
- Load open care requests with patient and consent references.
- Load consultation sessions, clinical evidence and existing review decisions for those requests.
- Load record attachments.
- Reconcile open requests and sessions with the source, test permissions and replay the exception cases before go-live.
Set up Telemedicine Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.