EXECUTIVE SUMMARY FOR EXPERT REVIEWERS

EXECUTIVE SUMMARY FOR EXPERT REVIEWERS [4]

1. Purpose of the document

The Vien gut Model is built on a three-layer architecture: WHAT — HOW — DATA-to-operate. These three layers appear consistently from A.0 to C.4 and serve as the common language for the entire document series [4]. Document A.2 has a single purpose: to precisely identify and define these three layers — where the boundaries between them lie, and why they cannot compensate for each other — before the reader proceeds to Part B (Operational Model) and Part C (Validation Targets) [4].

$A.1 identifies structural fractures in the EBM chain → A.2 defines the three layers filling that gap → A.3 confirms the gap with international evidence → A.4 implements detailed operational terminology [5].$

2. Definition of the three architectural layers

2.1. WHAT — Treatment Knowledge Layer

Aspect	Content
Identification	WHAT (What to do) — Evidence-based treatment knowledge layer [5]
Definition	A collection of treatment goals, clinical principles, biochemical thresholds, medication recommendations, and disease management strategies — established by international guidelines based on evidence from RCTs, systematic reviews, and expert consensus [5].
Connotation	Single-disease guidelines (EULAR, ACR, KDIGO, ESC, EASL, ADA); international consensus on multimorbidity (NICE NG56, JA-CHRODIS, WHO ICOPE); treatment targets (T2T, remission criteria); disease staging; medication principles, contraindications, and interactions [6].
Denotation	WHAT DOES NOT include: operational organization procedures; how to coordinate multiple guidelines on the same patient; longitudinal monitoring data that triggers decisions; mechanisms for continuous feedback and adjustment [6].
Operationalization	Part B: Application of ACR 2020, KDIGO 2024, ESC 2021, EASL 2018 guidelines. C.1: 18 guidelines consistent on crystal-free. C.2–C.4: guidelines for renal preservation, prevention of heart failure decompensation, and cirrhosis re-compensation [6].

2.2. HOW — Clinical Operational Layer

Aspect	Content
Identification	HOW (How to operate) — Structured clinical operational layer [7]
Definition	A clinical operation organization system: procedures, role assignment, action thresholds, multidisciplinary coordination mechanisms, guideline conflict resolution, and safety protection — allowing WHAT to be applied to the right person, at the right time, and at the right safety level [7].
Connotation	Clinical Conductor coordinating the vertical axis; multidisciplinary team; T1–T4 stratification; 4-phase treatment plan; integrated polypharmacy management; disease-disease / drug-disease conflict resolution; two-way safe referral valve; longitudinal monitoring rhythm; window of opportunity; patient education [7].
Denotation	HOW IS NOT a new treatment protocol, not a rigid protocol, not IT software, not an administrative management initiative — this is a clinical layer, operated by doctors and medical teams [8].
Operationalization	B.1: First consultation activates HOW. B.2: 4-phase plan. B.3: Necessary and sufficient conditions to maintain the window of opportunity. B.4: Patient role framework. B.5: Enabling conditions, guideline conflict resolution [8].

2.3. DATA-to-operate — Decision-Activating Data Layer

Aspect	Content
Identification	DATA-to-operate — Operational data layer for clinical decision activation [8]
Definition	A data set sufficient for action — not for storage. A longitudinal time-series data system designed to identify target organ damage, pathological cycles, trends, safety margins, windows of opportunity, and fracture points — then triggering corresponding decisions [9].
Connotation	Time-series data for each disease axis; action thresholds; trend dashboards for the Clinical Conductor; decision logs and audit trails; monitoring SLAs; patient compliance data; longitudinal imaging data (ultrasound, elastography, DECT) [9].
Denotation	DATA-to-operate IS NOT “big data”, not a typical EMR (EMR stores, DATA-to-operate activates), not collecting as much data as possible — but collecting the right data needed for decision-making. A single cross-sectional data point IS NOT DATA-to-operate [10].
Operationalization	B.1: Minimum paraclinical core. B.2: Data triggering phase transitions. B.3: Window time series. B.4: Compliance. B.5: Safety valve thresholds. C.1: mm² caliper ultrasound for crystal-free. C.2: eGFR time series. C.3: BNP/EF. C.4: Child–Pugh/Fibroscan [10].

3. Relationship between the three layers — no substitution, no trade-off

The three layers are neither three levels nor three choices. They are three structural components of the same architecture — without any layer, the other two cannot produce sustainable clinical outcomes in patients with complex chronic multimorbidity [11].

Combination	Status	Clinical Consequence
Strong WHAT + Weak HOW + Weak DATA	Knowing what to treat but unable to organize, no trend visibility	Fragmented care, lost windows of opportunity, increased events [11]
Strong WHAT + Strong HOW + Weak DATA	Organized but making decisions on single data snapshots	Trend blindness, delayed response, slow safety valve activation [12]
Full WHAT + HOW + DATA	Knowing, organized, visible trends, continuous adjustment	Crystal-free, delayed dialysis, reduced heart failure decompensation, cirrhosis re-compensation [12]

4. The three layers in the context of complex chronic multimorbidity

In mild-to-moderate single diseases, WHAT is often enough: one guideline, one doctor, one regimen. HOW and DATA-to-operate exist in an implicit form. When a patient concurrently carries 4–7 severe chronic diseases in a single debilitated body, the number of combinations of disease-disease, drug-disease, and goal-goal conflicts increases exponentially — far exceeding implicit processing capabilities [12]. Complex chronic multimorbidity mandates that all three layers be explicitly designed [12].

Implicit HOW becomes insufficient. Memory-based DATA becomes unsafe. This is a structural reason — not because single diseases are easier, but because the complexity level exceeds the threshold that implicit operations can safely handle [13].

5. Position in the document system

A.2 sits between A.1 (Theoretical EBM Framework) and A.3 (Global Gap Evidence), acting as a bridge: $A.1 points out the fracture point → A.2 defines the three layers → A.3 confirms with evidence → A.4–A.5 implement terminology$ [13]. Simultaneously, A.2 is the comprehension foundation for all of Part B (Operation) and Part C (Validation) [13].

6. Conclusion

WHAT maintains the role of treatment knowledge standards — inherited intact from international guidelines. HOW transforms knowledge into structured, role-assigned, and controlled actions. DATA-to-operate turns fragmented data into signals that trigger actions at the right time [14]. The separation and simultaneous integration of these three layers are mandatory architectural conditions for complex chronic multimorbidity care — the result of systematization from 18 years of integrated clinical practice at the Vien gut clinic [14].