Build Journal · THC CDSS
Decision support, not decision making: where I draw the line in a CDSS
By Ganesh R Datta. I build healthcare AI end to end: clinical decision support, clinic intake, and the marketing and operations around them.
In THC CDSS the physician stays responsible for the diagnosis and the plan; the software prepares, organises and suggests. Drawing that line clearly is what makes clinicians willing to use AI in the first place.
The phrase "clinical decision support" gets stretched. Some products quietly make the decision and ask the clinician to approve it. I build the other kind.
Where the line sits
THC CDSS guides the care team through an AI-assisted assessment, organises findings, highlights likely root causes and drafts a plan inside the clinic's program structure. The physician decides the diagnosis and the plan.
How the line shows up in the product
- Outputs are framed as findings and suggestions, not conclusions.
- The physician can change anything before it reaches the patient.
- Where data is missing, the system says so rather than filling the gap.
Why it matters beyond compliance
Clinicians are accountable for outcomes. They will only lean on a tool that respects that. Clear responsibility is not a limit on the product; it is the reason it gets used.
More from the Build Journal
The full Build Journal · The THC CDSS work · Book a 15-minute call