Skip to main content

Keep Private Patient Feedback Private: Test Every Publication Path

Keep private feedback in a restricted workflow from collection through storage, review, export and deletion or retention decisions. A separate public-review box is not enough if both feeds share an uncontrolled publication path. Treat any proposed testimonial as a new use, check the exact content and authority, and test public pages, attachments, previews and exports with synthetic private material before relying on the boundary.

By Bractis · Updated · 8 min read

Indian clinic owners and managers evaluating whether feedback, complaints and clinical comments can accidentally appear on public pages or reach unrelated staff.

Privacy depends on the whole route, not the label on the form

A patient can reasonably understand 'send privately to the clinic' as a different action from posting a public review. That distinction has to survive what the software does next, including notifications, dashboards, exports and integrations.

Map the content's destinations. A response may reach an email, a staff worklist, an attachment store, a reporting export and an analytics system before anyone considers publication. A private label on the original form says little about those later copies.

Separate the original feedback record from any public content object. Reusing the same text field with a visibility toggle can make an accidental state change publish the whole response, including details never intended for an audience.

Keep attachments in the map. A screenshot or PDF may contain identifying information that is absent from the visible comment. Restricting the comment page while leaving its attachment available through a direct link is an incomplete boundary.

Use synthetic material for the initial evaluation. A fictional phrase and invented patient identifiers let the team trace where content appears without exposing a real person's experience during a demonstration.

A hidden link or noindex setting is not access control

OWASP recommends denying access by default and validating permissions on every request. Applied to feedback, an unauthorised person should be unable to retrieve the private object itself, not simply unable to find its menu entry.

A long or unlisted URL can still be forwarded, logged or exposed through a preview. A search-engine instruction does not decide whether another person may open the page. Ask whether the server checks the requester's authority for the actual record.

Consider which authorised staff need which information. A billing manager may need the disputed charge and contact route; a clinician may need a care concern; reception may need only the assigned next action. A staff login should not imply unrestricted access to every complaint.

Exports deserve their own permission and purpose. A person allowed to handle one case may not need a bulk file of all responses. The destination device and later handling of that file also affect privacy.

Check what happens after a user changes role, a session ends or an attachment is replaced. A previously issued link or cached copy can behave differently from the current screen. Record what can be withdrawn and what cannot be recalled.

Source: OWASP: Authorization Cheat Sheet

Do not turn a private compliment into a public story by default

An internal response can support a service improvement without becoming marketing material. A private 'thank you' is not automatically a request for a public quotation, and deleting the name may not remove identifying details.

Look for indirect identifiers: a precise appointment date, rare procedure, village, family relationship or a recognisable sequence of events. The combination can identify a person even when each detail appears ordinary in isolation.

If publication is proposed, treat it as a separate decision about a specific excerpt, display identity, destination and purpose. Check the relevant professional and legal position as well as the person's choice; permission alone does not make every promotional use appropriate.

Do not publish the raw internal record and then ask the patient to object. A review of the exact proposed public version needs to happen before the publication action, with a record of what was agreed and by whom.

Be honest about withdrawal limits. The clinic may remove content it controls, but it cannot promise deletion from every recipient's device, screenshot or independent cache. That limitation should inform the decision before publication, not appear only after a problem.

Build an access matrix with both allowed and blocked cases

In an original synthetic exercise, test five outputs using three roles: a designated feedback manager, the clinician assigned to the particular care concern and an unauthenticated visitor. The fixture gives the first two roles a legitimate need to read its case and relevant attachment; only the manager is authorised for the particular export.

The five outputs are the private case, its relevant attachment, the authorised case export, public site search and the link-preview output. That gives 5 × 3 = 15 checks. The expected results in this invented configuration are five allowed reads and ten blocked disclosures.

Public search and link previews should contain none of this private fixture for any role. A logged-in staff member should not cause a public-facing preview to acquire private text merely because they can read the original case internally.

Also test a second clinician who is not assigned and a user whose access was revoked. These are additional checks beyond the fifteen-case example; their expected results come from the clinic's actual permission design.

Run the same reasoning through notifications, external review feeds and bulk reports. A passing case-detail screen cannot establish that every downstream route enforces the same boundary. Record the tested routes and any untested ones explicitly.

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

Original fifteen-check fixture: expected access to one private feedback case
Output containing the private fixtureDesignated managerAssigned clinicianUnauthenticated visitor
Private case detailAllow for the assigned taskAllow for this assigned care concernDeny
Relevant private attachmentAllow for the assigned taskAllow for this assigned care concernDeny
Case export authorised to managerAllow within the stated export scopeDeny in this fixtureDeny
Public search result textDo not expose private fixtureDo not expose private fixtureDo not expose private fixture
Public link-preview textDo not expose private fixtureDo not expose private fixtureDo not expose private fixture

Stop further exposure while preserving the facts

If private content appears publicly, first identify the actual outputs and restrict the routes under the clinic's control. Pausing the source form alone may leave an existing public page, attachment or outbound feed available.

Preserve proportionate evidence of what was exposed, when and through which route for the responsible response team. Avoid copying the full content into a large staff chat to ask who recognises it.

Assess recipients and downstream copies, what has actually been removed and what remains uncertain. Follow the applicable incident-response and professional notification process; this guide does not supply a universal legal deadline or decide a particular notification duty.

Keep the original complaint and any clinical action available to the authorised team. Removing a public copy should not erase the patient's concern or the evidence needed for its confidential investigation.

Before resuming the route, repeat the failed synthetic case and adjacent permission checks. A cosmetic change that hides a card is insufficient if the same content can still be retrieved from the underlying endpoint or attachment.

Assign one owner for the communication about the incident and another task owner where clinical follow-through is needed. The patient should not have to repeat the entire sensitive story to every team involved.

A private screen can coexist with a public attachment leak

The fifteen-check synthetic fixture expects five authorised reads and ten blocked disclosures. If the case page is protected but an unauthenticated visitor can retrieve its attachment, the boundary has failed despite a correct 'private' badge. The test follows the object and its outputs rather than trusting the screen label.

Test private-feedback publication boundaries

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

Map every destination
Trace one synthetic response from submission through staff views, notifications, exports and any public-facing output.
Define the negative cases
Identify who must not access the response, including unrelated clinicians, revoked users and unauthenticated visitors.
Separate public reuse
Write the exact process for considering a testimonial without reusing the raw private record or assuming anonymity.
Rehearse containment
Test how an accidental page or attachment exposure is restricted while the confidential complaint and clinical action remain intact.

Questions doctors ask

Do separate private-feedback and public-review boxes guarantee privacy?

No. Their storage, permissions, attachments and publication routes must also remain separate and controlled. A shared export or feed can expose private content despite different labels on the forms.

Is noindex enough to protect a private feedback page?

No. Discoverability controls do not authorise or deny a person's request for the content. The record and its attachments need appropriate access checks.

Can a private compliment be published after removing the name?

Not automatically. Dates, locations and circumstances can still identify a person, and public reuse is a different purpose. Review the exact proposed content, authority and applicable professional rules before publication.

Should everyone who can read a feedback case be able to export all responses?

No. Reading one assigned case and exporting a wider dataset are different operations. Define the export purpose, permitted scope, recipient and handling separately.

What should the clinic do if private feedback appears publicly?

Restrict the exposed routes under its control, preserve proportionate evidence and follow the appropriate incident-response process. Keep the underlying complaint and any clinical work available to authorised staff, and verify the fix before resuming publication.

Sources and scope

Updated on . Original privacy-boundary design and proposed security tests. It is not a legal determination about a particular disclosure, a certification of anonymity or a security assessment of the current product. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Ask the Bractis team to run the fifteen synthetic access checks, including direct attachment retrieval and public previews. Record the actual results and untested routes; this guide does not claim those product checks have already passed.

Request a clinic demo