Build Journal · THC CDSS
Why every page of a clinical tool sits behind sign-in
By Ganesh R Datta. I build healthcare AI end to end: clinical decision support, clinic intake, and the marketing and operations around them.
THC CDSS handles patient information, so every page is restricted to authorised clinicians. That choice limits what can be shown publicly and slows down demos, and it is still the right default for clinical software.
On most products, a public demo page is good marketing. On a CDSS it is a risk.
The decision
Every page of THC CDSS sits behind clinician sign-in. There is no public view of patient-facing screens, and no sample data mixed with real data.
What it costs
- I can't show the inside of the product on my site. The case study stops at the sign-in screen.
- Demos happen on calls, with care.
- Onboarding new clinicians takes a few extra steps.
Why I accept that cost
In healthcare, trust is the product. One leak of patient information outweighs every marketing benefit of an open demo. Practitioners and patients both notice when a vendor takes this seriously.
A practical habit
Treat security choices as product decisions and write them down next to the feature list. If the team discusses "who can see this" with the same seriousness as "what does this do", the defaults come out right.
More from the Build Journal
The full Build Journal · The THC CDSS work · Book a 15-minute call