Design Telehealth Platform - System Design | WinJob

Telehealth platform framing and care journeys

Anchor the three-sided marketplace: demand (patients), supply (clinicians), and compliance middleware (BAA-covered platform). This section focuses on telehealth platform framing and care journeys for a Teladoc-class telehealth platform—not a generic video chat app.

Numbers to state early

Metric A: 18M MAU
Metric B: p95 join < 45s
Metric C: 99.95% scheduling API

Mechanism

Patients book async or live visits; providers join from a licensed-state-aware queue; the platform mediates video, charting, and billing without storing raw card PANs.

Failure and edge cases

Treating telehealth as generic Zoom ignores state licensure, consent capture, and encounter IDs tied to billing.

When discussing Telehealth platform framing and care journeys, anchor 18M MAU and explain how Patient → Provider → Platform interacts with HIPAA visit boundaries, licensure checks, and async EMR export—not consumer messaging scale math alone.

Java

javaOne Dark Pro

1 public record VisitIntent(String patientId, String stateCode, VisitMode mode) {}

Python

pythonOne Dark Pro

1 @dataclass(frozen=True)
2 class VisitIntent:
3     patient_id: str
4     state_code: str
5     mode: str

TypeScript

typescriptOne Dark Pro

1 export interface VisitIntent {
2   patientId: string;
3   stateCode: string;
4   mode: "sync" | "async";
5 }

Why interviewers care

Telehealth Platform interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Telehealth platform framing and care journeys that proves you understand real outages, not happy-path diagrams.

Key Highlights

•18M MAU
•Patient → Provider → Platform
•Patients book async or live visits; providers join from a licensed-state-aware queue; the

1	@dataclass(frozen=True)
2	class VisitIntent:
3	patient_id: str
4	state_code: str
5	mode: str

1	export interface VisitIntent {
2	patientId: string;
3	stateCode: string;
4	mode: "sync" \| "async";
5	}