A healthcare network designs a multi-agent care-coordination solution. Agents can draft discharge summaries, propose medication changes, and schedule follow-ups. Clinical leadership requires that any medication change recommendation be reviewed by a licensed clinician before it is written to the electronic health record (EHR). Which architectural control best satisfies this requirement?
Select an answer to reveal the explanation.
Short Explanation
B is correct—and this is classic human-in-the-loop design. High-impact actions (medication changes hitting the EHR) need an explicit approval gate in the workflow, not just polite prompt wording. The orchestration pauses, a clinician reviews, then the system continues with approval or override. That is how you set autonomy levels and HAX/Responsible AI controls for multi-agent systems. A is dangerous: full write access plus a prompt is not a control plane. C confuses sampling randomness with governance; temperature never replaces policy gates. D reduces surface area slightly but still leaves automated writes without a human control loop. When the exam talks HITL, think approval workflows, overrides, and edge-case handling wired into the architecture—not vibes in the system prompt.
Full Explanation
B is correct because multi-agent logical architecture must specify autonomy levels and human-AI experience controls. For medication changes, the appropriate pattern is a human-in-the-loop approval workflow: generate recommendations, pause the control loop, require clinician approval or override, then allow EHR write tools to execute. A is wrong because prompt-only guidance is not an enforceable permission boundary; tool authentication and scopes must prevent unapproved writes. C is wrong because temperature adjusts generation diversity, not compliance or clinical sign-off. D is wrong because consolidating agents does not create an approval gate and can concentrate privilege. Design principle: bind high-risk tools to post-approval execution paths and record the human decision in workflow state for audit.