Generated offline from the frozen model and shown here verbatim from the pinned report JSON. This page computes none of these values. The explorer above is illustrative narrative; only its finding badges come from the pack.
Is every modelled business process or service supported by a named application?
business-enablement
Application deployment
23%
18 / 79 covered
Does every application land on named technology?
application-deployment
Governance reach
15%
31 / 204 covered
Is every application and technology element bound to a goal, requirement, principle, or constraint?
governance-reach
Motivation realization
24%
18 / 76 covered
Does every goal, requirement, and principle reach something that implements it?
motivation-realization
Viewpoint documentation
77%
273 / 353 covered
Does every model element appear on at least one viewpoint?
viewpoint-documentation
Executive summary
The submitted model describes 353 elements and 317 relationships across 6 architecture layers (Application 125, Technology 79, Motivation 76, Business 49), drawn on 4 viewpoints.
Across the 5 structural dimensions this report measures, the model is 28% complete. Its strongest dimension is viewpoint documentation at 77%; its weakest is business enablement at 0%.
7 findings follow, 5 of them rated high. Each names the elements that produced it and carries the observable condition that closes it.
The transformation roadmap sequences the findings into 2 horizons; the implementation brief assigns each horizon an owner role, its required inputs, and its exit criteria.
Findings register
opens the element on the explorer canvas, where it carries the finding’s badge · no canvas node: the element carries no source_id
F-01Severity highHorizon 1
Business activity with no application support modelled
11 of 11 business processes and services have no application element serving, realizing, or assigned to them. The model cannot show what runs the work.
Model the application that carries each unsupported activity, or record it as deliberately manual.
Exit criterion
Every business process and service in the model resolves to a named application element or a recorded manual-by-design decision.
F-02Severity highHorizon 1
Application elements with no technology footing
61 of 79 application components and services have no technology node, device, service, or artifact behind them. Hosting, resilience, and data residency cannot be read from the model.
Attach each application to the node, service, or artifact that runs it.
Exit criterion
Every application component and service resolves to at least one technology element.
F-03Severity highHorizon 1
Estate outside the governance boundary
173 of 204 application and technology elements are bound to no goal, driver, requirement, principle, or constraint. Nothing in the model states what governs them.
Add the missing elements to an existing viewpoint or introduce the viewpoint that covers them.
Exit criterion
Every model element appears on at least one viewpoint.
F-07Severity mediumHorizon 2
Data objects read or written under no stated constraint
11 of 21 data and business objects are accessed by at least one element while no requirement, principle, or constraint governs them.
Elements: 11 in total. The report names these:
Not on the canvas: Training Data: AI/Analytics Object Store
Not on the canvas: Training Data: Administrative NAS
Not on the canvas: Training Data: Clinical Order
Not on the canvas: Training Data: Clinical SAN (hot tier)
Not on the canvas: Training Data: DICOM Study
Not on the canvas: Training Data: Insurance Claim
Not on the canvas: Training Data: NDNQI Measure
Not on the canvas: Training Data: PACS Tiered (hot/warm/cold)
Recommended action
Attach the residency, retention, or access constraint that applies to each object.
Exit criterion
Every accessed data and business object carries at least one governing motivation element.
Transformation roadmap
The report’s horizons, each with its implementation brief. They are listed here, not drawn over the canvas.
Horizon 1 — Close the structural gaps
Horizon 1
Repair the places where the model cannot answer a question a board or auditor will ask. These findings block the others: a roadmap built over an incomplete model inherits its blind spots.
Implementation brief
Horizon 1 — Close the structural gaps
Owner role
Governance & Risk Lead
Objective
Repair the places where the model cannot answer a question a board or auditor will ask. These findings block the others: a roadmap built over an incomplete model inherits its blind spots.
Inputs required
The current ArchiMate model in its source form, with edit rights for the named owner.
The system or process owners for the elements named in F-01, F-02, F-03, F-04, F-06.
The governance artifacts — policies, standards, control statements — that the motivation elements should reference.
Sequence
F-01 — Model the application that carries each unsupported activity, or record it as deliberately manual.
F-02 — Attach each application to the node, service, or artifact that runs it.
F-03 — Bind each element to the requirement, principle, or constraint that governs it — or record why none applies.
F-04 — Trace each unrealized goal, requirement, or principle to the element that implements it.
F-06 — Connect each isolated element to the estate, or remove it from the model.
Exit criteria
Every business process and service in the model resolves to a named application element or a recorded manual-by-design decision.
Every application component and service resolves to at least one technology element.
Every application and technology element carries at least one motivation relationship.
Every motivation element reaches at least one business, application, or technology element.
No element in the model has a relationship degree of zero.
Findings in this horizon
F-01Business activity with no application support modelled
Severity highHorizon 1
11 of 11 business processes and services have no application element serving, realizing, or assigned to them. The model cannot show what runs the work.
Model the application that carries each unsupported activity, or record it as deliberately manual.
Exit criterion
Every business process and service in the model resolves to a named application element or a recorded manual-by-design decision.
F-02Application elements with no technology footing
Severity highHorizon 1
61 of 79 application components and services have no technology node, device, service, or artifact behind them. Hosting, resilience, and data residency cannot be read from the model.
Attach each application to the node, service, or artifact that runs it.
Exit criterion
Every application component and service resolves to at least one technology element.
F-03Estate outside the governance boundary
Severity highHorizon 1
173 of 204 application and technology elements are bound to no goal, driver, requirement, principle, or constraint. Nothing in the model states what governs them.
Add the missing elements to an existing viewpoint or introduce the viewpoint that covers them.
Exit criterion
Every model element appears on at least one viewpoint.
F-07Data objects read or written under no stated constraint
Severity mediumHorizon 2
11 of 21 data and business objects are accessed by at least one element while no requirement, principle, or constraint governs them.
Elements: 11 in total. The report names these:
Not on the canvas: Training Data: AI/Analytics Object Store
Not on the canvas: Training Data: Administrative NAS
Not on the canvas: Training Data: Clinical Order
Not on the canvas: Training Data: Clinical SAN (hot tier)
Not on the canvas: Training Data: DICOM Study
Not on the canvas: Training Data: Insurance Claim
Not on the canvas: Training Data: NDNQI Measure
Not on the canvas: Training Data: PACS Tiered (hot/warm/cold)
Recommended action
Attach the residency, retention, or access constraint that applies to each object.
Exit criterion
Every accessed data and business object carries at least one governing motivation element.
Layer profile
Layer
Key
Elements
Share of the model
Relationships
Application
Application
125
35%
221
Technology
Technology
79
22%
83
Motivation
Motivation
76
22%
53
Business
Business
49
14%
44
Implementation & Migration
Implementation_Migration
21
6%
28
Physical
Physical
3
1%
19
Model elements on no viewpoint
10-Year Medical Record Retention
ANCC Magnet Application
Acuity-Based Staffing
Administrator
Attending Physician
BCDR 45-min RTO
CFO / Finance
Care Delivery Service
Chief Nursing Officer
Clinical Protocol Compliance
Code Blue / Rapid Response
Device Health Attestation
Diagnostic Service
Discharge Initiated
EBP & Research / Shared Governance
Electronic Records Validity (Art 3–7)
Facilities Service
Facility Licensing
Facility Management (FMS)
Governance Leadership (GLD)
Health Information Manager
Health Regulator Portal
IAM / RBAC / Break-Glass
Implementation Event — Gap: Core AI — Clinical Services → Infrastructure — AI Compute & Network
Implementation Event — Gap: Current State → Foundation — Security & Governance
Implementation Event — Gap: Foundation — Security & Governance → Core AI — Clinical Services
Implementation Event — Gap: Infrastructure — AI Compute & Network → Target State
In-Country Data Residency (All PHI In-Country)
Incident Reporting
Infection Prevention (PCI)
Information Management (MOI)
JCI Survey Portal
Lab Technologist
Medication Management (MMU)
Micro-Segmentation
NDNQI Collection Trigger
NDNQI Outcomes (15 Indicators from C07)
Nurse Call Response & Triage
Nursing Informatics Service
Order Placed
PHI Encryption At-Rest & In-Transit
Patient / Family
Patient Arrival
Patient Digital Service
Patient Safety Goals (IPSG)
Pharmacist
Pharmacy Service
Practitioner Licensing
QTSP Digital Signatures (Art 16–25)
QTSP Provider (national digital ID / telecom carriers)
Radiologist
Registered Nurse
Regulator Licensing API
Result Available
Retention Architecture (Hot/Warm/Cold)
Revenue Cycle Service
SIEM Correlation & Threat Detection
Shared Governance 5-Council Model
Structural Empowerment
Surgeon
Surgical Service
Tamper-Evident Integrity (Art 26–29)
Transformational Leadership
VIP & Diplomatic Service
VIP Arrival
VIP Liaison
WF-01 Patient Admission & Registration
WF-02 Clinical Documentation & Orders
WF-03 Medication Management
WF-04 Surgical Scheduling & Execution
WF-05 Diagnostic Imaging & Reporting
WF-06 Lab Processing & Results
WF-07 Discharge & Transition
WF-08 Revenue Cycle & Billing
Work Package — AI Infrastructure Buildout
Work Package — Core AI Services Deployment
Work Package — Full Integration & Validation
Work Package — Security & Governance Hardening Package
Workforce Mgmt Service
mTLS Enforcement
Methodology, scope and limitations
Limitations
The report measures the model, not the estate. Systems absent from the submitted model are invisible to it, so coverage figures are upper bounds on what the model can evidence.
Relationship semantics are taken as modelled. A Serving relationship is counted as support whether or not the supporting system is operational.
Coverage is a structural proportion, not a risk score. A fully connected model can still describe an estate with material governance exposure.
Findings name the elements that produced them. Where an element list is longer than the print cap, the report states the full count alongside the sample shown.
Methodology
Every figure in this report is computed from the submitted ArchiMate model. Each coverage dimension counts the elements of one kind that carry a qualifying relationship of another kind, and reports the proportion that do. Findings are the complement of those counts, named to the elements that produced them, so any figure can be traced back to the model. No score is inferred from documents, interviews, or benchmarks, and no element is scored on quality — this report measures structure, not intent.
Disclosure
This posture reads the structural completeness of the architecture model itself — how far its business, application, technology, and motivation elements connect to one another. It is not a governance certification: a certified tier is issued only from a governance assessment.
Report metadata
Version
1.0
Owner
blank in the report
Classification
Public sample
Date
2026-10-17
Downloads
The pack’s own files, served exactly as pinned. Check a download against its sha256.