
NDA
The client is a US-based healthcare provider focused on oncology. The organization operates as a high-revenue clinic that requires precision tools for medical coding, patient management, and financial reimbursement.
Industry: Health & Pharma, AI/ML Big Data
Technologies: Python, C# & .NET
Solutions: AI/ML Big Data, App Development, Scripting & Process Automation, Database Management & Storage, Cloud Computing & Devops
After each patient visit, oncologists typically spent 10-20 minutes writing progress notes. This administrative burden reduced the time available for patient care and required hiring extra staff for scrubbing (medical coding for insurance reimbursement).
Communication between departments relied on scattered communication tools, including messengers, phone calls, and paper notes. When doctors ordered tests or procedures, there was no systematic way to track requests, communicate with staff, or maintain audit trails. Tasks were frequently missed or delayed.
The clinic needed clinical workflow automation software that could handle documentation, communication, and billing workflows within a unified system.
The project began in July 2025 as a Python script intended for AI summaries. Within weeks, feature requests multiplied, and the project evolved into a business-critical AI workflow assistant for healthcare, responsible for clinical workflows and revenue streams. The engineering team grew from 1 engineer to 10 contributors.
By November, we faced a critical decision: continue building on the architecture designed for a pet project or rebuild from scratch. We chose the latter, completing a full system rewrite while simultaneously onboarding new team members and maintaining an aggressive delivery schedule.
Healthcare software development presents unique challenges that don't exist in most enterprise environments. We couldn't simply move fast and break things. Every AI-generated summary had to be validated by oncologists.
Unlike traditional software with deterministic behavior, our AI healthcare assistant relied on evolving AI models. OpenAI and Azure regularly update their models, deprecate older versions, and modify behavior in ways that could break our carefully tuned prompts.
We used rapid prototyping for both requirements gathering and risk mitigation. Healthcare clients often lack the time or technical knowledge to produce formal requirements documents, so we built functional prototypes within 24 hours that clients could interact with using real UI and dummy data. This approach lets stakeholders quickly see and refine what they need rather than spending weeks on traditional requirements documentation.
For complex features like Ambient Listening, we created end-to-end prototypes with basic architecture to test feasibility (latency, quality, integration) before committing to full-scale development. We took the same approach with the workflow system: our engineer delivered a working prototype in 3 days, validating the concept early on. This approach reduced risk and ensured product-market fit before committing significant resources.
We developed an advanced AI medical scribe and AI tool for patient charting that:
In addition to structured summaries, we built Ambient Listening functionality. Ambient Listening automatically transforms doctor-patient conversations into formatted clinical documentation, using Speech Matrix for speech-to-text conversion.
We implemented prior authorization AI to streamline insurance approval processes. The system:
As a result, we reduced turnaround time and administrative burden on medical staff.
We replaced scattered communication tools with centralized clinical workflow automation software. When oncologists order tests or procedures, the system:
Built on Azure with C# Blazor for server-side rendering and Python FastAPI, the healthcare workflow automation system uses a PostgreSQL database for persistence and Azure Blob Storage for documents.
We chose Blazor for server-side rendering instead of client-side frameworks to improve initial load performance and simplify state management for healthcare apps where data consistency is critical. The platform leverages Azure App Service's built-in AD integration, automatically handling authentication redirects and headers without custom code.
We separated original documents and OCR/AI outputs into two Blob Storage containers with hierarchical paths. This enabled independent scaling, different retention policies, and simplified access control. Instead of using Azure's OCR services, we built a custom Python pipeline with open-source libraries that delivered comparable accuracy at significantly lower cost for processing thousands of documents monthly.
We designed a comprehensive billing platform to replace the legacy RCM system. The architecture supports current scale and accommodates growth as RCM and call center projects reach production. The AI infrastructure enables adding new capabilities without major architectural changes.
The RCM system manages claim lifecycle: generating medical codes from clinical notes, submitting claims to insurers, tracking reimbursement status, and providing visibility across 10 billing teams.
It serves 40-50 users managing ~$200M in annual revenue, which requires enterprise-grade reliability, security, and audit capabilities. Our team successfully migrated data from legacy systems (Integra, existing RCM) without revenue disruption or processing delays.
Currently we are working on the inbound call center system. This call center integrates conversational AI for routine patient inquiries (appointment confirmations, scheduling, basic questions). The system will autonomously resolve queries and create structured tickets with conversation summaries for human staff.
Ready to discuss your software engineering needs with our team of experts?