Spotlight: Yogesh Daga @ Nirmitee.io
A spotlight is a short-form interview with a leader in health tech. In this spotlight, you'll hear from Yogesh Daga, co-founder and CEO of Nirmitee.io.
What does Nirmitee.io do?
Nirmitee.io is a healthcare product engineering company connecting clinical systems and revenue cycle workflows. We help digital health teams build products, integrate EHRs through FHIR and HL7, and implement X12 eligibility and claims workflows. For teams building with Stedi, we deliver API integration, data mapping, screens to review coverage and correct rejected submissions, testing, and an operational handoff.
How did you end up working in health tech?
My father was bedridden for 18 years and recently passed away. Our family's experience of long-term care shaped my purpose in healthcare and my interest in elderly care. Nirmitee is my second company; running a bike rental business (boongg.com) and building its technology from scratch taught me to understand daily operational challenges before designing software.
How does your role intersect with revenue cycle management (RCM)?
As co-founder and CEO, I translate customers' operational challenges into engineering scope, from repeated data entry to unclear coverage responses and unowned follow-up. Claims workflows must distinguish rejection, denial, acceptance, and payment, with a clear next action for staff. I work with customers and our engineering leadership to define access requirements, responsibilities, and tests for routine and exception paths. We build software supporting RCM teams and expand after customers validate the initial workflow.
What do you think RCM will look like two years from now?
I expect RCM to become more proactive and coordinated by AI agents: checking coverage and authorization before care, catching documentation gaps before submission, tracking responses, gathering records, and routing exceptions. Payer APIs and electronic claims attachments should support this shift, although adoption will vary. The challenge is aligning clinical data, payer requirements, and claim status. Trust requires traceable actions, duplicate prevention, and informed human handoffs; eligibility or authorization still does not guarantee payment. I would measure success by fewer avoidable denials, less rework, and more predictable cash flow, supported by reliable integrations and clear ownership.