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
- Integrations and source ownership
Integrations and source ownership
Connect video, clinical records, e-prescribing, identity and billing with clear ownership of each record.
- Telemedicine Platform
- Telehealth video service
- Electronic health record
- E-prescribing
- Identity provider
- Billing
Systems to connect
-
Telehealth video service. Consultations take place in your video service; session provider, start and duration are recorded here.
-
Electronic health record. Patient and consent references, encounter notes and results come from your EHR or the provider’s clinical system.
-
E-prescribing. Prescriptions are issued in your e-prescribing system.
-
Identity provider. Map team members to user accounts; disabling a sign-in must remove access here too.
-
Billing. Claims and invoices for attested services stay in your billing system.
How connections are governed
Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated evidence message must not add a second line, and a repeated close must not close a session twice. Queue rejected records with their source identifier and a visible reason.
Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.
Use the implementation plan to agree integration acceptance criteria.
Set up Telemedicine Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.