Nookal AI Scribe: Where the Note Lands and Who Decides When It Goes
By The Kitt Team
The note exists. The AI drafted it from the session, captured the findings, covered the plan. Then it landed in the wrong case, or against the wrong practitioner, or in a queue attributed to nobody. Someone re-files it. That is the same admin task with an extra step upstream.
Filing is the part most people don’t see in a demo. The demo shows note generation, which is genuinely useful. It rarely shows where the note lands, who decides when it goes, or what happens when practitioner records do not match. That is not the practice management system’s fault. It is about how the documentation layer fits the structure Nookal already runs.
What a Nookal AI scribe is
A Nookal AI scribe is a documentation tool that runs alongside Nookal, takes the consultation or a dictation, drafts the clinical note, and connects to Nookal so the finished note can be filed against the right client. It is not a practice management system, does not touch billing or scheduling, and does not replace Nookal.
The phrase “integrates with Nookal” covers far too much ground. Reading a client list once is integration. Writing a finished note back into the right case against the right practitioner is a different product with the same sentence on the website. If you run Cliniko, the same questions apply.
Nookal’s structure is the part a scribe has to respect
Nookal is structured software. Appointments belong to clients, cases group episodes of care, practitioners are distinct records. A drafted note is not finished when it exists. It is finished when filed against the right appointment, case, and practitioner.
A tool that does not understand that structure hands back a note the clinician then has to place by hand. That is the admin the tool was bought to remove.
The difference between documentation tools is measurable. A 2025 randomised trial of 238 physicians across roughly 72,000 encounters found ambient AI scribes significantly improved burnout, task load and work exhaustion, but the time savings were tool-dependent: one tool cut time spent in the note by 9.5 per cent, while another showed no significant reduction at all. Source: Lukac PJ et al, published in NEJM AI, 2025. (These were US physicians, so it is category evidence rather than an allied health measurement.)
The tool has to know which appointment the session belongs to, which case it sits under, and which practitioner it is filed against. Someone has to have matched the practitioner records between the two systems before any of that works.
What moves between kitt and Nookal, and who starts it
The useful way to read any integration is record type by record type, because “two-way sync” hides which direction each thing actually travels.
| What | Which way it moves | Who starts it |
|---|---|---|
| Clients | Pulls from Nookal into kitt; pushing clients back to Nookal is an option a practice can switch on | The scheduled sync, or the practice if push-back is switched on |
| Clinical notes | Pulls from Nookal into kitt in bulk; a finished note goes back to Nookal one at a time | You, per note |
| Documents | Pulls in bulk; a finished document goes back one at a time, with duplicate-import protection | You, per document |
| Treatment plans | Drafted in kitt, sent across to Nookal | You |
| Cases | Pulls from Nookal into kitt so a note can be filed against the right episode of care; kitt mirrors the case rather than managing it, and Nookal stays the place cases live | The scheduled sync |
| Practitioners | Listed and matched between the two systems | You, once, during setup |
Source of truth is configurable per record type per practice. The default leaves Nookal authoritative across clients, notes, documents and cases. That is the right default, and kitt ships it that way. You can adjust it per record type, but the default does not need second-guessing.
Setting it up, and the first week
Connecting Nookal requires two things: your Nookal Company ID and your API key, both entered by the practice. Credentials are encrypted at rest. The API key is deliberately never kept in the browser, so you re-enter it rather than restore it.
After that, you match practitioners between the two systems through the practitioner mapping panel. The match tells the integration which record in each system belongs to the same person. Then you set source of truth per record type, or leave the default in place.
Sync runs on a schedule. You can also trigger a sync on demand, which jumps the queue. The screen shows connection status, sync statistics that refresh themselves, and a sync history you can filter. Failures are named rather than quietly dropped.
The integration is optional. kitt runs without it. You can trial documentation quality and daily workflow for a month before connecting anything to Nookal. When you are ready, both sides of your client’s care covers what moves in each direction.
What kitt does not do with Nookal
kitt is not a practice management system and does not touch billing or scheduling. Notes and documents do not push back to Nookal automatically or in bulk: push is per item, one at a time, and you start it. There is no webhook, no instant sync: the schedule runs periodically, with manual triggers on demand.
kitt mirrors the Nookal case so work can be filed against the right episode of care. It does not manage cases and does not create them. Nookal stays where cases live.
Nookal and Cliniko are the only two practice management systems kitt connects to.
FAQ
Does a Nookal AI scribe file the note against the right appointment?
kitt works from the Nookal appointment and case structure when a note is drafted against a client, and files the note against the client record. You review each note and send it yourself. The decision to file sits with the clinician, not the tool.
Do I need to move off Nookal to use an AI scribe?
No. kitt sits on top of Nookal and does not replace it. Nookal handles appointments, billing and case management; kitt handles documentation. Nookal stays in place and stays authoritative by default.
Can I try kitt before connecting it to Nookal?
Yes. The Nookal integration is optional and kitt runs as a documentation tool without it. You can trial drafting quality and workflow for a month, no credit card required, before connecting anything to Nookal. The integration can be added once you have decided it fits.
Who at the practice needs to set the Nookal connection up?
The person who holds the practice’s Nookal Company ID and API key. It is a one-time setup: enter credentials, match practitioners between the two systems, and set source of truth per record type or leave the default in place.
The short version
- The question is whether it files against the right appointment, case, and practitioner.
- Source of truth defaults to Nookal. That is the right call.
- Push back to Nookal is per note, per document, and you start it. No bulk write-back.
- The integration is optional. Trial kitt for a month before connecting anything.
Try kitt free for a month, no credit card required.