ChatDiagram
Essayer gratuitement
software architecture · healthcare

C4 System Context for an Online Clinic

This C4 system context diagram puts the online clinic system at the center and deliberately stays at the broadest architectural level. Patients, clinicians and clinic administrators are the people who use it. Calendar, video, messaging and health-records services are external software systems it relies on. This is the right drawing for a stakeholder conversation about scope, ownership and integration boundaries; it is not a deployment diagram or a database design. The next C4 level would replace the central system with containers such as a web application, API and data store. Add insurers, pharmacies, identity providers or analytics systems only when their relationship is important to the system boundary.

Type Schéma fonctionnelNorme Ogata / standard controls textbook conventionMoteur schematex-blockdiagramMis à jour 24/09/2026
C4 System Context for an Online Clinic
Drawing preview
La demande

“A C4 system context diagram for an online clinic system. Show patients, clinicians and clinic administrators using the online clinic system. The system connects to a calendar provider, video service, email and SMS service, and health records system.”

Essayez ensuiteAdd an insurance eligibility serviceAdd a pharmacy system connected to the clinic
Ce que contient ce dessin

Comprenez les décisions qui le sous-tendent.

01People and system

Identifies the human users of the system.

02External dependencies

Separates the clinic system from providers it integrates with.

03Scope boundary

Keeps internal implementation details out of the context view.

Use this C4 context view to agree on system scope and external integrations.

Voir tous les modèles de schéma fonctionnel →

FAQ

Questions fréquentes

What belongs in a C4 context diagram?

People, the system being described and the external systems it interacts with.

Does it show databases?

Usually not. Databases are normally introduced in a container or component view.

Why keep external systems separate?

It makes ownership boundaries and integration responsibilities visible.