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.
Evaluate patient links by whether the intended person can understand, complete and recover the actual task on their device. Test small-screen reflow, language, keyboard and screen-reader use, slow connections, authentication and appropriate family assistance. A low handset price or a fast page-load score alone cannot establish that a clinic form or report is accessible.
Indian clinics evaluating appointment, intake, report and follow-up links used on shared phones, older devices and variable connections.
A link may ask a patient to confirm an appointment, provide history, read a report or request help. Each task has a different endpoint. Loading the page is not completion, and submitting a form is not proof that the patient understood the resulting instructions.
Choose one task and write the expected result in ordinary language. For a fictional intake, that may be 'the correct patient's answers are submitted once, a clear receipt appears and the clinic can find the record'. For a report, it may include readable source information and a usable contact route.
Test devices and conditions representative of the clinic's patients rather than relying on a handset price category. Price does not identify browser version, storage pressure, text settings, screen size or network quality.
Include the people who may need assistance, with appropriate consent and privacy safeguards. A clinic should offer a workable alternative where a digital route is unsuitable; the testing exercise should not make patient access depend on buying a newer phone.
Prioritise the patient's next action, the purpose of the page and the identity context needed to avoid mistakes. Decorative content, repeated banners and large introductions can push the actual form or report below what the patient expects to find.
W3C's WCAG 2.2 Reflow explanation describes vertical content working at a width equivalent to 320 CSS pixels without two-directional scrolling, with exceptions for content that needs a two-dimensional layout. This is a defined accessibility criterion, not a claim that testing one narrow screenshot proves conformance.
Inspect long names, regional-language text, enlarged text and error messages. A design that works with short English labels may clip a translated option or put a required instruction off screen. Test the actual text rather than a placeholder of similar length.
For wide clinical tables, keep headers and relationships understandable and provide an accessible way to reach all columns. Do not solve narrow-screen layout by shrinking every number until it is technically present but difficult to read.
Give each input a persistent label and explain the format when needed. A placeholder disappears after typing and is a poor substitute for the question. For dates and phone numbers, consider the actual expected format and avoid error messages that merely say 'invalid'.
WCAG 2.2's Level AA minimum target-size criterion is 24 by 24 CSS pixels, with specified exceptions including spacing and inline targets. It is not a universal 44-pixel rule. The clinical task may still benefit from larger controls, especially where adjacent choices are easy to confuse.
Check keyboard order, visible focus, native control names and screen-reader announcements. A user must be able to find a validation error and return to the affected field. A green tick or red border alone does not explain what happened.
Separate 'not known', 'not applicable' and an unanswered question where those meanings matter. Do not make an uncertain patient select a negative medical answer merely to submit the form. Clinical interpretation belongs in the receiving workflow.
Distinguish loading, local entry, transmission and confirmed receipt. A spinning button may mean the request is still running, has failed or succeeded while the response was lost. The patient needs an understandable status and a safe next step.
Use fictional data to interrupt a submission, return from another app and reopen an expired session. Check whether entered information survives where promised, whether it remains protected and whether repeated taps create duplicate records.
Recovery has a privacy trade-off. Keeping answers on a shared device may reduce re-entry but expose sensitive information later. Do not assume persistent local storage is always preferable. The clinic and vendor need a deliberate policy for the actual task and audience.
Where a link expires, explain how to obtain appropriate access again without exposing the record to anyone who knows the old URL. A helpful error page should not ask the patient to send their complete medical history through an unverified channel.
The original matrix below covers different failure mechanisms. It is a practical starting point for clinic evaluation, not a complete accessibility audit or a substitute for testing with relevant users and assistive technologies.
Keep the task and expected ending consistent while varying the condition. Record the device, browser, text settings, language and network simulation used so a result can be reproduced.
On a narrow screen, scroll the table horizontally to read all columns.
| Condition | Task to attempt | Evidence to observe |
|---|---|---|
| Narrow screen and enlarged text | Read instructions and complete the form. | No lost labels, controls or essential content. |
| Keyboard or screen reader | Find fields, correct an error and submit. | Meaningful names, focus and understandable status. |
| Regional language or long name | Use actual content and labels. | Readable rendering and preserved meaning. |
| Slow or interrupted connection | Submit once, recover and check receipt. | Clear uncertainty; no misleading success or duplicate record. |
| Assisted shared-phone use | Select the intended patient and complete the authorised task. | Identity, assistance and access boundaries remain clear. |
| Expired or invalid link | Find an appropriate recovery route. | Helpful explanation without unauthorised disclosure. |
In a fictional twelve-attempt evaluation, eight people complete the task independently, two complete it with assistance and two do not finish. Independent completion is 8 ÷ 12 = 66.7%; completion including assistance is 10 ÷ 12 = 83.3%. These invented figures illustrate reporting, not a product benchmark.
Keep the two incomplete attempts in the record and explain their causes. One may fail because authentication cannot be completed; another may lose entered information after a connection break. Excluding them would hide exactly the problems the clinic needs to solve.
Assistance is not inherently failure. The important questions are whether it was appropriate, available and compatible with the person's privacy and preferences. Report the assisted route separately so staffing requirements do not disappear into a single success percentage.
Do not treat a small convenience sample as proof of accessibility for the entire patient population. Record who and what the evaluation did not cover, then use those limits to plan the next improvement.
Choose an owner for patient access problems and a way to distinguish a clinical question from a technical failure. A patient unable to open a report should not be sent repeatedly between reception and generic vendor support without a responsible next step.
Use the original record below to make an acceptance decision. Resolve barriers that block the essential task and document any remaining limitations and alternatives. An automated score alone cannot establish whether the workflow is usable or clinically understandable.
A fictional report link loads quickly on a phone, yet the download control is obscured after the user enlarges text. The clinic's performance dashboard shows success because it measures page loads. A task-based review finds the barrier, verifies the repaired control with the relevant access methods and retains an alternative route for the patient. The measured endpoint changes from loading to usable access.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
A price category does not define compatibility or accessibility. Test the relevant devices, browsers, settings and tasks, and state the supported scope with an alternative route where needed.
It demonstrates access to a channel. Patient identity, representative authority and the intended record still need the appropriate workflow, especially on shared family phones.
It can be a valid route when appropriate and available, but report it separately from independent completion. Record the privacy boundaries and staff or family help required.
No. Verify real task completion, comprehension, authentication and recovery with relevant devices and access methods. Automated checks cover only part of the experience.
Updated on . This guide provides task-based evaluation ideas and selected accessibility references. It is not a WCAG conformance report, device compatibility guarantee or verification of every Bractis patient-link workflow. No independent clinical or legal review is claimed.
Explains the 320 CSS-pixel reflow criterion and exceptions. The clinic task checks are not a full WCAG conformance audit.
Explains the 24 by 24 CSS-pixel Level AA criterion and its exceptions. Larger usable controls can still be appropriate.
Handle shared family phones with separate patient records, worked matching cases, purpose-specific contact changes and queued-message checks.
Build a coherent record across remote and in-person visits, separating participant identity, clinical evidence, issued instructions and unfinished follow-up.
Prepare a source-linked immunisation summary, separate administered and reported doses, handle corrections and clarify when a recipient needs an official certificate.
Complete one fictional patient task using enlarged text and an interrupted connection. Repeat through an appropriate assisted route, then inspect the receipt, record identity and any duplicate submission.
Request a clinic demo