The bedside reality check.
I still practice medicine. Patients, time pressure, and clinical uncertainty keep my engineering grounded in how care actually happens.
I build safer clinical AI and FHIR-integrated health software, grounded in patient care.
I still practice medicine. Patients, time pressure, and clinical uncertainty keep my engineering grounded in how care actually happens.
I build and test the software myself. Data quality, schema boundaries, runtime behavior, and failure modes are engineering decisions with clinical consequences.
Recorded ECG and PCG data, BLE experiments, FHIR resources, and clinician-facing interfaces each require careful handoffs. I work across those boundaries without losing the clinical question.
Generic text scores can miss dangerous clinical errors. I built an evaluation path for diagnostic omissions, contraindications, and dosage discrepancies, with clinician review kept in the loop.
I developed a path from HL7 v2 feeds to structured FHIR R4 resources, then into a keyboard-driven clinical workspace that makes a patient’s course easier to reconstruct.
For use in India, I consider ABDM’s FHIR R4 profiles, consent-led health-data sharing, and India’s data-protection framework. This project has not undergone formal conformance or legal review.
I led an exploration of whether patterns in recorded ECG and heart-sound datasets could help identify coronary artery disease risk. I used Python and MATLAB for the analysis and explored BLE as a possible device connection. The prediction model remains an early research prototype, not a diagnostic tool.
Rural care cannot assume a stable connection. I designed local-first collection and delayed synchronization around field diagnostics and follow-up, with record integrity as the central constraint.
A study of why patients self-administer NSAIDs, how they obtain them, and their awareness of adverse effects.
DOI 10.18231/j.ijpp.2020.002Evidence mapping on unmet surgical need across low- and middle-income countries. Accepted by World Journal of Surgery; indexing and citation details are pending.
Doctor who codes.
I translate bedside needs into clear product decisions and working software, so clinical intent reaches engineers without getting lost in handoff.


Outside clinical practice and software, I spend my time at the piano and behind a lens. Both sharpen the same instincts I bring to engineering: cadence, restraint, structure, and attention.
I can recognize clinical edge cases while writing the system that handles them. Active practice keeps patient safety, workflow friction, and uncertainty close to the implementation.
Clinical work keeps me grounded in real care. I plan engineering work around those commitments and collaborate asynchronously with clear specifications, code, and decision records.
Its outputs need clinical evaluation, deterministic checks where possible, and a human review path. I test missed red flags, contraindications, dosage errors, and whether the interface keeps the clinician in control.
I build clinical AI and FHIR tools, plus React dashboards, web apps, and heatmaps. Java is my strongest language; I also use JavaScript and Python.