ePA & Service Apps
Two years in the PMO for electronic patient record development. Subsequently responsible for development subproject leadership, product ownership, requirements management and team leadership for service apps and digital public services.
From patient record development to leading service-app projects.
Two years in the PMO for electronic patient record development. Subsequently responsible for development subproject leadership, product ownership, requirements management and team leadership for service apps and digital public services.
From PMO to product ownership
I spent two years in the PMO for electronic patient record development: milestone planning and tracking in MS Project, checking deliverables, weekly status conversations and analysis of usage chains. In subsequent service-app and OZG projects, I became development subproject lead and later Product Owner, responsible for requirements management and team leadership.
What we built
Electronic patient and health records and an end-to-end service app based on a white-label solution tailored to the customer. Features included tracking tools, live-data monitoring, clearing centres and form generators. We digitised more than 30 administrative processes under Germany’s Online Access Act (OZG), working with statutory and private health insurers, executive boards, project leads, the steering committee, business departments, case workers and requirements managers.
The challenge
Features originally developed for other customers were sometimes unfinished or insufficiently documented. I investigated their capabilities and readiness, documented them and explained what was available and what still needed development. This created a clear catalogue of selectable features to support customer discussions and decisions.
How I work
As subproject lead and Product Owner, I also took on work beyond my formal responsibilities. When documentation was missing, questions remained unanswered or delivery stalled, I stepped in myself. My practical approach is to create clarity and help wherever the project needs it.
Delivery across organisational boundaries
I coordinated multiple development teams, partner companies and management, and helped develop the project management approach. This included templates for development-ready requirements, cross-team release planning, testing and go-live support. Project references highlight precise specifications, dependable coordination, ownership and the ability to motivate teams.
Responsibility throughout delivery
Across several projects: two years in the patient-record PMO, followed by subproject leadership and product ownership for service apps and OZG processes. These roles were not all held simultaneously.
PMO & Product Ownership · Cross-phase responsibility from concept to operations
- 01
Concept
Analyse usage chains, clarify value and priorities.
Analysis · Prioritisation - 02
Requirements
Translate business needs into development-ready requirements.
Requirements management - 03
Development
Plan across teams and coordinate dependencies and deliverables.
Subproject leadership · Cross-company team leadership - 04
Test & release
Support testing and release planning; resolve open questions.
Subproject leadership - 05
Go-live
Support launches and align the people involved.
Subproject leadership - 06
Operations
Feed insights from live operations into further development.
Coordination · Further development
Feedback: insights from testing and delivery inform requirements and priorities.







