Healthcare Partner & CRM Platform

Outcomes

Context

Healthcare B2B processes are long-lived; the platform must absorb new apps without collapsing into one unmaintainable monolith UI.

Challenge

Partner onboarding, CRM, customer care, and specialty operational tools were split across systems. Teams needed one platform family with clear app boundaries and shared infrastructure.

Approach

We delivered a multi-app Symfony/Monofony landscape behind nginx routing: partner service, CRM, customer care, admin, and a VM-oriented tool with Shopware order import. Docker/DDEV supported local development; front assets used modern progressive enhancement patterns.

Architecture

PHP Symfony multi-app monorepo, nginx path/host routing, Docker/DDEV, relational database, HTMX/Alpine/jQuery progressive UI, Shopware 6 integration for order import in specialty tooling.

Scope

• —Partner portal
• —CRM
• —Customer care
• —Admin
• —Specialty operational tool
• —Order import integration

Constraints

• —Regulated data handling expectations
• —Multiple personas and apps
• —Need to integrate with commerce order flows

Solution highlights

• —Multi-app routing instead of a single mega-admin
• —Shared platform practices with independent app evolution
• —Progressive frontends that stay maintainable

Technologies

Results

• —Multiple healthcare business apps on one engineered platform
• —Clear routing and ownership per app
• —Commerce import path for specialty operational tooling
• —Local environments that match multi-app reality

Lessons learned

• —Healthcare platforms need app boundaries as much as modules.
• —Import integrations should never own the core CRM domain model.
• —Progressive enhancement keeps complex B2B forms shippable.