Skip to main content

Locum Doctor Access: Onboarding, Expiry and Clinical Handover

Give a locum doctor an individual account with verified identity and relevant professional credentials, an agreed clinical scope, limited permissions and explicit start and end times. Plan the handover of results, drafts and patient queries before access expires. Ending the roster entry should not leave clinical work unowned, and removing a menu or account label is not evidence that an existing session can no longer access records.

By Bractis · Updated · 15 min read

Indian clinic owners arranging holiday cover, visiting doctors or short-term clinical sessions across one or more practice locations.

Separate professional eligibility, clinical scope and software access

A locum arrangement involves at least three decisions: whether the person’s identity and professional credentials are satisfactorily established, what work the clinic authorizes them to undertake, and which system actions they need. An account invitation cannot settle the first two decisions.

The Government of India’s NMR description identifies registration and qualification information and an aim of public access. That description does not prove that every practitioner record or search function is currently available. Use the relevant official register and State Medical Council process as appropriate, record what was checked and when, and resolve discrepancies. A name match or self-entered number alone is not full verification of identity, current status or the proposed scope.

Agree the locum’s duties in ordinary operational terms: consultation sessions, access to relevant records, prescribing within authorized scope, result review and follow-up responsibility. Do not assume that a professional credential grants every administrative or bulk-export permission in the clinic’s software.

Source: National Portal of India: National Medical Register description

Define the access needed for the actual assignment

Start with the clinic locations, patient work and dates covered. A doctor covering Saturday morning at one branch may not need records from every affiliated practice, billing configuration or staff administration. Ask what is required to provide the agreed care, then test the resulting permissions.

OWASP’s authorization guidance recommends least privilege and checking permission for each request. It is technical guidance, not clinical credentialing. For the clinic, this means an apparently restricted screen should be backed by actual restrictions on the records and actions the account can reach.

On a narrow screen, scroll the table horizontally to read all columns.

Decisions for a locum’s access scope
AreaQuestion to settleEvidence to retain
Clinic and patient scopeWhich location and care records are needed?Approved assignment and observed permitted/denied access
Clinical actionsWhat may the doctor document, approve or sign?Role scope and correct attribution in issued records
Administrative functionsAre user management, configuration or exports necessary?Explicit decision rather than inherited owner permissions
Time windowWhen does access start and end, in which timezone?Configured boundary and verification result
Continuing workWho owns results and queries after the session?Accepted handover and unresolved-task list

Source: OWASP: Authorization Cheat Sheet

Use the locum’s identity on notes and issued documents

Do not lend the owner’s login to make onboarding faster. Shared credentials obscure who read a chart, entered a note or approved a prescription. They also make offboarding difficult because changing the locum’s access may disrupt the owner’s account.

Check the displayed author and prescriber details in the final output, not only the profile page. A document template may retain the owner’s name or registration information even when the locum is signed in. The issued record should accurately reflect the responsible professional and any applicable review relationship.

Where supervision or co-signing is required by the actual arrangement, record those roles truthfully. Do not convert a pending draft into a signed document under the returning doctor’s name merely because the locum has left. The relevant clinician must perform and document the required review through the appropriate process.

Give a practical handover before the first patient

Explain the clinic’s record structure, emergency routes, referral contacts and how to find current medicines and unresolved results. A locum may be clinically experienced while unfamiliar with a particular EMR or local handover convention. The orientation should focus on finding and completing the actual work.

Use fictional records to practise saving a draft, issuing an approved document, correcting an entry and routing a pending task. Include the clinic’s downtime process. Do not make the first real consultation the only test of whether the account can perform the assigned role.

Identify who can resolve an access problem during the session. A clinician unable to see a necessary record needs an appropriate escalation route, not instructions to borrow reception credentials. Keep emergency and continuity arrangements separate from routine permission changes.

Test access expiry with a session that is already open

Record start and end times precisely, including the timezone. “End of Saturday” can mean different things to the roster, the server and a user who is still finishing documentation. Decide how late work is handled and who may approve an extension before that situation occurs.

In a fictional access test, leave an authorized session open across the configured end time. Then try an ordinary record request and a previously opened document link within the permitted testing scope. Confirm the actual outcome. Disappearance from a staff list does not establish that sessions, downloads or links have stopped working.

Any extension should be attributable and scoped, with a new end time and reason. Avoid changing a temporary account to permanent administrator status just to resolve one unfinished task. Record which work still needs access and whether another authorized clinician should take it over instead.

Transfer unfinished care before disabling the account

Prepare a list of outstanding work linked to patients and encounters: pending reports, unsigned drafts, promised calls and unresolved questions. Agree who will accept each item. Sending a list to a group without acceptance can leave everyone assuming someone else is responsible.

In a fictional handover there are five tasks: two laboratory results awaiting review, one unfinished note and two patient queries. The returning doctor accepts the results and queries, while the note’s author and clinical lead resolve the appropriate completion process. Five tasks assigned does not mean five tasks clinically completed.

The access end time and clinical responsibility transition should be coordinated, but one must not hide the other. If urgent information arrives after expiry, use the agreed clinical communication and covering route. Do not leave broad access open indefinitely as a substitute for an accepted handover.

Use a timed rehearsal with both permitted and excluded actions

L-8 is a fictional assignment at Branch A from 08:00 inclusive to 13:00 exclusive on 31 October 2026, in IST. The doctor may perform the approved clinical work at that branch but has no Branch B, user-administration or whole-clinic export permission. These are explicit exercise assumptions, not a default Bractis configuration or a universal locum role. Agree the real assignment before deciding what each test should allow.

The window corresponds to 02:30–07:30 UTC on the same date. Retain the date and timezone in the approval and compare them with the configured system boundary. A five-hour assignment is not the same as “five hours after whenever the doctor first logs in”. Test the rule actually configured, including whether any idle-session limit is a separate restriction.

The matrix contains two intended permitted actions and seven intended denials. It is an acceptance plan, not evidence that a product passed nine tests. Observe the result in fictional records, retain the account, resource and time used, and investigate any mismatch. A successful login alone cannot establish the scope; the relevant question is whether that account can perform that specific action.

OWASP distinguishes request-level authorization from authentication and calls for server-side session invalidation on expiry. That supports checking an already open session as well as a fresh sign-in. In L-8, a page already displayed before 13:00 may still contain previously received information; it is not proof of a new authorized read. Test a fresh request and distinguish protected document links from files already downloaded. The example does not claim that expiry retrieves local copies.

On a narrow screen, scroll the table horizontally to read all columns.

L-8 acceptance plan: expected outcomes for the explicitly agreed assignment
Time, ISTFictional actionExpected resultWhat to inspect
07:59Request a Branch A chart before the assignmentDenyClinical data is not released before the approved start
08:00Request an in-scope Branch A chartAllowActual record access, not just successful login
09:00Request a Branch B chartDenyLocation scope applies to the request
09:05Change another user’s roleDenyClinical privileges do not imply user administration
09:10Request a whole-clinic exportDenyBulk disclosure is outside this assignment
12:59:50Save in-scope draft D8AllowSaved version and locum authorship are attributable
13:00:01Make a new chart request from the open sessionDenyA previously open tab does not extend the window
13:00:02Request a protected document URL directlyDenyThis path enforces the agreed access boundary
13:00:03Submit an edit from the old D8 tabDenyNo silent write after expiry; recovery route is explained

Source: OWASP: Authorization Cheat Sheet

Source: OWASP: Session Management Cheat Sheet — session expiration

Five accepted responsibilities are not five completed clinical tasks

Keep L-8’s access rehearsal separate from its handover ledger. At 12:45, the returning doctor has accepted two result-review tasks and two patient queries. Draft D8 still has no accepted completion arrangement. That is four of five tasks with accepted ownership, or 80%, while all five remain unfinished. A message sent to the clinical lead about D8 is not acceptance until the lead has actually taken responsibility for resolving it.

At 13:10 the clinical lead accepts responsibility for coordinating D8’s completion with its author through the appropriate process. Ownership is now accounted for on all five items. The lead’s acceptance does not transform the draft into the lead’s own consultation, authorize a signature they did not provide or prove that the draft is complete. The existing author and the actual reviewer must remain distinguishable.

At the 14:00 checkpoint, one patient-query callback has a documented outcome under the responsible doctor’s plan. The other four task actions remain open. Therefore accepted ownership is 5/5, while documented task completion is 1/5. Those figures describe this fixed five-item ledger, not the quality of clinical care or a clinic performance benchmark. A new result arriving later should receive its own entry instead of being invisibly added to this denominator.

The practical handover should say what the receiving person has accepted: the question to answer, evidence available, current uncertainty and next required action. Clinical urgency determines the response; the invented times do not supply a permissible waiting period. A roster closure can coexist with open tasks, provided their actual ownership and care pathway remain explicit.

On a narrow screen, scroll the table horizontally to read all columns.

L-8 handover: ownership and completion at separate checkpoints
TaskAcceptance at 12:45Acceptance at 13:10Status at 14:00
Result R1 reviewReturning doctor acceptedSame doctor retains ownershipOpen; review outcome not yet recorded
Result R2 reviewReturning doctor acceptedSame doctor retains ownershipOpen; review outcome not yet recorded
Draft D8 completionNo accepted completion arrangementClinical lead accepts coordination with authorOpen; no finalization inferred
Patient query Q1Returning doctor acceptedSame doctor retains ownershipCompleted task action; callback outcome recorded
Patient query Q2Returning doctor acceptedSame doctor retains ownershipOpen; response still required

An extension needs a new boundary, not a rewritten exit time

Suppose the lead approves a separate L-8 extension from 13:20 inclusive to 13:40 exclusive to address D8. That adds twenty minutes, equivalent to 07:50–08:10 UTC. It does not erase the gap from 13:00 to 13:20 or authorize actions that were attempted during it. Preserve the original end time, the later approval, the permitted purpose and the new boundary.

Confirm that the system can express the intended scope. If it can only restore a broad clinic role, do not record the result as “D8-only access”. State that limitation and have the accountable lead choose an appropriate supported route, such as a different authorized completion process. A permission label should describe what the system enforces, not what staff hope the user will do.

The returning clinician must not issue D8 under their own name simply to remove it from the locum’s queue. Preserve what the locum recorded and document any actual review or subsequent assessment. If a later addendum is appropriate, it must identify its real author and time. Account administration cannot settle the clinical authorship question.

At the end of the extension, repeat the affected access checks and inspect the task’s real status. An approved extra window does not prove the task was completed within it. The filled record keeps the access result, the outstanding work and any previously downloaded copy as separate matters. This makes the next cover period easier to review without restoring every former privilege automatically.

Preserve authorship while addressing local copies

Deactivating an account should preserve attribution in historical records and audit history. Deleting the identity in a way that makes prior notes anonymous can damage the ability to reconstruct care. Confirm how the system represents a former clinician in exports and issued documents.

Address downloaded files, printed material and use of personal devices through the clinic’s agreed confidentiality and device process. Revoking server access cannot recall a file already copied elsewhere. Do not claim that a successful sign-out proves every copy has disappeared.

For recurring cover, review the assignment and access scope again rather than automatically restoring every previous privilege. The clinic, tasks and professional circumstances may have changed. A reusable onboarding record can reduce repeated administrative work while preserving a fresh decision about the actual assignment.

Review the cover period for ownership gaps

After the session, sample issued documents for correct identity and inspect the handover list for accepted owners and outcomes. Focus on mismatches that can affect care: a result assigned to an inactive user, an old prescriber footer or a draft incorrectly treated as finalized.

Record the access tests actually performed and the limitations. A successful test in one browser does not establish that every integration or cached download is revoked. Ask the vendor to demonstrate the relevant paths in the configured environment before relying on a broad expiry claim.

Use the findings to improve the next cover period’s preparation. The aim is clear professional responsibility and a workable end to access, not a larger checklist whose boxes can be completed without observing the workflow.

The account expires while five clinical tasks remain

A fictional locum has two pending results, one unfinished note and two patient queries. The clinic records who accepts each task and how the note will be completed, then verifies the agreed access boundary. The account’s expired status is not used to mark those five tasks complete, and historical authorship remains visible.

Locum Access and Handover Worksheet

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Eligibility and scope
Separate professional checks, authorized clinical work and software privileges.
Identity
Inspect authorship and prescriber details in a fictional issued document.
Expiry
Test the configured time boundary using an already open session and an extension scenario.
Handover
Assign and obtain acceptance for outstanding care while preserving the departing doctor’s record history.

Questions doctors ask

Does an accepted handover mean all of the locum’s work is complete?

No. Acceptance establishes who is responsible for the next action. Track result review, queries and draft completion separately, and preserve the actual author and reviewer. A task needs its own recorded outcome before it is treated as complete.

Can a later access extension cover an earlier period when the account had expired?

Do not backdate the access history. Record the original end time, later approval, new window and supported scope. Any attempt during the gap keeps its actual time and result; a later extension does not make it an authorized earlier action.

Can a locum use the clinic owner’s login for one shift?

Use an individual identity instead. Shared credentials obscure authorship, access history and offboarding, even for short cover.

Does a typed registration number establish the doctor’s credentials?

No. Verify the relevant identity and professional evidence through appropriate official routes and resolve discrepancies for the proposed assignment.

Does removing a doctor from the roster revoke an open EMR session?

Do not assume so. Test the actual access boundary, including already open sessions and relevant document paths, in the configured system.

Who handles results arriving after the locum leaves?

An identified clinician or covering service must accept that responsibility through the handover plan. Account expiry does not itself transfer clinical ownership.

Should the locum’s old notes lose their author when access is removed?

No. Preserve historical attribution and audit history while ending current access. Unfinished notes need a truthful completion or review process.

Sources and scope

Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Use a fictional one-shift doctor to discuss individual authorship, limited access, an open-session expiry test and an accepted clinical handover.

Request a clinic demo