A hospital wants Microsoft Foundry to host a model that suggests clinical codes from chart text. That model must not be the system that files the chart. Which constraint fits?
Select an answer to reveal the explanation.
Short Explanation
You can host the coding model in Foundry and keep the chart filing tool out of its reach. Separation lets the model suggest a code while a separate tool handles the official chart. If the model can file the chart, its suggestion and the official record become one act.
Full Explanation
Microsoft Foundry is the right host for a model that suggests clinical codes from chart text. Filing the chart is a separate right, so keep it with a separate tool the model is not allowed to call. The model can propose a code without becoming the system that writes the chart. Giving the Foundry model the filing tool collapses the suggestion and official write into one unreviewed step, contrary to the hospital’s constraint. Skipping Foundry for a Copilot Studio chat that both invents the code and files the chart keeps both rights on one identity and abandons the specified model host. Fine-tuning on previously filed charts so the model itself writes the official chart trains the forbidden role into the model rather than separating it from filing. Exam caveat: separating tool rights is not the same as hiding the filing action in a longer instruction; if the tool is connected, the instruction is not the control. Practical check: list the tools available to the coding deployment, confirm the chart-filing tool is absent, and run a chart sample to verify that it produces a suggested code without updating the chart.