QiiQ Scribe

Ambient capture, speaker separation and structured note generation are the entire product, with a stated intention to expand into a wider clinical assistant. No services layer or platform business underneath.

The review gate is built into the workflow rather than described in prose. Notes carry explicit In Progress, Complete and Archive states, and the vendor states plainly that the note may be edited by the physician before it is marked as complete, so completion is a deliberate clinician action rather than a system event. That state machine is a clearer mechanism than most competitors offer at this size. Held at B because no acceptance rate, edit burden figure or confidence threshold is published.

More mechanical description than most small vendors offer, naming voice separation between physician and patient, background noise suppression tuned for the emergency department, and prompts refined for non linear workflows and clinical anomalies rather than generic clinical language. But nothing is measured: no accuracy figure, model card, named models or evaluation methodology was located.

Nothing identifies any party in the chain: no model or model family, no foundation model provider, no hosting arrangement and no sub processor list was located in two passes. The mechanical description is better than most small vendors offer, naming voice separation between physician and patient, background noise suppression tuned for the emergency department, and prompts refined for non linear workflows and clinical anomalies rather than generic clinical language, so a buyer can see what the system is doing without learning anything about what runs it or where.

Residency is the specific gap and it is not a technicality here. The vendor is Canadian, sells into Canadian emergency departments, and publishes a compliance claim referencing the United States privacy rule, which suggests the infrastructure and the posture may have been built for a different market. Some provincial statutes constrain where health information may be held or require notice when it leaves the province, so a buyer needs to know the answer before deployment rather than after. Ask where content is processed and stored, whether any third party model provider is invoked, and for a sub processor list with the jurisdiction of each party.

No study, controlled evaluation, accuracy benchmark, third party rating, named customer or deployment count was located. Time saving is claimed as hours per shift without denominator or method. App store presence across iOS and Android shows an actively maintained product with a visible release history, which is a modest reliability signal rather than evidence of benefit.

The only statement located is that the product meets the United States health privacy standard, which is a compliance assertion rather than a data lifecycle. No retention schedule for audio or transcripts, no de identification practice and no statement on whether customer content trains models was found.

One thing about that assertion is worth flagging on its own, because it suggests the compliance material may not have been written for the market being served. This is a Canadian vendor whose product is built for Canadian emergency departments. The United States rule is not what governs a Canadian hospital's health information. Provincial health information statutes do, and they differ meaningfully between provinces on consent, custodianship and where information may be held. A Canadian buyer reading this page is being told the vendor meets a standard that does not apply to them, and is told nothing about the one that does.

That may reflect United States ambitions or a template, and either way the practical instruction is the same: establish which framework the vendor actually operates under and which provincial statute governs the deployment, rather than reading the published claim as an answer.

The capture setting makes the missing retention schedule more pointed than average. Emergency departments record patients who are intoxicated, confused, in acute distress or unconscious, and psychiatric presentations are documented in the same system as everything else. Nothing published states how long that audio persists, whether it is deleted after the note is produced, or whether consent is addressed at all where it cannot be obtained.

Ask for the retention schedule, the training position, and the governing privacy framework in writing.

Graded down for a jurisdictional gap rather than an absence. The vendor states it meets the HIPAA standard, but QiiQ is a British Columbia company whose stated beachhead is the emergency department and whose natural market is Canadian hospitals, and no claim was located for PIPEDA, provincial health information legislation or British Columbia's own privacy statute.

Citing only the United States regime is an odd position for a Canadian vendor selling into Canadian care settings, and a Canadian buyer should establish the domestic compliance position directly rather than reading HIPAA as a proxy for it.

No named or dated attestation, no report of either type, no penetration testing statement and no trust centre were located.

The distribution model is what makes the absence consequential here, and it is the sharpest version of a pattern this lane has now seen several times. The product is downloaded directly by an individual physician, with no credit card required, a free first month, and marketing that emphasises no hassle for the technology team and starting with zero delay. Nothing in that path involves the hospital.

So there is no procurement review, no privacy impact assessment, and no institutional security assessment anywhere between the vendor and a recording being made in an emergency department. The physician carries the professional obligation and has neither the tools nor the mandate to assess a vendor's controls. The hospital carries the custodial obligation for the health information and may not know the product is in use.

That is a real gap rather than a theoretical one, because emergency medicine is precisely where a physician might reasonably adopt a tool on their own initiative to survive a shift.

The vendor is small and this grade records what a counterparty can verify rather than a judgement that controls are absent. But the usual proportionality argument, that a small vendor selling to sophisticated buyers can defer certification while procurement asks the questions directly, does not apply when the model is designed so that no procurement happens at all. Publishing becomes the only mechanism.

Ask what external testing has been performed, what is held and where, and whether the vendor has completed a privacy impact assessment for any Canadian health authority.

No clearance claimed and none required for ambient documentation. No device pathway attaches in either the Canadian or United States framework to a note the physician reviews and edits before use.

The scribe itself is narrow and that is worth recording as a positive. No coding engine, no risk adjustment scoring, no decision support layer, no patient facing component and no order generation were located in it. The vendor also describes speaker separation, distinguishing the physician's voice from the patient's, and states the note may be edited before use, which places the review gate where it belongs.

What governs in the Canadian setting is professional and medico legal rather than regulatory. Emergency department documentation is the subject of sustained attention from the national medical protective body, whose published analysis of medico legal cases identifies documentation deficiencies as a recurring factor in emergency medicine claims. So the standard an emergency physician's note is held to is set by the profession and tested in claims and college complaints, not by a device regulator. A tool that changes how those notes are produced sits inside that frame.

One item to watch. The vendor markets a further product described as an assistant that responds to commands, positioned as a departmental upgrade beyond the scribe, with capabilities the vendor states it intends to expand. Assistants that act rather than record move toward different territory, and this record assesses the scribe. Ask what the assistant does before it is adopted, rather than assuming the scribe's position carries across.

Markets appear to be Canada with the application also listed elsewhere.

This record differs from most of the category in a way that makes it worse rather than better, and the distinction is worth drawing carefully.

Most vendors here publish nothing about accent or dialect performance. This one makes the claim. Its material states the product handles most languages, dialects and accents, and is unhindered by background noise. No evaluation, methodology, language list or subgroup data accompanies it. Alongside the claim the vendor invites the reader to see for themselves.

A claim without evidence is a stronger call on this axis than silence, because silence leaves a buyer to ask while a claim invites them to stop asking.

The invitation to verify personally is the part that most needs answering, because it sounds reasonable and cannot work. An individual clinician trying the product across their own encounters can establish whether it works for them, with their voice, in their department, with the patients they happened to see. It cannot detect the failure this axis exists to surface, because that failure is distributional. A system performing well on average and materially worse for one group of speakers looks fine to almost every individual tester, and the clinicians who would notice are those whose patients are affected, who are the least likely to be running the evaluation.

The setting makes it sharper still. Emergency departments serve unscheduled populations with the widest range of language, intoxication, distress and acuity of any care setting, which is the hardest acoustic and linguistic environment a speech model faces, and the one where a degraded transcript is least likely to be caught by the patient.

Ask for the evaluation behind the claim.

The band is reached through the regime rather than through the vendor, and on this record that distinction is unusually stark. Canadian provincial health information legislation gives the individual an enforceable right to have inaccurate information corrected, with a regulator behind it, and the custodian hospital carries the obligation regardless of what its supplier publishes.

So a patient recorded in a Canadian emergency department has a mechanism, and it does not depend on this vendor offering one. What the vendor publishes is a compliance claim pointing at the wrong regime entirely. This is a Canadian company selling into Canadian emergency departments, and the only privacy statement located is that the product meets the United States health privacy standard, which does not govern a Canadian hospital's health information.

Provincial statutes do, and they differ meaningfully between provinces on consent, custodianship and where information may be held. A Canadian buyer reading that page is being told the vendor meets a standard that does not apply to them and nothing about the one that does, which also leaves the cross border question open: if the posture was built for the United States rule, a buyer should establish where content actually sits. The setting sharpens everything above.

Emergency departments record patients who are intoxicated, confused, in acute distress or unconscious, and nothing published addresses consent where it cannot be obtained. No accuracy figure, warranty, indemnity or remediation commitment was located. Ask which framework governs, which province's statute applies, and where the data is held.

The default workflow is transfer: notes are viewed in the web application and copied into the record. EMR integration exists but is offered on request rather than shipped, with the vendor inviting interested buyers to make contact, which means integration is bespoke and its depth is unknowable in advance.

The pitch that a clinician can push notes into the record without bothering the IT department is appealing for a physician group with no informatics support, and it is also the description of a workflow that bypasses the usual integration governance.

No hosting region, residency option or subprocessor detail was located, and nothing establishes which model service processes the encounter.

The earlier assessment identified why that is a specific gap rather than a generic one, and it stands. This is a Canadian vendor whose buyers face provincial residency expectations that differ by province, and several provinces expect health information about their residents to be held in country or impose conditions on cross border transfer. A vendor serving those buyers who does not state where data sits has left them unable to answer the first question their own privacy office will ask.

One further fact from the second pass changes how the integration picture should be read. Record system integration is not a delivered capability. The vendor invites interested parties to get in touch about it, which places it somewhere between a roadmap and a bespoke engagement. So for a clinician downloading the application today, output leaves the product by hand.

That matters beyond convenience. Where notes are moved manually, the vendor's environment holds the only copy of the encounter for whatever interval elapses before transfer, and no institutional system has visibility of what was captured. It also means the deployment sits outside hospital information technology entirely, since the vendor markets that there is no hassle for the technology team and that a clinician can start with zero delay.

That is a real adoption advantage and it means the hospital whose patients are being recorded may not know the product is in use.

Ask for the hosting region and whether it can be pinned per province, the subprocessor list, the model provider, and what integration actually exists today.

Partial. A first month free with no credit card is offered and stated plainly, and team discounts are advertised, but no rate card, tier structure or per clinician figure was located and team pricing requires contact. A buyer knows the trial terms and nothing about the cost.

Deliberately narrow and genuinely specialised, the same shape as Sayvant in the same specialty. The emergency department differs from outpatient care in ways this product addresses directly: acoustic clutter, and a non linear workflow where a physician holds several patients open at once, is interrupted, and returns to encounters out of order, which is why the note state machine matters more here than elsewhere.

Note structure covers history of present illness, review of systems, exam and assessment and plan. The stated roadmap runs from the emergency department to the wider hospital and then outpatient, so current coverage is one setting done properly rather than many done thinly.