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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
C4 system context review
Key decisions
- People and system: Identifies the human users of the system.
- External dependencies: Separates the clinic system from providers it integrates with.
- Scope boundary: Keeps internal implementation details out of the context view.
When to reuse this
Use this C4 context view to agree on system scope and external integrations.
Frequently asked questions
What belongs in a C4 context diagram?
Does it show databases?
Why keep external systems separate?
More software architecture examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.