GNOSIS Health · How a catch actually happens

01 / The ground truth

Start with what happens today.

A record is written into CorCare, and from that moment it is trusted. No independent layer compares one entry against the others, watches whether a result was ever acted on, or checks whether a loop was ever closed. We add exactly that layer, and nothing else.

Today

The record is written and trusted

Orders, results, medications, notes, and referrals live in CorCare. Each is trusted on its own, on the device already in the room.

→

What we add

An independent layer reads and cross-checks it

The same record is checked against itself and against clinical logic, in real time. Only the entries that contradict, or the loops left open, become a flag.

→

Where it shows up

On the screen the clinician is already on

A flag in the EHR panel and on the unit worklist. One review, one action, then it is sealed to a tamper-evident record.

The whole idea in one line: we do not read minds or rooms. We read the record, and the record is already full of catchable failures that nothing currently checks.

02 / The plumbing

Where the data comes from, and how the flag reaches the clinician.

No double entry and no separate program to open. We read the record through the standard interfaces CorCare already speaks, run the checks in Canada, and deliver the result back into the clinician's existing workflow.

Read

Orders and medications
Lab and imaging results, with status
Notes and problem lists
Referrals and their acknowledgements
Timestamps: who, what, when

Via HL7 / FHIR. No new data entry.

→

Cross-check

One entry against another
A result against the plan it should change
An order or referral against whether it was ever acted on
Certainty in a note against the evidence on file
Scored by severity and likelihood of harm

Runs in AWS Canada (ca-central-1), sealed.

→

Deliver

A flag in the EHR side panel
A worklist or task queue for the unit
A receipt that proves what happened, and when
Clinician reviews, acts, or signs
Nothing new to carry, nothing new to learn

Same device. Same login for the everyday flow.

CorCare · Patient chart ● GNOSIS Health connected

Results · review queue

1 GNOSIS flags

HIGH · OPEN LOOP

Critical result, not yet reviewed

Released to portal 14:32No clinician review on record

View · route to physician →

This is the whole answer to “how does it reach the clinician.”

Not an email, a pager, or another tab. A card in the panel beside the chart they are already reading, with the two facts that matter: a critical result went out, and no clinician has reviewed it. They open it, review, and act, before the patient is left alone with it.

03 / The scope, stated plainly

We work on the record, not the room.

The fair question a clinician will ask: if something was never charted, how can you possibly catch it? The honest answer sets our scope, and that scope is exactly where our credibility comes from. We never overclaim.

What GNOSIS catches

Already in the record, never cross-checked

A critical result that came back and was never reviewed before it reached the patient.
A referral sent that was never acknowledged or booked.
A test collected with no result returned past its expected turnaround.
A new result that should have changed the plan, while the order or medication continued unchanged.
A diagnosis documented as confirmed with no confirming study anywhere on file.

What GNOSIS does not claim

Honest limits, said out loud

It does not listen to the room and does not record or transcribe conversations.
It does not invent what belongs in a note. It only compares what is written against the rest of the record.
If a fact was never entered anywhere, no system can surface it, and we will not pretend otherwise.
It does not replace clinical judgment. It flags; a clinician decides and signs.

The failures hurting patients in Newfoundland right now are not hidden in the room. They are sitting in the record, uncaught. That is the gap we close.

04 / The scope of work

We cannot fix it all at once. We start with three places the record breaks.

Each is a real, documented failure with no independent check today, and none of them is a duplicate of an alert the EHR already runs.

Guard 01 · Handoff Integrity

The handoff

What the record holds but does not carry across a shift or a transfer: a pending critical result the receiving team never learns to chase, a diagnosis carried forward as certain with nothing on file to support it.

Guard 02 · Charting Integrity

The chart

Contradictions the record itself reveals: a new result that should change the plan while the order stands, a condition written as confirmed with no confirming study, a note that disagrees with the data it sits beside.

Guard 03 · Results & Referrals

Open loops

The loops the system leaves open: a critical result released with no clinician review on record, a referral sent and never confirmed, a specimen collected and never resulted. The exact failures Newfoundland has reported.

05 / The storylines

Six catches, step by step.

Two per guard. Each reads left to right: what happened, what the record showed, the flag it raised, who it reached, and the harm it prevented. Every one is caught from the record alone.

HIGHHandoff Integrity

The result that came back after the team changed

A test resulted overnight. The clinician who ordered it is off. Nobody owns it, and it sits unread.

1Ordered
Day team orders an urgent test before signing off.
2Resulted late
The result files at 03:10, after they have gone home.
Result 03:10Orderer off 23:00
3Cross-checked
Result criticality checked against whether anyone has acknowledged it.
4Flagged
HIGH: critical result returned, ordering clinician off, no acknowledgement.
5Reached
Routed to the covering team on the unit worklist.
6Caught
The covering physician acts on it hours sooner. Sealed.

MEDIUMHandoff Integrity

The diagnosis that hardened across the transfer

A working theory is carried forward as a confirmed diagnosis when the patient moves units, with nothing on file to support it.

1Presumptive
Admitting note documents a suspected condition.
2Transferred
On transfer, the problem list now reads it as confirmed.
Admit: suspectedTransfer: confirmed
3Cross-checked
Certainty in the note checked against any confirming study on file.
4Flagged
MEDIUM: documented as confirmed, no confirming result on record.
5Reached
Surfaced to the receiving team before rounds.
6Caught
Reset to presumptive. The workup continues instead of closing.

HIGHCharting Integrity

The result that should have changed the plan

A new critical result is on file, but the order it should have changed carries on unchanged.

1Order stands
A medication is running on an existing order.
2New result
A critical lab files that should prompt a change.
Critical result filedOrder unchanged
3Cross-checked
The result is checked against the active orders it bears on.
4Flagged
HIGH: new critical result, related order not reviewed.
5Reached
Appears in the prescriber's panel for review.
6Caught
The order is adjusted before the next administration. Sealed.

MEDIUMCharting Integrity

The certainty with nothing behind it

A condition is documented as confirmed, but no test was ever ordered or resulted to confirm it.

1Documented
A note records a condition as confirmed.
2No basis
No confirming order or result exists on file.
Charted: confirmedConfirming study: none
3Cross-checked
The claim in the note is checked against the orders and results.
4Flagged
MEDIUM: confirmed diagnosis, no supporting study on record.
5Reached
Surfaced to the author before the note is signed.
6Caught
Either the study is ordered or the wording is corrected. Sealed.

HIGHResults & Referrals

The critical result nobody opened

The failure Newfoundland reported: a serious result reaches the patient portal before any clinician has reviewed it.

1Resulted
A report with a critical finding is finalized.
2Released
It posts to the patient portal on the standard schedule.
On the patient's phoneNo review on record
3Cross-checked
Criticality checked against whether a clinician has reviewed it.
4Flagged
HIGH: critical result released, no clinician review on record.
5Reached
Routed to the responsible physician, top of the worklist.
6Caught
The physician calls first. The patient hears it from a person.

MEDIUMResults & Referrals

The referral that was never confirmed

A referral is sent and then goes silent: never acknowledged, never booked, a lost patient nobody notices.

1Sent
A referral leaves the clinic for a specialty service.
2Silent
No acknowledgement returns from the destination.
Sent day 0No reply day 12
3Cross-checked
Every referral tracked against an expected acknowledgement window.
4Flagged
MEDIUM: referral sent, not acknowledged, aging past threshold.
5Reached
Appears on the primary-care team's referral worklist.
6Caught
Followed up and re-sent. The patient keeps their place in line.

07 / Every promise, the workflow

Six promises. The same shape, six ways.

Each card on the site is a promise. Here is the workflow behind each: the clinician keeps their flow, GNOSIS reads the record, cross-checks it, flags only what matters, and seals the proof.

Referrals that arriveconfirmed · sealed

Send as normal→Watch for the acknowledgement→No reply in the window→Flag the worklist→Followed up · sealed

Results held for reviewphysician first

Result finalized→Criticality vs review status→Physician-first, top of worklist→Reviewed, then released→Timeline sealed

Protection for the frontlinerole-verified

Every action stamped: who / what / when→Written to a tamper-evident chain→Alter one entry, the chain breaks→Clinician can prove what they did

Works across the splitone record

Read CorCare + other systems + paper (one scan)→Normalized together→One sealed timeline across the fragments

Built for skeleton crewsminutes to learn

Cloud, no onsite server→Flag rides the existing EHR→One skill: tap to review→Useful the same shift

Zero added burdenin the flow

Reads passively→Checks run silently→Only a real divergence flags→One tap in the same screen

Two honest lines to keep in the provider version: for Results held, the portal hold itself is enforced by the EHR's release rules; GNOSIS decides which results those rules must catch and proves the review happened first. For Works across the split, digital sources are read automatically; paper needs one capture step to enter the sealed record.

How a catch actually happens.