Locum and visiting cover, cleared against the credentials and privileges you already hold.
In plain words: Book locum cover, cleared against their registration and privileges.
Business · No PHI · hospitalsA 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.
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.
Every app page carries this section. A listing with only benefits is an advertisement.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.
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.
Every record stays; only the workflow leaves.
Yes — LocumLink is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.
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.