Getting started

1. Complete the QiXMind intake

Start at console.orchintel.com/signup/qixmind. Choose Mental Health or Youth Mental Health, your country and, in Australia, your state or territory. The state is required because mandatory reporting and mental health law differ by state. The intake sets up your default profile for your clinical lead to review: safety gates, consent model, de-identification level, follow-up rule and the jurisdiction notices clinicians will see.

2. Check the profile

Open Profile and gates in QiXMind. It shows the care setting, clinical region, consent model, the safety gates that run on every output, the follow-up rule and the notices recorded in receipts. The care setting comes from the intake and cannot be switched inside the workspace. Sign-off is checked against the profile your organisation was provisioned with. A different care setting needs its own intake.

3. Run a safety review

Open Safety review, paste notes, a transcript or a referral, and generate. Names and common identifiers are pseudonymised before text is sent to the model. Pseudonymisation is not complete de-identification, and its accuracy on mental health notes has not been measured, so do not paste details you would not send to an external processor. The draft covers presenting concern, risk signals, protective factors, escalation and handover, follow-up and a review checklist. Drafts have not been clinically evaluated, so review every draft against the source. The draft is not designed to diagnose and does not assign a risk level. If the model declines to write a draft or returns an empty one, the output is held and cannot be signed off.

4. Acknowledge fired gates

The gates check the model's output, not the text you entered. They look for specific wording and can miss risk that is worded differently. If a gate fires, an acknowledgement item appears for it. In Australia the item carries the reporting or mental health law summary for your service's configured state or territory. Every fired gate must be ticked before sign-off. If the gate check could not run, the output is held and cannot be signed off.

5. Record the session and sign off

Before signing off you can add an optional pseudonymous episode reference (your service's own code, never a name, NHI or Medicare number), the care event, whether AI use was disclosed to the patient, and the consent record. Choose the role you are signing as and select Mark as reviewed. The receipt records the role you selected, never your name. The console keeps your account identifier with the sign-off for accountability.

6. Download the receipt

Select Download session receipt. The receipt is signed and holds hashes, ids, roles and times only. Anyone can check it offline for alteration since it was signed:

pip install ioa-core
curl -o qixmind-pubkey.pem https://orchintel.com/.well-known/qixmind-pubkey.pem
ioa verify qixmind-receipt-<id>.json qixmind-pubkey.pem

7. Confirm the follow-up

If a gate escalated, a follow-up is due, within 24 hours by default. The follow-up deadline tracks a recorded obligation. Urgent concerns require action under your service's immediate-response protocol. Confirm it on the Follow-ups page once it is done. When the follow-up status changes, a new receipt can be issued that names the one it supersedes. See Follow-up obligations.