Capabilities / E · Scenario

E.4 Institutional programmes Active

Institution-level programmes such as disease registries, regional follow-up and departmental quality control, composed from D.3 and D.7. Graded by before-and-after comparison of intervention rate and closed-loop rate.

Evidence: none. No benchmark card lists this capability yet. No level is issued: methodology 0.1.0 sets no level thresholds. For scenario capabilities the state is derived from the D-domain capabilities they are composed of (the lowest among them); levels for E are issued only by signed L5 override.

Domain
E · Scenario
Evidence form
program
Veto constraints
—
Depends on
D.3 Disease registry quality controlD.7 Follow-up and care pathway audit
Required by
—
Internal task families
—
External anchors
—
Version
0.1.0 · 0.1.0

Definition in detail

Institution-level programmes such as registries, regional follow-up and departmental QC succeed when issues are found and closed, not only found.

Inputs a task gives

  • Baseline intervention and closed-loop rates
  • Workflow materials for the component capabilities D.3 and D.7
  • Definitions of when an issue counts as closed

Artifact required

The component artifacts defined by D.3 and D.7, and a scenario run record with issues raised, interventions, closures and indicator values before and after.

How it is graded

Graded by before-and-after scenario indicators: intervention rate and closed-loop rate, computed by program from the run record against the baseline. Levels L1 to L4 are to be derived by program from verified result records once their thresholds are set; methodology 0.1.0 sets none and issues no level. L5 (role candidate) is never derived: it requires written before-and-after evidence on the scenario indicators and external anchors pointing the same way, and is granted only by a signed level override in registry/level-overrides with evidence links and the signer named.

In scope

  • Registry QC and follow-up at institution scale
  • Closing issues as well as raising them

Out of scope

  • Scoring of each component artifact - graded under D.3 and D.7
  • Regulatory classification of a product built on the scenario - recorded in regulatory_context, not graded

Typical failures

Expected failure patterns; not measured rates.

Standards: std-medgauge-capability-framework

Benchmarks

No benchmark card lists this capability.

Grading references

No grading reference is mapped to this capability.

Levels by model and harness

No verified results yetLevels would be derived from site-verified result records; methodology 0.1.0 sets no level thresholds, so the level shows not issued.