Work the results Inbox: Practitioner vs Assigned to, routing, COPY and corrected results, Follow-up
Clear your results and letters with confidence — know which filter answers which question, route what isn't yours, read COPY and corrected results correctly, and use Follow-up as the safety net it is built to be.
Before you start
Results arrive automatically where a lab is connected and are matched to the patient by their identifiers, name and date of birth. Anything that could not be matched confidently waits in the Lab feed, not the Inbox — that is KB-019 — Pathology results not filing — what to check's territory. Reviewing an item records who read it and when, and can raise a recall from the same place.
Choose the right filter
Two filters narrow the Inbox, and they answer different questions:
| Filter | Shows | Use it when |
|---|---|---|
| Practitioner | Items for patients whose usual GP you are | Clearing your own patients' results |
| Assigned to | Items routed to you — the letter addressed to you, whoever the patient usually sees | You're a locum, registrar or covering |
A locum's referral coming back to the locum is exactly where the two differ: it's assigned to the locum, but the patient's practitioner is someone else. The unreviewed count at the top follows whatever filters are on, so it never claims work the list isn't showing.

Route an item
- Open the item's detail pane.
- Route it to a clinician, or back to the practice pool. Any item can be routed until it is actioned.
Every routing change is in the Audit log with the previous and new addressee. A scanned letter filed to the wrong doctor is fixed the same way (KB-047 — Scan and file paper letters, including the appliance's pre-filled suggestions).
Read COPY and corrected results correctly
- A result marked COPY was addressed to somebody else and copied to your practice. It is for information only; the addressee is responsible for actioning it.
- A corrected result supersedes the one it corrects. The withdrawn result is kept and marked — it is what was on file at the time — and the correction comes back to whoever reviewed the original. The patient's cumulative Results view shows only the amended result.
Use Follow-up
Follow-up lists results and correspondence nobody has actioned. The manual is blunt about why it exists: a result that arrives, is filed and is never looked at is the commonest serious failure in general practice. Make it part of the daily routine.
If you are not named on a restricted record, its rows are left out of the Inbox and Follow-up, and each screen says how many (KB-061 — Restrict a patient's record, and open one in an emergency).
If that didn't work
| What you see | What to do |
|---|---|
| A result is in the Lab feed but not on the patient | Open the Lab feed and assign it (KB-019 — Pathology results not filing — what to check) |
| An incoming letter with nothing to open | It could not be stored; the message is kept. Ask your administrator to check object storage. |
| Results have stopped arriving entirely | Don't wait — the manual lists this as a call-support situation. |
For a clinically urgent result you're waiting on right now, phone the laboratory.
Still stuck? Raise a ticket at support.curaeon.com.au or call 1300 XXX XXX. If your clinic can't see patients right now, call and choose option 1. Support is staffed Monday to Friday, 8:00–18:00 Sydney time; outside those hours a call or text to the same number is answered on a best-effort basis.
Related articles
- KB-019 — Pathology results not filing — what to check — Pathology results not filing — what to check
- KB-047 — Scan and file paper letters, including the appliance's pre-filled suggestions — Scan and file paper letters, including the appliance's pre-filled suggestions
- KB-051 — Run recalls: book from a recall, and why a recall stays open or comes back — Run recalls: book from a recall, and why a recall stays open or comes back
- KB-107 — Order a test, add copy-to recipients, and chase a result that never came back on the Requests screen — Order a test, add copy-to recipients, and chase a result that never came back on the Requests screen