Shared Patient-Intake Tablets: Privacy Between Every Session
Evaluate a waiting-room intake tablet across start, submission, timeout and reset, with a two-person privacy trial and an assisted alternative.
Before a returning-patient form displays saved history, establish both the intended patient record and the person's authority to view it. A name, date of birth or shared phone number can help match a record but should not be treated as a secret that grants access. Show only the information needed for the current task, provide a private assisted route for mismatches, and send patient-entered changes to an accountable review process.
Clinics evaluating returning-patient intake, prefilled forms, family-assisted booking and access to previously recorded information.
Three questions can be hidden inside a single 'verify' screen. Which patient record is intended? Who is using the form? What are they allowed to see or change? A system can answer the first correctly while answering the other two incorrectly.
A family may use one mobile number for several patients. A patient may know a relative's birth date, and a paper file may contain an estimated age rather than a documented date of birth. These facts affect matching and recovery. They do not justify treating every member of a household as one account with unrestricted history.
OWASP's authentication guidance advises against security questions for authentication or reauthentication. For an intake journey, the practical implication is that readily known demographic information should not be presented as proof that someone is entitled to see a clinical history. The appropriate authentication and permission design still needs technical assessment.
WHO's 2007 identification guidance concerns matching a patient to intended care using multiple identifiers. That safety process is related to, but different from, authenticating a remote user. A clinic should not convert an in-person identity checklist into a public history-unlocking form without examining the access consequences.
Source: OWASP: Authentication Cheat Sheet
Source: WHO Collaborating Centre: Patient Identification, May 2007
Prefilling can reduce repeated typing, but it also increases the information exposed if the wrong person opens the form. List the fields needed for the current task. Confirming a booking may not require showing past diagnoses, old consultation notes or detailed family information.
Use progressive access appropriate to the purpose and verified role. A person arranging an appointment may need a limited confirmation, while reviewing clinical history requires a different authorised journey. Do not assume a longer form is more helpful merely because the database can supply more fields.
Describe each displayed value as previous information until it has been confirmed or reviewed as appropriate. A phone number from three years ago, a temporary address and a historical medicine list do not become current because they appear in editable boxes.
Provide a clear way to say that a value is wrong, unknown or not appropriate to answer in that setting. Requiring an exact date where only an estimated year is known can produce invented data. Preserve the recorded uncertainty and use the clinic's identity process to resolve the mismatch.
On a narrow screen, scroll the table horizontally to read all columns.
| Situation | What must be established | What to avoid |
|---|---|---|
| Patient uses their usual verified access | Correct record, current session and permitted fields | Treating all stored history as necessary prefill |
| Shared family phone | Which patient and which person's access role | Opening every family member's history after one phone check |
| Birth date does not match | Whether the stored or entered value is uncertain or wrong | Disclosing hints that reveal another record or inventing a date |
| Contact number has changed | Supported identity recovery and contact update | Overwriting the old contact merely because a new number is entered |
| Companion completes the form | Reporter identity and authorised scope | Recording the companion's statements as the patient's verified account |
| Old link or expired session | Whether the access is still valid | Continuing to expose saved history from an earlier permission state |
A failed match should explain the next step without announcing whether a particular person has a record or revealing their stored details. Avoid public prompts that progressively expose a birth date, phone ending or diagnosis in response to repeated guesses.
Offer a staffed route through the clinic's approved verification process. Explain when it is available and what the person should do if their appointment is imminent. A recovery option that only says 'contact support' without a usable contact path pushes staff towards informal disclosure.
When updating a contact, consider where existing reminders or private links are going. Record the verified change and reconcile future communication through the supported process. A number replacement should not silently move another family member's messages or grant access to their records.
If the patient cannot recall the expected information, preserve the uncertainty. Staff can investigate a paper card, an earlier encounter or other approved evidence privately. The goal is to find the right record and establish authority, not to make the patient guess until the form accepts an answer.
Do not create a second patient record simply to bypass an access problem. Where a new registration is genuinely needed, make that decision through the identity process and retain the relationship to any unresolved previous file for later review.
The origin of a change matters. A patient reporting a new phone number, a carer entering a medicine name and a clinician correcting an allergy are different actions. Keep the author or reporter, time and original value where relevant, with an appropriate decision about who may accept the change.
An original reconciliation example contains 20 submitted changes: 12 straightforward demographic confirmations, three contact changes needing verification, two clinical-history conflicts and three unanswered items. These total 20 review items, not 20 patients. The two conflicts and three unanswered items must not be silently converted into normal findings.
Define how the clinician sees submitted information before relying on it. A patient may select 'no change' while overlooking an old medicine or may leave an allergy field blank because they do not understand it. Neither action should erase a previously documented safety concern automatically.
If a submitted change corrects a genuine error, preserve an appropriate history of the correction rather than keeping two equally current versions. If it remains uncertain, make the uncertainty visible and assign the next step. A neat-looking profile is less valuable than an accurate account of what is known.
Use a synthetic household with two patients sharing a contact number, a person with an uncertain birth date and a separately authorised companion. Demonstrate what each user can see before and after verification. Include a case that should succeed and a case that should be refused.
Test old links, refresh, a second tab and the end of a session on a shared device. Check whether previously displayed history remains visible after access ends and whether the next patient starts with their own context. Changing the page title is not sufficient evidence that the previous record has been removed from view.
Inspect the saved change in the staff review view and the patient's current record. Verify that the same response was not submitted twice after a timeout, and that rejecting a proposed change does not remove the original evidence.
Ask staff to complete the assisted route without using an owner's password or exposing the chart on a public screen. The recovery path needs to be both usable and appropriately restricted; otherwise the intended access controls may be undermined in everyday work.
Review later changes to family contact arrangements and permissions through the same model. A person who previously helped with booking may no longer be the chosen contact. Historical assistance should not become permanent unrestricted access.
In the fictional review, 12 demographic confirmations, three contact changes, two clinical conflicts and three unanswered items total 20. The clinic uses different acceptance paths for each group. A successful form submission is evidence that information arrived, not that every value is current or clinically verified.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
A birth date may help match a record, but it is not a reliable secret establishing digital access authority. Evaluate authentication, permission and a private assisted recovery route separately.
Preserve the uncertainty and use the approved identity-resolution process. Do not invent a date merely to satisfy the form.
Patient-entered changes need provenance and the appropriate review. A blank or conflicting answer should not silently erase an existing clinical concern.
First investigate the existing record and access problem through the private recovery route. A second registration should not be a shortcut around verification.
Updated on . Original identity and intake analysis. It is not a specification of a complete authentication system or a claim that a demographic check grants clinical-record access. No independent clinical or legal review is claimed.
Technical authentication guidance; clinic identity matching and authority to see another person’s records require separate decisions.
International identification guidance; a queue token and knowledge of demographics do not establish digital access authority.
Evaluate a waiting-room intake tablet across start, submission, timeout and reset, with a two-person privacy trial and an assisted alternative.
Review repeated, conflicting and newly reported allergy information with provenance, clinician decisions and an explicit reconciliation matrix.
Coordinate family appointments and support while keeping individual records, recipient permissions, payer roles and contact changes distinct.
Use a synthetic shared-phone household and an uncertain birth date to demonstrate permitted access, refusal and assisted recovery. Trace one proposed contact change and one clinical conflict into their separate review paths.
Request a clinic demo