REMOTE CARE ENCOUNTER

Telehealth

A teleconsultation journey from appointment and readiness through identity, consent, waiting room, video/chat/upload, clinical output, orders/ePrescription, escalation, follow-up and evidence.

Product capabilityPatients, clinicians and remote-care support staffIntegration-dependent where noted

Explore workflow View integrations Request a demo

01 · WORK CONTEXT

Built around the actor, object and decision—not generic feature cards

PERSONA

Patients, clinicians and remote-care support staff

OBJECTS

Appointment · Encounter · Consent · Media/document · Order · Prescription · Follow-up

WORK MODEL

Create/receive appointment → Readiness & device/network check → Identity & consent → Waiting room…

TRUST BOUNDARY

Encounter-bound identity · Purpose-specific consent · Document/media provenance

02 · WORKFLOW

End-to-end operating flow

Every step exposes state, owner, handoff and recovery expectations.

Create/receive appointment

Readiness & device/network check

Identity & consent

Waiting room

Video / chat / upload

Clinical assessment & output

ePrescription / order

Follow-up, handoff & evidence

03 · DECISIONS

Where workflow becomes accountable

Decision 1

Are identity and consent sufficient before entering the encounter?

Decision 2

Is connection quality sufficient to continue or should the channel change?

Decision 3

Can the condition remain remote or does it require escalation/in-person care?

04 · SCREEN STORY

Verified source screens, ordered by business importance

**Telehealth — Trusted Device Approval**

**Telehealth — Payment On Behalf Limit**

**Telehealth — Payment Failed Timeout Duplicate And Retry**

**Telehealth — Invoice Electronic Receipt**

**Telehealth — Partial Failure And Retry**

**Telehealth — Evidence Receipt With Hash And Timestamp**

05 · EXCEPTIONS

Failure must preserve state and evidence

Failure must preserve state and evidence
#	Scenario & required behavior	Treatment
01	Connection loss preserves encounter state and offers reconnect/channel change.	Controlled recovery
02	If identity/consent cannot be established, the clinical portion requiring that assurance does not start.	Controlled recovery
03	Clinical escalation records reason, destination, handoff context and acknowledgement.	Controlled recovery

06 · TRUST & INTEGRATION

Controls and system boundaries

Trust controls

Encounter-bound identity

Purpose-specific consent

Document/media provenance

Clinical output & evidence receipt

Integration surfaces

Scheduling

Doctor / Patient portals

FHIR Appointment / Encounter / Communication

ePrescription / Laboratory / Imaging orders

Appointment readinessConnection recoveryConsultation completionFollow-up closure

07 · RELATED

Continue the product story

APPLICATION ACCESS

Governed application access

Access to this portal is granted on request. Submit an access request to get an account.