Skip to main content

D2 – System Architecture & Constellation Governance

Purpose of the Domain​

D2 ensures that digital clinical infrastructure is understood and governed not as a collection of individual systems,
but as an integrated clinical system constellation.

Digital impact does not arise within isolated systems.
It emerges from the interaction of applications, medical devices, data flows, integrations, responsibilities, and operational structures.

This domain operationalizes Principle P2 – Holistic System Responsibility – at a structural level.

Core Governance Question​

Is digital infrastructure systematically planned, documented, and governed as an integrated clinical system constellation?

D2 addresses more than architecture diagrams.
It concerns the organization’s ability to incorporate systemic dependencies into decision-making.

Problem Context​

In many organizations, systems are:

  • procured component-by-component
  • integrated project-by-project
  • documented in isolation
  • operated separately

Typical consequences include:

  • interface failures despite stable individual systems
  • unclear integration responsibility
  • unexpected side effects after updates
  • local optimizations with global consequences

Without structural constellation governance, digital infrastructure becomes complex —
but not controllable.

Structural Requirements​

A mature expression of D2 requires:

  • Transparent representation of clinical system constellations
  • Visibility of relevant data flows and integration points
  • Clear allocation of integration responsibility
  • Evaluation of changes in the context of the overall constellation
  • Consideration of regulatory operator obligations at constellation level

Architecture in this context does not mean technical elegance.
It means governable interdependencies.

Relationship to Other Domains​

  • D1 defines the clinical purpose of the constellation.
  • D2 structures its architectural reality.
  • D3 allocates responsibility within the constellation.
  • D4 evaluates patient-relevant risks across system boundaries.
  • D5 ensures long-term operational sustainability of the constellation.
  • D6 enables controlled evolution.

D2 forms the structural frame
within which all other domains become operationally effective.

Typical Misconceptions​

  • “If every system runs reliably, the constellation is stable.”
  • “Integration is primarily a technical task.”
  • “Interfaces are minor details.”
  • “Architecture is a one-time project.”

System architecture is not a document.
It is a continuous governance process.

Indicators of Structural Stability​

D2 is structurally stable when:

  • Clinical system constellations are explicitly described
  • Integration dependencies are transparent
  • Changes are evaluated at constellation level
  • Procurement decisions are not made in isolation

D2 is weakly developed when:

  • There is no consolidated overview
  • Interface issues are treated reactively
  • Integration responsibility remains implicit
  • Architectural knowledge depends on individuals

D2 ensures that digital clinical infrastructure does not grow in fragmented fashion,
but remains governable as an integrated component of clinical care.