How one embedded team delivered React, React Native, and React Native Web inside a US healthcare product org, for 32+ months, without a separate delivery stream
A US network of clinics operated an in-house product engineering team responsible for developing and supporting a live healthcare platform spanning patient and clinician applications, a public website, mobile experiences, and TV applications used in clinics.
The challenge wasn't building another healthcare app from scratch. It was keeping an established product moving while the team had more work than its existing engineering capacity could absorb. Azati joined the team and contributed across React, React Native, and React Native Web, working on new patient and provider workflows alongside ongoing maintenance and tech improvements.
delivery disruptions; new engineering capacity integrated into the existing product process
patient and clinician experiences delivered across all application surfaces
months of continuous engineering contribution
Healthcare products rarely evolve one interface at a time. A change to scheduling, intake, or patient information can affect several user-facing surfaces at once.
The client's US healthcare ecosystem operated in a compliance-sensitive environment, bringing these workflows together across web and mobile applications, with additional TV experiences deployed in clinics. The broader product ecosystem also supported telehealth and telemedicine experiences alongside in-person care, patient scheduling, clinical workflows, and patient-provider communication.
Azati joined the established product organization to provide additional engineering capacity across React, React Native, and React Native Web while the internal team continued owning product direction and clinical priorities.
The client's product team needed to continue evolving a live healthcare platform while handling a broad range of feature and maintenance requirements.
The product supported workflows across appointment scheduling, patient intake, clinician interactions, patient information, and communication.
The product ecosystem included web and mobile applications, telehealth and telemedicine services, as well as TV experiences used in clinics, requiring frontend development across different environments.
The engineering backlog ranged from bug fixes and code improvements to substantial product features. Additional capacity allowed the existing team to handle this breadth of work within its established delivery process.
Azati introduced frontend unit testing with React Native Testing Library and Jest alongside normal feature delivery, giving the team repeatable coverage for frontend behavior as the application continued to evolve.
The team also contributed to the migration from REST APIs toward GraphQL using Apollo Client, supporting the platform's evolution while continuing to deliver product functionality.
Add React, React Native, and React Native Web engineers directly to your existing product team while keeping your roadmap, product decisions, and delivery process in-house.
Explore embedded healthcare engineeringThe work wasn't isolated to mobile or web. Because the product shared functionality across React Native and React Native Web, changes often had to work across both surfaces. Azati contributed within the existing product team, taking on both feature development and maintenance across the shared codebase.
Azati worked on the patient intake questionnaire experience, including branching questionnaires where subsequent questions depend on earlier answers. This allowed the product team to support more structured intake flows without treating every questionnaire as a separate interface.
Azati redesigned and extended the appointment-booking experience, evolving how patients find and schedule visits across the healthcare platform's web and mobile applications.
Azati implemented functionality for selecting a primary care provider, extending the patient-facing workflow within the existing app architecture rather than introducing a separate experience.
Azati contributed to functionality for viewing, updating, and applying patient vital information within the healthcare workflow. The work involved extending existing interfaces while keeping the implementation consistent with the shared application architecture.
Azati expanded frontend unit testing using React Native Testing Library and Jest, while also contributing to the migration from REST APIs to GraphQL with Apollo Client. These changes were introduced alongside normal feature delivery rather than as a dedicated modernization project.
Across 32+ months, Azati contributed to the product team's regular development workload, from bug fixes and maintenance to larger feature releases. Approximately 4,800 engineering hours were delivered across the engagement, with work prioritized alongside the client's existing roadmap and product team.
| Area | Delivery | Outcome |
|---|---|---|
| Patient intake | Branching patient questionnaires | More adaptable digital intake workflows within the existing patient application |
| Appointment scheduling | Scheduling redesign and new booking functionality | Continued evolution of patient-facing booking without introducing a separate scheduling experience |
| Primary care | Primary care provider selection | Expanded patient choice within the existing care-navigation workflow |
| Patient vitals | Functionality for viewing, updating, and applying vital information | Extended digital support for patient information workflows used within the existing product |
| Frontend engineering | Unit testing with Jest and React Native Testing Library; contribution to REST-to-GraphQL migration with Apollo Client | Testing and API-layer improvements introduced alongside normal feature delivery rather than through a separate modernization initiative |
| Cross-platform development | React, React Native, and React Native Web development across shared product surfaces | Feature changes could be evolved across web and mobile without splitting the work into separate frontend delivery streams |
| Embedded product capacity | ~4,800 engineering hours across 32+ months covering features, maintenance, and bug fixing | Additional engineering capacity absorbed into the client's existing product process without creating a separate delivery stream |
Before expanding the team, the client's product organization was balancing new patient features, ongoing cross-platform development, maintenance, and a frontend modernization backlog, all within the same engineering capacity.
Traditional hiring to expand capacity would have required an independent recruiting and onboarding cycle. Instead, the embedded model integrated engineering resources straight into the current product workflow, allowing development across React, React Native, and React Native Web to progress seamlessly alongside the client's roadmap.
Healthcare product teams don't always need another development process. They often need additional engineers who can enter an existing codebase, understand the workflow, and contribute at the same pace as the people already building it.
| Factor | Internal hiring | Freelance contractors | Embedded engineering partner |
|---|---|---|---|
| Ramp-up time | Months (recruiting and onboarding) | Weeks, but limited context retention | Days to weeks, with sustained product context |
| Cross-platform coverage | Requires multiple specialist hires | Each contractor covers one surface | One team covers React, React Native, and React Native Web |
| Product continuity | High, but expensive to maintain | Low. Context leaves when the contract ends | High. Sustained engagement with accumulated domain knowledge |
| Process integration | Native | Parallel (often creates a separate stream) | Embedded inside the existing delivery process |
When patient and clinician workflows share a React Native and React Native Web codebase, the engineering challenge isn't simply adding another developer. It's adding someone who can work inside the existing product and keep changes moving across surfaces.
Talk to Azati about your healthcare application| Priority | Why it matters |
|---|---|
| Shared web/mobile development | React Native and React Native Web can help an existing team evolve multiple frontend surfaces without splitting delivery across separate specialists. |
| Patient workflows | Scheduling, intake, provider selection, and patient information need to evolve around real healthcare workflows rather than generic application patterns. |
| Frontend quality | When one codebase serves patients, clinicians, web, mobile, and TV, you can't test it casually. Every change touches multiple surfaces, and the consequences of a regression are clinical, not cosmetic. |
| Sustainable engineering capacity | The point of an embedded model is that your team stays your team. You keep the roadmap, the product decisions, and the engineering culture. Azati adds capacity, not complexity. |
An embedded engineering model integrates external developers into the existing product organization, working within the same tools, backlog, development process, and delivery cadence as the internal team. This adds capacity without creating a parallel product organization and allows the client to retain ownership of product decisions and priorities.
Over a longer engagement, embedded engineers also build working knowledge of the product and its codebase, reducing the need to repeatedly onboard new external resources. In this 32+ month healthcare engagement, engineers worked alongside the client's existing developers, testers, managers, and designers on new functionality, maintenance, and bug fixes across web and mobile applications.
A shared cross-platform codebase can reduce the need to implement the same product logic independently for every client surface. React Native and React Native Web allow teams to reuse parts of an application architecture while adapting interfaces to mobile and web requirements where necessary.
This approach can be particularly useful for healthcare products that need to evolve patient and provider workflows across multiple channels. In this engagement, Azati contributed across React, React Native, and React Native Web within the existing product codebase, supporting functionality used across the client's web and mobile applications.
Digital patient questionnaires often need conditional or branching logic because later questions may depend on answers given earlier in the intake process. Designing this logic within the application allows questionnaires to adapt to different patient responses instead of forcing every user through the same fixed sequence.
The approach can make more complex intake workflows manageable while keeping the questionnaire experience within the existing patient application. Azati contributed to a patient questionnaire tool that supported branching flows, where responses to previous questions determined which questions appeared next.
Appointment scheduling can usually be evolved incrementally by extending the existing booking workflows, interfaces, and application architecture rather than treating scheduling as a separate product. This allows teams to introduce new booking functionality while continuing to maintain the surrounding patient experience.
For established healthcare products, incremental development is particularly relevant when scheduling is connected to other workflows such as provider selection and patient information. During the engagement, Azati contributed to the redesign and expansion of appointment scheduling functionality within the existing healthcare application.
Frontend testing helps product teams verify that existing behavior remains stable as applications become more complex and new functionality is added. Unit and component-level tests can provide repeatable checks around interface logic and reduce the need to rely exclusively on manual verification during ongoing development.
Introducing testing incrementally can be practical for established products where feature delivery cannot simply stop for a separate testing initiative. In this engagement, Azati contributed frontend unit testing using Jest and React Native Testing Library while continuing normal feature development and maintenance.
GraphQL can be useful when an application needs more flexible access to data across multiple frontend experiences and when teams want clients to request the fields required for a particular workflow rather than relying exclusively on fixed REST responses. The value depends on the application's architecture, data relationships, and existing API model; migrating to GraphQL is not automatically an improvement for every product.
In this engagement, Azati contributed to the migration from REST APIs toward GraphQL using Apollo Client while continuing development of the existing React and React Native applications.
Get a snapshot of our recent projects and see how Azati delivers measurable results for our clients.
A Danish digital healthcare provider needed to adapt its telemedicine offering for multiple insurance organizations with different branding, workflows, translations, and operational policies. Separate applications for each partner would increase delivery and maintenance complexity, while the platform also needed to support consultations, scheduling, eligibility, payments, notifications, and reporting.
Azati contributed to building a multi-tenant telemedicine backend from scratch, enabling multiple insurance organizations to operate on a shared codebase while retaining customer-specific configurations. The platform supports the consultation lifecycle, patient administration, provider scheduling, billing, communications, reporting, and continuous onboarding of new insurance partners.
The client needed to integrate multiple healthcare systems and data sources into a unified eHealth platform. However, they faced fragmented systems with incompatible data formats, manual data transfers between platforms, strict compliance requirements for sensitive health data, and unreliable cross-system synchronization. These issues created delays, increased operational overhead, and risked data inconsistencies in critical healthcare workflows.
Azati designed and implemented a secure integration layer that connects disparate healthcare systems into a unified platform. The solution standardizes data exchange using healthcare protocols, enables real-time synchronization across systems, ensures secure handling of sensitive medical data, and reduces manual intervention through automation. This creates a reliable, regulations-aware, and scalable integration ecosystem.
A healthcare company needed to unify Physician and Patient Records systems built on different database technologies while improving usability and supporting new healthcare workflows. The scale of the data and user base made migration, UI modernization, and system performance critical concerns.
Azati merged PostgreSQL and Oracle data into a unified structure, optimized internal Java logic, modernized the user interface, and added reporting and recruitment capabilities. The resulting system provided a single data foundation, smoother workflows, and improved performance for a large active user base.
Last updated
