GNOSIS Health
Workflow brief · Referrals

The referral, from sent to seen.

The referral lifecycle, tracked in the record: what GNOSIS Health does at each stage, and what it means for the patient waiting. It works on the record, not the room.

Prepared for the NL Health Services innovation team · 2026
Independent record integrity, built for AWS Canada · St. John’s, NL
GNOSIS HealthIndependent record integrity
Workflow brief · Brief 3 of 3
Prepared for the NL Health Services innovation team

A referral is a diagnosis on pause. We make sure it arrives.

A referral is sent, and then it goes silent. Nobody owns the gap between “sent” and “booked,” and a patient can wait weeks for an appointment that never existed. In Newfoundland, the medical association reported exactly this: missed referrals, and referrals routed to the wrong provider. This brief tracks one referral, stage by stage, showing what GNOSIS does in the record and what it means for the patient. It works on the record, not the room.

Brief 1 · The chartBrief 2 · The handoffBrief 3 · Referrals
01 / Why referrals vanish

The record shows it was sent. Nothing watches whether it arrived.

A referral leaves the clinic and enters a gap no one owns. It can stall in an outbox, reach the wrong department, or simply go unacknowledged. The sending clinician assumes it is in progress; the patient assumes they will be called. Weeks later, a diagnosis is still on pause and nobody noticed.

What is sent

The outbound referral

It leaves CorCare and crosses to another service. The sending team's job feels done the moment they hit send.

What is silent

The missing acknowledgement

No confirmation comes back that it was received or booked, and no one is watching the silence.

What is lost

The misrouted referral

Sent to the wrong department or provider, it is quietly dropped, sometimes with a confidentiality breach along the way.

GNOSIS treats every referral as an open loop until it is confirmed, so a patient keeps their place in line instead of falling out of it.
02 / One referral, stage by stage

What the technology does, and what it means for the patient.

The same referral, read two ways. On the left, what GNOSIS is doing in the record. On the right, what it means in real life for the patient who is waiting.

Stage
In the record · the technology
In real life · the patient
Day 0Sent
GNOSIS logs the outbound referralIt records that the referral left, to whom, and starts an acknowledgement clock sized to that service's expected turnaround.
“You’ll hear from the specialist”The patient is told a referral is on its way, and goes home to wait.
Day 1Transmitted
Confirmed it actually left the systemGNOSIS checks the referral cleared the outbox and was transmitted, not stuck in a queue on the sending side.
Not lost before it startedThe most invisible failure, a referral that never left the building, is ruled out on day one.
Day 5Window opens
The acknowledgement window is checkedBy now the receiving service should have acknowledged or booked it. GNOSIS checks whether either has happened.
Still waiting, assuming it is movingThe patient has no way to know if anything is happening. Neither does the sending clinic, until now.
Day 12Silence
No acknowledgement, past threshold, flaggedThe clock has run out with no reply. GNOSIS raises a flag: referral sent, not acknowledged, aging, on the primary-care worklist.
The patient is not forgottenInstead of falling through the gap, they surface on a list a human will work, this week.
Day 12Followed up
The follow-up is loggedThe clinic re-sends or calls the service. GNOSIS records the follow-up against the same referral, keeping one continuous thread.
Back in the queue, on the recordThe chase is captured, so if it stalls again it will flag again, not disappear.
Day 20Booked
Acknowledged and booked, loop sealedThe service confirms and an appointment is booked. GNOSIS closes the loop and seals the full history: sent, chased, confirmed.
The patient has an appointmentThe diagnosis is no longer on pause. And there is a provable record that the referral was handled.
03 / The scope, stated plainly

We watch the referral. We do not run the specialty's queue.

GNOSIS makes sure no referral goes silent unnoticed. It does not book the appointment for the specialist and it does not jump the waitlist. It watches, and it flags what stalls.

What GNOSIS tracks

The full referral loop, in the record

  • That a referral was sent, and actually transmitted.
  • Whether it was acknowledged or booked within the expected window.
  • A referral aging past its threshold with no reply.
  • A referral acknowledged by the wrong department, a misroute.
  • A sealed history of sent, chased, and confirmed.
What GNOSIS does not claim

Honest limits, said out loud

  • It does not book the appointment or control the specialty's schedule.
  • It does not shorten the clinical wait; it makes sure a patient is in the line at all.
  • If a referral was never created in the record, there is nothing to track.
  • It flags; a human follows up. It never closes a loop on its own.
The lost referral is not hidden. It is sitting in the record marked “sent,” with nothing watching for the reply. That is the gap we close.
04 / The storylines

Three referral catches, step by step.

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.

MEDIUMReferrals

The referral that was never confirmed

Sent and then silent: never acknowledged, never booked, a lost patient nobody notices.

  1. 1Sent

    A referral leaves the clinic for a specialty service.

  2. 2Silent

    No acknowledgement returns from the destination.

    Sent day 0No reply day 12
  3. 3Cross-checked

    Tracked against an expected acknowledgement window.

  4. 4Flagged

    MEDIUM: sent, not acknowledged, aging past threshold.

  5. 5Reached

    Appears on the primary-care referral worklist.

  6. 6Caught

    Followed up and re-sent. Place kept. Sealed.

HIGHReferrals

The referral routed to the wrong provider

The failure Newfoundland reported: a referral acknowledged by the wrong department, with a confidentiality risk attached.

  1. 1Sent

    A referral goes out to a specialty service.

  2. 2Misrouted

    It is acknowledged by a department it was not meant for.

    Intended: service AReceived: service B
  3. 3Cross-checked

    Acknowledging party checked against the intended destination.

  4. 4Flagged

    HIGH: acknowledged by the wrong provider, possible misroute.

  5. 5Reached

    Surfaced to the sending clinic to correct.

  6. 6Caught

    Re-routed correctly, exposure contained. Sealed.

HIGHReferrals

The referral that never left the building

Marked sent on the clinician's side, but it stalled in a queue and was never transmitted.

  1. 1Created

    The clinician completes and sends the referral.

  2. 2Stuck

    It does not clear the outbound queue.

    Marked sentNot transmitted
  3. 3Cross-checked

    Sent status checked against transmission confirmation.

  4. 4Flagged

    HIGH: marked sent, never transmitted.

  5. 5Reached

    Flagged back to the clinic within a day.

  6. 6Caught

    Re-sent and confirmed. Sealed.

05 / On the screen

What the primary-care team sees.

Not a spreadsheet nobody maintains and not a second app. The referral worklist lives inside the EHR, built from the record, showing only the referrals that have stalled or misrouted.

Referrals · worklist
!Not acknowledgedday 12
!Wrong providermisroute
!Not transmittedstuck
✓Bookedconfirmed
✓Acknowledgedon time
Work the 3 flags · the rest are clean

Only the referrals that need a human.

GNOSIS does not ask anyone to police a list of everything. It surfaces the exceptions: the one that was never acknowledged, the one that reached the wrong provider, and the one that never actually transmitted. The team works three, not three hundred, and the confirmed ones are sealed and off the list.

06 / What it asks of the front line

Send the referral the way you always do.

Nothing changes at the point of sending. GNOSIS watches from there, and only speaks up when a referral stalls or misroutes, so a patient never quietly falls out of the line.