Shared Family Phone Numbers: Keep Each Patient Record Separate
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
A teleconsultation record should establish who is involved, how the consultation took place, the applicable consent evidence, the information available to the doctor and the clinical outcome. The doctor decides whether remote assessment is appropriate. Build the workflow around those decisions and any unfinished work, not around whether a booking was paid or a video call ended.
For Indian registered medical practitioners and clinic owners setting up teleconsultation documentation and reception handovers.
A video link solves a connection problem. It does not automatically establish patient identity, the purpose of the visit, access to relevant records, an appropriate clinical assessment or a usable plan afterwards. Those elements need to remain understandable even if the platform changes.
India’s Telemedicine Practice Guidelines of 25 March 2020 address identity, mode, consent and information needed for assessment in their stated RMP scope. Sections 3.3–3.5 leave suitability and information sufficiency to the doctor; a booking platform cannot make those judgments from connection status.
Use the official text and current applicable requirements when approving the clinical process. The workflow below explains what a clinic needs to observe and record in its software; it does not replace the guideline’s scope, prescribing provisions or professional judgment.
The separate NMC notification dated 23 August 2023 held the 2023 professional-conduct regulations in abeyance and made the 2002 regulations effective. Both that notification and the 2020 guidance were checked on 28 October 2026. Avoid mixing wording from the suspended 2023 publication into an unlabeled checklist of current requirements.
Source: MoHFW: Telemedicine Practice Guidelines, 25 March 2020
Source: NMC: professional-conduct amendment dated 23 August 2023
A relative may book, pay and join the call using the same phone that appears on several family records. These actions do not make the relative the patient. Confirm the chart and identify the participants before allowing documents or clinical notes to attach automatically to the booking contact.
Record relevant caregiver involvement without erasing the patient’s identity or preferred communication arrangement. If the person joining differs from the person expected, pause the administrative assumption and resolve it through the clinic’s process. A convenient auto-match is not evidence of correct identity.
The doctor’s identity and encounter should also remain clear. In a group practice, a link generated under one doctor’s schedule may later be handled by another clinician. Inspect which prescriber and reviewer appear in the note, document and patient-facing summary after that change.
A checkbox labelled “consent” is weak evidence if the clinic cannot explain what it records. Capture the context required by the approved process: who initiated the consultation, who participated, the mode and how the relevant consent was obtained or documented.
Keep consent for the consultation distinct from other choices that may arise. Recording audio, sharing a document with another person or sending promotional messages are separate activities; one generic booking checkbox should not silently stand for all of them. Determine the applicable process for each activity before enabling it.
When reviewing the software, ask to retrieve the actual evidence associated with a fictional encounter. Can staff distinguish a patient-initiated request from a caregiver arrangement? Can a doctor see what was recorded before starting? Can a correction to an administrative error be traced without making the record appear to have been completed earlier?
Section 3.4 distinguishes patient initiation, for which consent is implied, from initiation by a caregiver, health worker or RMP, for which explicit patient consent is needed. It permits several ways of expressing explicit consent, including an oral statement, which the RMP records in the patient record.
In fictional encounter TC-62, an adult patient’s daughter requests the visit and pays using her phone. The patient is present when the doctor joins. A useful record separates the initiator, the patient, the people present and the consent evidence. The payment receipt establishes none of the latter facts. This example assumes an adult patient able to participate; it is not a substitute for assessing another representation or capacity situation.
For TC-62, the doctor records at 10:02 that the patient expressed agreement to the teleconsultation orally, in the language used for the discussion. The record identifies the doctor and encounter. It should describe the actual interaction, not insert a prewritten declaration that nobody heard. Nor does this event document permission to record the whole call, add the daughter to future communications or send marketing messages.
If the patient is absent, the daughter’s knowledge of a booking reference should not settle whether she can represent the patient. The doctor needs to establish the applicable caregiver circumstances. Reception can collect and route the relevant information without promising that the consultation will proceed.
Source: MoHFW: Telemedicine Practice Guidelines, 25 March 2020
Continue the fictional TC-62 case. The uploaded laboratory document has only one of two pages. The doctor starts on video; the connection then drops and a telephone conversation resumes. A platform that stores only the original booking mode would call the entire encounter “video”, although the doctor’s access to information changed.
These invented times demonstrate event order, not a response-time standard or a clinical waiting recommendation. At each change, record the doctor’s decision about what can be done with the available information. Staff should not automatically change the clinical outcome because the replacement call connected or payment settled.
On a narrow screen, scroll the table horizontally to read all columns.
| Event | Evidence to retain | What the event does not establish |
|---|---|---|
| 09:55 — one report page received | Source, patient match, page count and the missing-page request. | That the full investigation was available to the doctor. |
| 10:02 — patient and daughter join video | Participants, actual clinician, initiation circumstances and recorded consent evidence. | That every later activity is covered by a booking checkbox. |
| 10:07 — video disconnects | Actual interruption, information obtained so far and doctor’s next instruction. | That the planned visual assessment was completed. |
| 10:10 — telephone contact resumes | The mode change and doctor’s assessment of what can proceed. | That audio is interchangeable with the lost video information. |
| 10:16 — doctor requests in-person assessment | Doctor-approved instructions and the arrangement assigned to reception. | That a suitable appointment has already been secured. |
| 10:25 — full report arrives | Receipt linked to TC-62 and the outstanding review task. | That the later report was seen during the earlier assessment or cancels the in-person plan. |
A patient may send a blurred photograph before the call, upload only one page of a report or attach an old prescription that differs from reported current use. Make those limitations visible. File receipt should not automatically imply that the content was verified or clinically reviewed.
Provide a way to connect a later document to the same unresolved question. Otherwise a report arriving after the call can sit in the chart without reaching the doctor who requested it. The encounter can be over from the video platform’s perspective while clinical work remains open.
Use timestamps that describe their event: uploaded, received by the clinic, reviewed by the clinician and communicated. These are useful for handover and troubleshooting. A single “last updated” time cannot explain the sequence when someone asks what information was available during the consultation.
Remote consultations can end because the call drops, the patient cannot hear, a document is unavailable or the doctor decides another assessment route is needed. A system that automatically marks every ended session complete makes these different outcomes difficult to recover.
Use administrative states that preserve the doctor’s actual outcome. Keep payment and booking consequences separate: a rescheduling or charge decision does not tell the next clinician what assessment occurred. The proposed states below describe workflow, not clinical eligibility.
On a narrow screen, scroll the table horizontally to read all columns.
| Event | What to record | What should remain visible |
|---|---|---|
| Patient has not joined | The contact attempt and administrative state. | Whether a clinician assessed anything; do not create a completed clinical visit by default. |
| Call disconnects | The interruption and the doctor’s documented outcome so far. | Any reconnection, review or other action the doctor specifies. |
| Required document is unclear | The limitation and what information is requested. | Who will obtain it and who will review it when received. |
| Doctor arranges in-person assessment | The clinical decision and relevant instructions. | The practical arrangement and accountable handover. |
| Consultation completed with follow-up | The approved record and communicated plan. | Any separate future task; completed consultation does not erase it. |
Confirm what document the patient will receive and by which appropriate channel. A patient who could hear the doctor poorly may also need clarification of the written plan. Preserve the final issued version and any later correction, just as for an in-person consultation.
If the doctor asks for more information or an in-person visit, assign the operational next step. Reception needs enough instruction to coordinate it without interpreting the clinical issue. If the patient cannot be reached or an appointment is unavailable, the obstacle should return to the responsible clinical process rather than disappear into a generic support ticket.
A useful end-of-session record answers three questions: what did the doctor conclude, what was communicated, and what still needs to happen? The video duration and a successful payment answer none of those questions by themselves.
A task reading “follow up teleconsultation” makes the next shift reconstruct the encounter. In TC-62, reception needs the specific arrangement requested, the patient’s agreed contact route, the person responsible and the route back to a clinician if the arrangement cannot be made. It does not need to invent an explanation for the clinical decision.
Record the action and its outcome separately. “Called, no answer” is an attempt; “patient confirmed the appointment and repeated the arrangement” records a different result. If the original doctor is unavailable when the missing report arrives, the clinic needs an identified clinical cover process. A task assigned to an absent person has not provided that cover.
Late information should carry its actual receipt and review times. The clinician can add a subsequent assessment linked to the earlier encounter without making the first note appear to include evidence that had not arrived. Keep an unresolved arrangement visible until the approved process records what happened; an administrative close button should not erase it.
Use fictional encounters that exercise the parts of the process most likely to be hidden by a polished video demo. Ask the vendor to show the record after each case, including what the next staff member can see. Confirm which behaviour is built into the product and which needs a clinic procedure or additional provider setup.
The acceptance evidence should describe the actual configuration, not simply repeat a feature label. “The interrupted encounter retains the doctor’s note and an assigned information request” is observable. “Complete telemedicine compliance” is not established by that single test.
In a fictional clinic, a relative books for an older family member and uploads a cropped report. The call connects, but the doctor records that the information is insufficient and chooses the next assessment step. The video provider reports the session ended normally. The clinic record nevertheless retains the limitation, the doctor’s decision and the person responsible for arranging the next step. When the full report arrives, it is linked to the outstanding task rather than silently changing the earlier encounter into a fully assessed visit.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
The doctor must decide whether the changed mode is suitable for the remaining assessment. Record the interruption, actual mode and decision. Successful telephone contact does not prove that information requiring video or an in-person examination was obtained.
Link it to the encounter and the outstanding question, with its actual receipt time and an assigned reviewer or cover arrangement. Keep the earlier note clear about what was available then. Receipt alone does not change the doctor’s prior plan or establish a new clinical review.
No. It establishes an administrative transaction. The record still needs to show the actual clinical assessment, applicable documentation, outcome and any outstanding next step.
Do not assume so. Map consultation documentation and separate activities such as recording or sharing to their applicable processes. The clinic should be able to explain what each recorded choice means and retrieve its evidence.
Keep the interruption and the doctor’s actual outcome visible, along with any further information or arrangement required. Ending the session should not automatically imply a complete assessment.
No. Remote prescribing must be assessed by the responsible doctor under current applicable guidance and the circumstances of the encounter. This article focuses on the supporting record and workflow.
Preserve the decision and relevant instructions, then connect them to a practical next step with an owner. It should remain clear that the video session and the subsequent arrangement are different events.
Updated on . The official guidance has its stated RMP scope. The status model, fields and test cases here are original operational analysis, not a statutory consent form, a remote-prescribing authorization or guidance for every system of medicine. No independent clinical or legal review is claimed.
Sections 3.2–3.5 and the caregiver section, read in the stated RMP scope on 28 October 2026. TC-62 and its administrative fields are original fictional examples, not statutory forms or timelines.
Clauses 3–6, checked from the NMC regulations index on 28 October 2026. Establishes the cited 2023 notification; it is not an exhaustive legal-status review of all telemedicine requirements.
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
Verify outside lab reports with worked OCR errors, missing-page handling, distinct dates and amended-report reviews for Indian clinic EMRs.
Review NMC prescription provisions, an annotated OPD format, a two-doctor document audit and reprint checks that preserve the original issued copy.
Use a fictional caregiver booking, a doctor change and an interrupted consultation. Inspect the record and follow-up tasks as well as the call interface, and confirm the available provider setup.
Request a clinic demo