Legal document

AI Clinical Safety Statement.

How Miraa should be used safely as a clinician-reviewed AI documentation and workflow assistant.

m
Miraa Team
Effective 4 August 2026
2 min read Australian law
On this page

Key points

  • AI output can be wrong, incomplete, duplicated, unsupported, or overly confident.
  • A qualified clinician remains responsible for the final clinical record and any patient-facing or third-party communication.
  • Miraa must not be used as an autonomous diagnosis, triage, prescribing, emergency, or treatment decision system.
Section 01

Human review is mandatory

Miraa generates assistive drafts from available source material. A qualified clinician must review, edit, and approve the final output before it is relied on, filed, exported, prescribed from, sent to a patient, sent to another provider, or copied into an external system.

Clinicians should compare generated output against the consultation, patient record, medication list, investigation results, and clinical context. Any unsupported, unsafe, ambiguous, or irrelevant output must be corrected or removed.

Clinician review before an external send is not waivable and is enforced by the product, not merely recommended.

Section 02

Known AI limitations

AI and transcription systems may misunderstand speech, misattribute speakers, omit clinically relevant detail, infer information not present in the source, duplicate content, summarise incorrectly, or produce text that sounds plausible but is inaccurate.

Miraa may not detect every safety issue, missing follow-up, medication risk, billing error, or contradiction. Safety flags are prompts for review, not clinical determinations.

Section 03

Prohibited high-risk use

Miraa must not be used as the sole basis for diagnosis, triage, emergency escalation, treatment decisions, prescribing, medication reconciliation, billing claims, patient instructions, or legal certification.

Miraa must not be used where a clinician cannot review the source information and final output before use.

Section 04

Regulatory positioning

Miraa is intended as a clinician-reviewed documentation and workflow support tool. Its regulatory status can depend on intended purpose, deployed features, claims, configuration, and jurisdiction. Clinics should obtain their own compliance advice before using Miraa for regulated or high-risk workflows.

Miraa does not claim to replace a regulated clinical decision system, clinician judgement, or required professional review.

Section 05

Safe deployment expectations

Before rollout, clinics should define approved use cases, patient notice language, consent handling, staff training, review requirements, escalation pathways, template governance, audit review, and downtime procedures.

Clinics should start with lower-risk workflows, monitor output quality, document incidents or near misses, and restrict access where staff have not been trained.