Skip to main content

Junior Doctor Notes and Co-Signing: Authorship and Review

A supervised clinical note should identify who collected information, who assessed the patient, who authored the note and what the supervising doctor actually reviewed. A co-signature must relate to a specific document version and review event; it should not erase the junior doctor’s authorship or imply that the supervisor personally examined the patient when they did not. The required supervision and issuing authority depend on the person’s registration, role and applicable institutional rules.

By Bractis · Updated · 14 min read

Indian clinics and polyclinics coordinating junior doctors, duty doctors and consultants, including practices where assistants prepare parts of a visit record.

Set the supervision arrangement before designing the approval button

“Junior doctor” is a workplace label, not a complete description of professional eligibility or authority. An intern, a resident in a training programme and an independently registered duty doctor may work under different arrangements. Establish the actual registration, appointment and applicable supervision requirements instead of applying one software rule to all three.

Define the tasks involved: collecting history, entering measurements, assessing the patient, deciding treatment, drafting documents and issuing the final output. Some may be delegated within the appropriate role; others require the responsible clinician. A co-signing feature cannot create authority that the person does not otherwise have.

The NMC-hosted professional code provides registration and truthful-documentation context. The 23 August 2023 notification, published the next day, holds the 2023 conduct regulations in abeyance and adopts the 2002 framework. Those official texts were checked on 28 October 2026; they do not settle every appointment or training arrangement. This article proposes an attribution and review workflow, not a universal Indian co-signature rule or a replacement for programme-specific supervision requirements.

Source: NMC: Professional eligibility and truthful certificates or reports

Source: NMC: 23 August 2023 conduct-regulation amendment

Preserve the preparer, examiner, author and reviewer

A receptionist may type the patient’s stated complaint, a nurse may record a measurement, a duty doctor may assess the patient and a consultant may review a proposed plan. A final note that labels all of this “seen by consultant” can misrepresent the encounter even if the consultant later approves the document.

Keep the origin of information and the clinician’s accepted assessment understandable. This does not require printing every keystroke on the patient’s prescription. It requires the record and approval trail to support the claims made in the final document.

When the supervisor does examine the patient, record that encounter accurately. When the supervisor only reviews a record or discusses a case, describe that activity instead. A title or signature image should not silently change one kind of involvement into another.

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

Separate work performed from review performed
Role in the encounterEvidence to preserveMisleading shortcut to avoid
Information collectorWho obtained the history or measurement, when and from what sourceTreating every entry as the doctor’s direct observation
Assessing clinicianActual clinical assessment and decisionsReplacing the examiner with the senior doctor’s name
Document authorWho prepared the note and which content they enteredErasing authorship when a supervisor signs
Reviewing clinicianScope, version, decision and time of reviewA blanket approval that does not identify what was reviewed
Issuing clinicianAuthority and approval for the final patient-facing documentAssuming document review automatically authorises every associated order

Make the supervisor’s review scope explicit

A review can concern the whole assessment, a specific clinical question, a draft prescription or documentation completeness. These scopes are not interchangeable. Define what the supervisor is being asked to decide and ensure the relevant patient context and sources are available.

The reviewer should be able to accept, request clarification or record a differing opinion. A system that allows only “approve” encourages a misleading appearance of agreement. If the plan changes, preserve the final clinical decision and the reasoning needed to understand the change.

Do not treat a quick scroll, notification receipt or opened document as a completed clinical review. The meaningful event is the responsible clinician’s recorded decision within the actual supervision arrangement. Review time is an event, not proof of clinical quality by itself.

Attach approval to a version, especially when two people edit

In a fictional encounter, the consultant opens revision 3 at 11:10. The duty doctor adds a newly reported medicine at 11:12, creating revision 4. At 11:14 the consultant approves the screen they opened. The clinic must know whether that approval covers revision 3 or the updated record.

A reasonable workflow makes the change visible and requires the relevant reviewer to resolve it before claiming approval of the final version. The exact implementation can vary, but the evidence should not imply that the supervisor saw information that arrived after their review.

Check related artifacts separately. A revised clinical note may contain a new plan while the prescription PDF still contains the old instruction. The final review should identify the outputs within its scope rather than treating one approval icon as evidence that every document is consistent.

Worked review: a current note can coexist with an unresolved prescription

Fictional V-26 extends the revision example into a small polyclinic handover. The duty doctor is the examiner and author; the consultant provides record review and discussion without a personal examination. Assume the clinic has already established both clinicians’ eligibility and the applicable supervision arrangement. All times below are on the same day in IST. The example supplies no examination findings or medicine instructions: its purpose is to expose which document each decision actually covers.

The patient mentions an outside medicine while the consultant has the earlier note open. The author records that report in N4, preserving that it came from the patient and that the exact product remains unresolved. A new prescription draft is an object needing its own decision. Recording the medicine report faithfully does not establish that the product has been identified or that a revised prescription may be issued.

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

Fictional V-26: seven events across note and prescription versions
Time / eventObject and evidenceMeaning for the next person
11:10 · review openedConsultant opens note N3 and prescription draft P1Opening records is not approval
11:12 · new report recordedDuty doctor creates N4 with the attributed outside-medicine reportN3 does not contain the new information
11:14 · earlier note acceptedReview event explicitly refers to N3Historical approval; no claim that N4 or a prescription was accepted
11:18 · current note reviewedConsultant accepts N4 documentation after discussion; product confirmation still required for prescribingAcceptance has a stated limit; prescription approval remains open
11:22 · new prescription draftAuthor saves P2 as pending; P1 is supersededA saved draft is not an issued prescription
11:25 · follow-up requestedTask asks the responsible clinician to resolve the medicine question and decide P2Queue delivery alone is not accepted ownership
11:30 · handover acceptedCovering clinician accepts the outstanding assessment task; no P2 decision recorded yetOwner established; the clinical and issuing decisions remain unfinished

Source: HL7 FHIR R4: Provenance and version-specific targets

Translate “reviewed” into decisions about named questions

At the V-26 cutoff there are two note revisions, two prescription revisions and two recorded note-acceptance events. Only one note acceptance concerns the current note, and neither is a prescription approval. Reporting “two approvals, therefore the encounter is complete” would conceal the unresolved decision. These are object and event counts, not measures of supervision quality or a recommended completion target.

Use the scope matrix to prevent a narrow decision expanding as it passes from consultant to reception or the next shift. “N4 documentation accepted” has a different meaning from “all aspects of care approved”. The supervisor may accept that the note truthfully records an unresolved issue while still requiring information before deciding what to prescribe. The note must keep that uncertainty visible; an approval label cannot replace the actual decision.

The sequence is an original operational example. FHIR R4 Provenance provides a useful technical vocabulary for a target, participating agents and separate activity and recording times, with version information when needed to identify the target unambiguously. It does not decide Indian clinical authority, mandate this screen design or establish that Bractis implements the proposed behaviour.

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

V-26 scope at 11:30: four questions with different recorded states
QuestionEvidence at cutoffPermitted interpretation
Does N4 accurately record the reviewed discussion?Consultant’s limited acceptance at 11:18That documentation review is recorded; the unresolved medicine question remains in the note
Is P2 ready to issue?Product confirmation and responsible clinician’s decision pendingNo completed prescription approval is evidenced
Has the patient received a final instruction?No final instruction or delivery event recorded in this exampleDo not mark communication complete from note acceptance
Has a fitness certificate been approved?No certificate request or assessment forms part of this reviewThe co-signature supplies no fitness opinion

Source: HL7 FHIR R4: Provenance and version-specific targets

Record a decision that can be understood after the shift

Use concise review entries that identify the actual activity. “Reviewed the history and proposed plan in revision 4 after discussion with the duty doctor” describes more than a generic “approved”. Add whether a direct examination occurred only when it actually did.

The outline below is for an internal review event. It is not a liability disclaimer, and it cannot transfer all responsibility from one clinician to another through wording alone.

Keep unfinished review visible without making care disappear

When supervision is required, a pending approval should remain an owned clinical task. Identify who will review, how urgent clinical needs are escalated and what authorised alternatives exist if the supervisor is unavailable. This guide gives no universal response deadline because the clinical situation and supervision model determine it.

Do not let “awaiting co-signature” hide an already issued prescription, a patient who has left or an uncommunicated change in plan. Track those events separately. The patient-facing document must accurately reflect its authorisation state and should not pretend a future review has already happened.

An independently authorised clinician may have a different review arrangement from a trainee. Configure the workflow around the actual role; neither unnecessary blanket blocking nor automatic senior-name signing is a substitute for understanding the appointment and professional requirements.

A later co-signature must not rewrite when decisions were made

If a supervisor reviews a record after the consultation, preserve the actual review time. A later review can add information or an opinion, but it should not make the record look as though the supervisor approved the plan before the patient received it.

When the later review identifies a material problem, follow the appropriate clinical correction and communication process. Recording a disagreement in an internal comment is not sufficient if an affected patient or another clinician needs an updated instruction. Keep the corrective action and its outcome linked.

If the original author leaves the clinic, preserve their identity and unfinished work history. A replacement clinician can assume appropriate tasks through an accepted handover; the old signature and account should not be reassigned to make the queue look complete.

Hand over the unresolved decision without replacing the original author

A change of shift is where a precise review record can become a vague task such as “finish consultant approval”. In V-26, the incoming clinician needs the unresolved question, the available evidence and the documents affected. They should not have to guess whether they are being asked to authenticate another doctor’s examination, review a prescription or telephone the patient. Accepting the task establishes responsibility for taking it forward; it is not evidence that the review has already occurred.

The filled example below is an internal task record, not a clinical note or a form ready for signature. “No final instruction recorded” describes the evidence available at the cutoff, not proof that nobody spoke to the patient. If the patient reports an earlier verbal instruction, record who reportedly gave it, when and what was understood, and ask the responsible clinician to reconcile it. Do not retrospectively fill the delivery field from assumption.

Count reviewed encounters separately from approval clicks

Suppose ten fictional encounters require review. Seven have an accepted current version, two are awaiting clarification and one has an approval of a superseded draft. The seven current approvals and the one superseded approval give eight recorded approval events, while only seven encounters have a current completed review.

Report the denominator as encounters requiring the defined review, and show unresolved states. Do not infer supervision quality from a high click count or a low average delay alone. Examine whether the right person reviewed the relevant information and whether changes reached the patient-facing output.

A useful software demonstration includes a late medicine update, a reviewer disagreement and an absent supervisor. These situations reveal whether the system preserves truthful roles and task ownership better than a perfect one-click approval example.

Revision 3 was reviewed; revision 4 still needs a decision

In the fictional 11:10–11:14 sequence, a new medicine is added after the supervisor opens the draft. The review record must identify the version actually considered and resolve the changed information before claiming approval of the final output. The signature remains a record of an event, not a shortcut around the new clinical question.

Supervised Note Review Worksheet

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

Authority
Establish the actual registration, appointment and required supervision for each role.
Attribution
Identify who collected, examined, authored, reviewed and issued without collapsing their work.
Version
Show late changes and connect approval to the exact documents considered.
Follow-through
Assign pending reviews, corrections and patient communication to an accepted owner.

Questions doctors ask

Must every doctor called “junior” use the same co-signing rule?

No single rule can be inferred from that title. Establish registration, training or employment status and the applicable institutional requirements for the actual work.

Can a co-signed note say the consultant personally examined the patient?

Only if that is true. Record review, case discussion and direct examination are different activities and should be represented accurately.

What if the author edits the note after the supervisor opens it?

Make the changed information visible and identify which version was reviewed. Do not silently attach an earlier approval to a materially changed final document.

Can a later review be dated as though it happened during the visit?

No. Preserve the actual review event and any subsequent correction or communication. A later signature should not rewrite the chronology of care.

Is an approval count enough to measure completed supervision?

No. Count encounters with the required current review and show unresolved or superseded approvals separately. Multiple clicks can relate to the same encounter.

Can a consultant accept a note while the prescription remains pending?

Yes, a clearly limited documentation review can record that the note accurately represents an unresolved issue. It does not establish that the medicine question has been resolved or the prescription authorised. Name the reviewed note version, the remaining decision and its accepted owner; assess actual issuing authority under the clinic’s supervision arrangement.

How should a covering doctor finish a review started by someone else?

They should record their own involvement, the evidence and versions they considered, and the decision they actually made within their authority. Keep the original author and earlier reviewer events intact. A task handover does not permit borrowing the absent doctor’s signature or backdating the new review, and patient communication may need a separate follow-through step.

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.

  • NMC: Professional eligibility and truthful certificates or reports

    Official text amended through 8 October 2016; sections 1.1.3 and 7.7 provide broad eligibility and truthful-document context. Checked 28 October 2026. The attribution matrices and review methods are original; no universal co-signing rule is inferred.

  • NMC: 23 August 2023 conduct-regulation amendment

    Official notification published 24 August 2023 holds the 2023 conduct regulations in abeyance and adopts the 2002 framework. Checked through the official regulations index on 28 October 2026; this is not an exhaustive review of local or training-specific obligations.

  • HL7 FHIR R4: Provenance and version-specific targets

    Version 4.0.1 reference for targets, agents, activity times and recorded times, checked 28 October 2026. Used as technical context for traceable review; no implementation, conformance or Indian legal-authority claim.

Try the workflow
with Bractis.

Try a fictional note with different author and reviewer accounts, then add information during review and inspect which version is approved.

Request a clinic demo