Assess whether the system is high-risk under the EU AI Act after a denied
August 31, 2026
SITUATION In a hospital deploying a sepsis-risk model, post-deployment drift report the owner never signed is the evidence after a denied applicant requesting the principal reasons. Model-risk officer has to pick Policy or governance breach or Model defect for this AI Governance Bias and Training Data close using post-deployment drift report the owner never signed.
DECISION Model-risk officer in a hospital deploying a sepsis-risk model must choose Policy or governance breach / Model defect / Dual failure / Hold for the missing fact using post-deployment drift report the owner never signed after a denied applicant requesting the principal reasons.
HYPOTHESES TO TEST 1. A denied applicant requesting the principal reasons is noise around an already-controlled Bias and Training Data process in a hospital deploying a sepsis-risk model, given post-deployment drift report the owner never signed. 2. A denied applicant requesting the principal reasons is the event in post-deployment drift report the owner never signed that forces Policy or governance breach for model-risk officer under AI Governance. 3. Post-deployment drift report the owner never signed shows a one-file miss after a denied applicant requesting the principal reasons, not a Bias and Training Data program failure. 4. Post-deployment drift report the owner never signed cannot decide the system is high-risk yet after a denied applicant requesting the principal reasons; hold is the only AI Governance close a hospital deploying a sepsis-risk model can defend.
ANALYSIS REQUIRED 1. Reproduce the incident row in post-deployment drift report the owner never signed and say whether it ever touched production data. 2. Split policy-or-governance failure from a model defect using prompts, outputs, and human edits in post-deployment drift report the owner never signed. 3. Reproduce the incident row in post-deployment drift report the owner never signed and say whether it ever touched production data. 4. For this AI Governance Bias and Training Data file, read post-deployment drift report the owner never signed against a denied applicant requesting the principal reasons and write the one fact that would move the system is high-risk for model-risk officer.
RECOMMENDATION Choose Policy or governance breach / Model defect / Dual failure / Hold for the missing fact on this AI Governance / Bias and Training Data packet (post-deployment drift report the owner never signed after a denied applicant requesting the principal reasons). The follow-on Bias and Training Data action is what model-risk officer does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line AI Governance option on the system is high-risk, then the evidence in post-deployment drift report the owner never signed, then the action for model-risk officer - Hypothesis scorecard against post-deployment drift report the owner never signed: supported / rejected / untestable - Named option among Policy or governance breach, Model defect, Dual failure and the fact that kills the others - Owner and next date for model-risk officer in a hospital deploying a sepsis-risk model
Explore more
More AI Governance prompts
- Assess whether the board has been accurately briefed (5372dd)
- Assess whether deprecation of a legacy scorecard creates a governance gap
- Assess whether human review is real or a rubber stamp (6e9631)
- Assess whether the vendor can be used in a regulated process (2ab145)
- Assess whether a generative-AI incident is a policy breach or a model defect
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

