Who is responsible when AI drafts a clinical note?
AI does not take over clinical responsibility. An authorized clinician remains responsible for clinical judgment and approval within the institution's workflow. Other legal, contractual, data, and security duties depend on each party's role and the deployment.
Put the evidence in context
Review the intended task, source information, human checkpoints and observed results together. A benchmark or sandbox result has a defined scope; it does not establish suitability, approval or performance for every institution.
Read the full explanationCare Workspace connects healthcare work such as appointments, reviewed reporting and follow-up. Micromeet Cowork supports team work with digital employees and reusable Skills, including meeting summaries, decisions and task handoffs.
Read the full explanationAI can prepare, structure, check, and route a draft, but it should not become an approved clinical note until the institution's authorized clinician has had a meaningful opportunity to review and change it. The institution should define who may approve each type of note, what information the reviewer sees, and when additional review or escalation is required.
This does not mean the software vendor has no responsibilities. The institution, vendor, and any subprocessors may each carry separate duties for system performance, data handling, security, instructions, and incident response under applicable law and contract. The exact allocation of legal liability is jurisdiction- and fact-specific. A governed workflow should distinguish drafts from approved records and preserve the review evidence required by the institution; the events recorded, their integrity, and retention period must be verified for the actual deployment.