Healthcare workflow automation

Aktisea

Healthcare workflow platform for scheduling, reporting, and document-heavy operational processes.

Worked on Ma Visite Médicale in France, where workflow durability and admin clarity mattered more than feature volume.

Problem

Scheduling, reporting, and document handling had to stay predictable in a compliance-sensitive workflow where admin teams could not be blocked by PDF generation, email failures, or unclear status transitions.

My Role

Owned backend workflow logic in Symfony for scheduling and reporting flows

Designed API and admin-facing validation rules for sensitive workflow steps

Introduced async document and notification handling for long-running operations

Led code reviews and technical guidance across backend work

Approach

I moved compliance-sensitive rules into Symfony services, shifted document and notification work out of the request path, and made workflow state clearer for admin teams.

Impact

Stabilized reporting and document-heavy workflows in a compliance-sensitive healthcare environment.

Turned PDF and email failures into recoverable background work instead of blocking admin operations.

Reduced manual coordination across reporting, notifications, and document handling.

Made workflow state clearer for operators and easier to support in production.

Key Decisions

Centralized workflow rules in Symfony services -> kept compliance logic consistent across scheduling and reporting paths.

Moved PDF generation and notifications into background jobs -> prevented long-running tasks from blocking admin actions.

Exposed clearer workflow state in admin tooling -> reduced operator ambiguity around pending, failed, and completed work.

Kept validation close to backend workflow logic -> avoided rule drift across controllers and admin screens.

Medical workflow orchestration

Where workflow state is committed before document, email, and reporting side effects continue in the background.

flowchart LR
    A[Admin UI] --> B[Symfony Controllers]
    B --> C[Workflow Services]
    C --> D[(Scheduling & Reporting Data)]
    C -. queue .-> E[Async Worker]
    E --> F[PDF Processing]
    E --> G[Email Notifications]
    E --> H[Audit Trail]
    C --> I[Operational Status Views]

Solid arrows: synchronous requestsDashed arrows: async jobsPanels: admin-facing system surfaces

My Ownership

Owned backend workflow logic in Symfony for scheduling and reporting flows

Designed API and admin-facing validation rules for sensitive workflow steps

Introduced async document and notification handling for long-running operations

Led code reviews and technical guidance across backend work

Tradeoffs

Added more backend orchestration to keep admin behavior predictable.

Introduced background processing, which required stronger monitoring and clearer failure visibility.

What I’d Improve

Add richer retry strategy for document-processing failures with clearer failure classes.

Introduce distributed tracing across admin actions, workers, and notification delivery.

Add more explicit replay tooling for failed document and reporting jobs.