CrossCare

What CrossCare does

A group with more than one site moves patients between them constantly — to the branch with the cath lab, to the one with a bed, back to the one near home — and the record of that move is usually a phone call and a folder somebody carried. This is the clinical version of the stock transfer the product already does between branches: the sending doctor writes a handover, lists everything that travels with the patient, and sends it. The receiving branch accepts it by naming the clinician taking over, or declines it with a reason, and then ticks off each thing on the list as it arrives — including anything that did not. The arrival is not recorded until every line has been answered, which is what turns “the drug chart never came” from a conversation nobody had into a row somebody has to close. Nothing is copied: each line is a reference to a record that stays in the app that owns it.

How you actually use it

1. 1Work from the branch you are atThe filter reads coming to this branch or leaving this branch, and a session that has not chosen a facility is told so rather than shown somebody else’s work.
2. 2Prepare the transferFind the patient, choose the receiving branch, routine, urgent or emergency, why in a sentence and the handover summary; a transfer to the branch the patient is already in is refused.
3. 3List what travels with themAdd to the list names each thing — the drug chart, a film, an implant card, the valuables envelope — as a line; the record itself stays in the app that owns it, and what travels is the manifest.
4. 4Send, and let the far end answerSend puts it in front of the receiving branch, which presses Accept naming the clinician taking over or Decline with a reason; Cancel asks why and works from the sending end.
5. 5Tick every line before the arrivalThe receiving branch marks each line Here or Missing — Missing asks what happened to it — and Record the arrival stays disabled while any line is unacknowledged, the button reading how many are left; the same rule is a not-exists in the guarded update.

What it does not do

It is not a referral to another hospital: both branches must be facilities of your own organisation, and that is re-read against your own tables on every write rather than trusted from the request. The two ends are two branches, not two buttons: sending and cancelling are done signed in at the branch the patient leaves, accepting, ticking off and recording the arrival signed in at the branch receiving them, and a session at no branch can do neither — holding the receive permission at the sending desk does not let that desk receive its own patient. It moves no records — what travels is a list of what was handed over, and each entry points at a record that stays where it lives. Nothing is accepted that was not sent, and nobody arrives at a branch that has not agreed to take them. An acceptance names a clinician on your own active staff list, because “the hospital accepted” is not a person you can hand a patient to. A transfer cannot be sent with an empty list, its handover summary cannot be a blank line, and the arrival cannot be recorded while a single item is unacknowledged — saying something did not arrive is a first-class answer, and it needs a sentence. Declining and cancelling both need a reason.

Questions clinics ask