Reviews, without the HIPAA problemReviews and reputation management for audiology practices
Volume, recency and response, collected in a way that discloses no care.
The problem
Reviews decide the map pack and they decide the phone call. Most review software works by confirming, in public, that a named person received care — which is the one thing a healthcare practice cannot do.
Nobody here is named, and that is the point. The outcome is publishable; the patient is not.
The constraint is the whole design
Generic review tools assume a restaurant. They pull a customer list, send a request, and respond publicly with thanks for coming in on Tuesday. Run that at a hearing practice and every public response is an acknowledgement that a named individual is a patient.
So the flow gets built backwards from that constraint: how the request is triggered, what it says, who it comes from, and what a response may and may not confirm.
Hearing care has a structural advantage here
Patients in this field are unusually, genuinely grateful. Someone who has been withdrawing from their own family for six years and can suddenly hear their grandchildren does not need to be incentivised to write something. They need to be asked, once, at the right moment, in a way that is easy to act on.
The right moment is not the day of the fitting. It is a week or two later, after the adjustment period has done its work.
Steady beats spiky
Twenty reviews in a fortnight after eleven months of silence is a visible pattern and it is discounted accordingly. A handful every month, indefinitely, is worth far more and is easier to sustain, because it is a habit rather than a campaign.
Responding without disclosing
Every review gets a response, and the templates are written to be warm while confirming nothing. Thanking someone for kind words about the team is safe. Referencing their appointment, their device, or their hearing is not. The same discipline applies to a complaint, where the instinct to correct the record publicly is strongest and most dangerous.
- Praise: warm, brief, specific to the team rather than to the person's care
- A fair complaint: acknowledge the feeling, move it to a phone number, confirm nothing
- A review that is not yours: the reporting route, plus a public response that stays neutral
- A review naming a clinician: handled at provider level, since it affects that provider's own profile
What reviews tell you about the practice
Read quarterly and in aggregate, reviews are the cheapest operational feedback a practice gets. Recurring themes about waiting, about the front desk, about how the price was explained — that is not marketing data, and it is usually the most useful thing in the report.
Questions about this piece
Is asking for reviews a HIPAA problem in itself?
Asking is not the problem; the disclosure risk sits in how the request is delivered and how responses are written. We build the flow around that, and your own compliance counsel should sign off before it goes live. We are not lawyers.
Can you remove a bad review?
Only where it genuinely violates platform policy, and that is rarer than anybody hopes. The realistic answer is to respond well and to out-publish it with steady recent reviews, which works better than it sounds.
Do you use incentives?
No. It violates platform terms, it is a regulatory problem in healthcare, and it produces reviews that read as bought. The ask is the whole mechanism.
This one rarely works alone.
The audit decides which pieces you actually need and in what order. You keep it whether or not you continue.
Works with
- 8 kHzLocal SEO & Google Maps
The three results above the fold when someone types hearing test near me.
- 8 kHzGoogle Business Profile optimization
Categories, services, hours, providers and photos: the fields that decide the map pack, filled in properly.
- 2 kHzAI search & answer engines
Being the practice an assistant names when someone asks it who to see.