BusinessLive · in the productSettings

LocumLink

Locum and visiting cover, cleared against the credentials and privileges you already hold.

Get LocumLink Open the appAvailable nowHow pricing works →

What it is

A locum says yes on a phone call, and the two questions nobody asks in that call are whether their registration is still live and whether this hospital has ever privileged them for the list they have been handed. So a shift here is not confirmed by being agreed: it is proposed, accepted, and then CLEARED — and clearing it means naming the registration it rests on and asking the privileging register about every procedure the shift involves. Both answers are written down, and a refused check is kept as a refused check. The registration comes off the hospital’s own credential file, which has its door here and in StaffDesk: recorded by one person, verified by another. What is left over is the ordinary bookkeeping cover needs: who can be engaged, the hours they have offered, what was agreed, and what they are being paid on.

Who uses it: Built for: Hospitals
Reads: Your staff records, the registrations on your credential file, the privileging register
Writes: Engagements, offers of cover, shifts, clearance attempts and what the gate answered, registrations on the credential file
Never: It keeps no second register of anybody.
Access: Only people whose role includes it — the clinic owner decides who
Your data: No PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

Register the person under PeopleThe Person list is drawn from your own staff records marked locum or visiting. Pick the Kind, a specialty, and a usual basis and rate together — a rate with no basis is refused.
Record what they have offered, or book straight to a shiftOffers takes the hours a locum said they can work; Use for a shift carries that window into Book a shift. A shift ends after it starts, and one person cannot be offered or booked twice across the same window.
Propose, then mark it acceptedPropose the shift puts it on the Cover list as proposed. Open the row and press They accepted once the locum has said yes.
Clear it against the credential file, and read the answerOn an accepted shift, name the Registration on file and list the Procedures on this shift. A registration is refused unless it is verified, active, belongs to this person and runs past the end of the shift; one you add here is recorded unverified until a second person presses I checked it on the register. Every procedure comes back privileged, not gated or refused, a refused check stays on the shift, and Confirm the shift is offered only once the clearance passed — this screen’s own word, written to nothing else.
Close it outShift worked completes a confirmed shift. Cancel asks why and keeps the reason on the row.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It keeps no second register of anybody.

It engages people your own staff records mark locum or visiting — the word is chosen when they are invited under Team or accepted in HireDesk — it names a registration from the credential file StaffDesk keeps, and it asks the same privileging gate the theatre list asks — a refusal is written into that register, where the superintendent already reads refusals, and kept on the shift as a refused attempt so the board can show it.

A clearance is refused if the registration is not this hospital’s, not that person’s, not verified and active, or runs out before the shift ends; a shift with a refused procedure cannot be cleared, and an uncleared shift cannot be confirmed.

Confirming is this app’s own word for its own effect: nothing is written to StaffDesk’s rota, which is a login’s shifts and not a locum’s hours.

Nobody can be offered or booked twice across the same hours.

It is not a marketplace: there is no outside directory, no ratings, and nobody beyond your own hospital sees anything.

And it pays nobody — the basis and the agreed rate are recorded so the argument does not happen later, and the money is payroll’s.

AI in LocumLink

AskQuestions about what is on screen — “What needs attention in LocumLink today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

LocumLink — Locums — Book locum cover, cleared against their registration and privileges — 01Locums — Book locum cover, cleared against their registration and privilegesCaptured from the running demo clinic

01Locums — Book locum cover, cleared against their registration and privilegesCaptured from the running demo clinic

1 of 1

Questions clinics ask

What does LocumLink do?

Locum and visiting cover, cleared against the credentials and privileges you already hold. A locum says yes on a phone call, and the two questions nobody asks in that call are whether their registration is still live and whether this hospital has ever privileged them for the list they have been handed. So a shift here is not confirmed by being agreed: it is proposed, accepted, and then CLEARED — and clearing it means naming the registration it rests on and asking the privileging register about every procedure the shift involves. Both answers are written down, and a refused check is kept as a refused check. The registration comes off the hospital’s own credential file, which has its door here and in StaffDesk: recorded by one person, verified by another. What is left over is the ordinary bookkeeping cover needs: who can be engaged, the hours they have offered, what was agreed, and what they are being paid on.

What data does LocumLink read and write?

LocumLink reads your staff records, the registrations on your credential file, the privileging register and writes engagements, offers of cover, shifts, clearance attempts and what the gate answered, registrations on the credential file. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.

What does LocumLink deliberately not do?

It keeps no second register of anybody. It engages people your own staff records mark locum or visiting — the word is chosen when they are invited under Team or accepted in HireDesk — it names a registration from the credential file StaffDesk keeps, and it asks the same privileging gate the theatre list asks — a refusal is written into that register, where the superintendent already reads refusals, and kept on the shift as a refused attempt so the board can show it. A clearance is refused if the registration is not this hospital’s, not that person’s, not verified and active, or runs out before the shift ends; a shift with a refused procedure cannot be cleared, and an uncleared shift cannot be confirmed. Confirming is this app’s own word for its own effect: nothing is written to StaffDesk’s rota, which is a login’s shifts and not a locum’s hours. Nobody can be offered or booked twice across the same hours. It is not a marketplace: there is no outside directory, no ratings, and nobody beyond your own hospital sees anything. And it pays nobody — the basis and the agreed rate are recorded so the argument does not happen later, and the money is payroll’s.

What happens to our data if we uninstall LocumLink?

Every record stays; only the workflow leaves.

Is LocumLink available today?

Yes — LocumLink is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see LocumLink running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Business

All 144 →