The Clinical Anatomy of Elective Care: Damini Rijhwani’s New Architecture for Private Practice

By Ethan M. Stone | Jun 10, 2026
Damini Rijhwani

Opinions expressed by Entrepreneur contributors are their own.

You're reading Entrepreneur Middle East, an international franchise of Entrepreneur Media.

Damini Rijhwani builds software for elective care the way an engineer builds for a system that cannot afford to fail. A computer engineer and the founder of Automation Core Inc., she treats the private consultation room as a safety-critical environment, where a misjudged clinical decision or a moment’s distraction carries genuine consequence. Her platform, Dalphene, is designed to hold a clinician’s attention on the patient rather than the paperwork, starting with medical aesthetics as its first deep vertical. Her work targets a persistent vulnerability in healthtech, where fragmented, disjointed software increases the cognitive load on the people delivering care and can introduce unnecessary risk at the precise moment it matters most.

Rijhwani trained as a computer engineer at Purdue University before joining Philips North America, where she worked on machine learning for interventional and diagnostic imaging. This was the field that taught her to treat clinical software as something closer to instrumentation than to ordinary business tooling, and where she became a named inventor on an international patent application owned by Philips. Time spent inside procedure rooms and clinics gave her a working fluency in both the clinical vocabulary and the operational friction of elective medical practice.

“I treat clinical software with the same unforgiving discipline I applied to medical imaging code,” Rijhwani says. “You must assume the clinical input is far more chaotic than the technical specification, you must assume the clinician is exhausted, and you must design for the most difficult Tuesday afternoon of their week rather than the polished environment of a sales demonstration.”

She built and incorporated Automation Core in the United States, where the company is based, and designed the platform for international deployment with the United Arab Emirates as an intended expansion market. Anticipating that health data tied to care delivered in the region would face data-localization requirements, she architected the platform to meet that constraint from her first commit rather than retrofitting it later.

At Automation Core, Rijhwani filed her first provisional patent application as an independent inventor earlier this year, setting out her own approach to digital procedure planning. According to the application, the invention introduces an anatomical reference visualisation system that renders population-derived risk zones, drawn from peer-reviewed anatomy literature, directly onto a photograph of the patient’s face during a planning session, intended as a visual reference to support, rather than replace, the clinician’s own anatomical judgement. The application is her first patent filing under Automation Core, distinct from the Philips research behind her earlier inventorship.

Rijhwani deliberately rejected the fragmented systems common in elective care, where scheduling, charting, and inventory tools are loosely connected by manual data entry. Instead of building a broad, shallow operating system, she engineered Dalphene as a single platform with a shared spine (scheduling, patient record, payments, memberships, inventory, communications, AI front desk, and ambient charting) where highly specialized clinical workflows plug in, starting with medical aesthetics. “The majority of my engineering work is unglamorous,” she says. “It is hours of watching how a treatment actually unfolds in the room, where a clinician hesitates, what they reach for, what pulls their concentration away, because those are the exact moments the software has to absorb instead of adding to.”

For the clinicians who would actually use it, the clinical depth of this safety layer is the part that resonates most.

“In our practice, safety during non-surgical interventions relies entirely on a precise understanding of facial danger zones and vascular anatomy. Damini’s approach of rendering peer-reviewed anatomical risk zones directly onto the patient’s own photograph during the planning phase is a highly sophisticated way to support clinical decision making and patient education.”

Dr. Suhas Sateesh, Plastic Surgeon

In Rijhwani’s view, the point of greatest vulnerability in elective procedures is less often a lack of clinical knowledge than a lapse in the physician’s focus. The visual rendering of vascular danger zones in her first vertical is intended to help at a critical moment of the patient encounter, but she argues that its usefulness depends on a broader operational reality: a clinician’s attention, she contends, is only as clear as the clinical and operational system supporting them in the lead-up to that moment.

Rijhwani’s design treats the entire patient visit within her platform as a single, continuous record, an attempt to keep the small frictions of switching between disconnected tools from fragmenting a clinician’s attention during the work itself.

“Damini understands the math and the clinical gravity of what we do in aesthetic medicine, and that understanding is built into how the platform actually works. She has engineered the booking, the consultation, the chart, the patient photographs, and the inventory into a single continuous record, which removes the tiny, repetitive structural frictions that interrupt our attention during a treatment.”

Dr. Murtuza S. Bandukwala, Aesthetic Dermatologist

Rijhwani is working during a quiet correction within the healthtech industry, which is beginning to question the legacy systems of the past fifteen years. Those older platforms were often optimised for administrative audits, leaving clinicians to bear the cost in cognitive fatigue, late-night administration, and the gradual erosion of their clinical focus. Rijhwani is candid that her own correction in elective care is early and incremental, the kind of change that comes one practice at a time rather than all at once, in a category that has gone underserved by deep clinical software for years.

For now, Rijhwani is spending her time where the software meets the work, in consultation rooms rather than boardrooms, refining the platform against what she observes. Whether that close-range approach can scale as she expands Dalphene across the broader landscape of elective care is the open question for any founder building deep clinical software one practice type at a time.

This article is for informational purposes only and does not constitute medical advice. Any technology described is intended to support, not replace, the independent judgement of a qualified clinician.

Damini Rijhwani builds software for elective care the way an engineer builds for a system that cannot afford to fail. A computer engineer and the founder of Automation Core Inc., she treats the private consultation room as a safety-critical environment, where a misjudged clinical decision or a moment’s distraction carries genuine consequence. Her platform, Dalphene, is designed to hold a clinician’s attention on the patient rather than the paperwork, starting with medical aesthetics as its first deep vertical. Her work targets a persistent vulnerability in healthtech, where fragmented, disjointed software increases the cognitive load on the people delivering care and can introduce unnecessary risk at the precise moment it matters most.

Rijhwani trained as a computer engineer at Purdue University before joining Philips North America, where she worked on machine learning for interventional and diagnostic imaging. This was the field that taught her to treat clinical software as something closer to instrumentation than to ordinary business tooling, and where she became a named inventor on an international patent application owned by Philips. Time spent inside procedure rooms and clinics gave her a working fluency in both the clinical vocabulary and the operational friction of elective medical practice.

“I treat clinical software with the same unforgiving discipline I applied to medical imaging code,” Rijhwani says. “You must assume the clinical input is far more chaotic than the technical specification, you must assume the clinician is exhausted, and you must design for the most difficult Tuesday afternoon of their week rather than the polished environment of a sales demonstration.”

Related Content