MartinJurkiewicz
I work on healthcare products that have to survive contact with real systems, real workflows, and real people.
I build where healthcare meets reality.
I work where product decisions meet clinical workflows, integrations, and operations.
I started in medical physics and hospital systems, then moved into the products and integrations that make clinical data usable. That path gives me both the hospital perspective and the healthcare-software vendor perspective.
Today I own healthcare capabilities across product, engineering and integration, from requirements and architecture through implementation, testing and release. I work directly on the product when it helps, while keeping clinical stakeholders, delivery teams and technical decisions aligned.
After the API
The real integration starts after the API works.
APIs connect systems. The difficult work starts when products enter real workflows.
That means clear ownership, workable hand-offs, sensible exceptions and trust under operational pressure. What matters is whether teams can actually use what was built.
This isn’t theory. It comes from delivering hospital connectivity across HL7 v2 and FHIR, a regulated FHIR API attested against ISiK, and clinical AI taken from zero to its first pilot.
Start with the workflow. The exchange format is rarely the hardest part. Understand how people work before defining the integration.
Expose the trade-offs. Make scope, dependencies and technical constraints visible early enough for teams to act on them.
Keep the system aligned. Product, engineering, hospital IT and external partners need one shared picture of what is being delivered.
Design for production. Healthcare products have to survive regulation, rollout and daily operational use, not only a convincing demo.
Career
-
Nov 2025 – Present
Technical Project Manager
Make hospital data usable across Recare’s clinical AI suite.
Defined and implemented the AI suite integration architecture. The pilot now runs in three hospitals of one of the largest hospital groups in the German market, with rollout planned for more than 80.
Took Recare Voice from zero to its first pilot and its DMEA demo as interim Product Manager and deputy Tech Lead.
-
Oct 2024 – Nov 2025
Senior Solution Designer, Interoperability
Shape a regulated FHIR API on Oracle Cloud Infrastructure for the i.s.h.med ecosystem.
Led conception, implementation and attestation of the FHIR API against ISiK levels 2 and 3.
Owned medical terminology support and standards compliance for third-party integration with the i.s.h.med EHR.
-
Oct 2022 – Oct 2024
Application Designer & Clinical Systems Consultant
Turn hospital workflows into maintainable clinical software solutions.
Delivered updated operating-room documentation and implemented an i.s.h.med downtime concept.
-
May 2020 – Oct 2022
SAP Consultant, i.s.h.med
Support hospital digitalization from inside the clinical application landscape.
Consulted on i.s.h.med clinical applications and hospital digitalization work.
Contributions
- pyfhircheck
A public Python tool for FHIR R4 validation with evidence output and CI integration.
- cursor-plugin-cc
A public TypeScript plugin for using Cursor from Claude Code for review and delegated tasks.
- Healthcare Hackathon 2026
Winning AI prototype that pre-fills the 71-field German stroke registry questionnaire from hospital FHIR data.
Now
Right now at Recare, I’m focused on healthcare products that need to work across clinical workflows, FHIR and HL7 integrations, and real operational environments, including the careful integration of applied AI.
Start a conversation
If you’re working on a healthcare product that has to work beyond the happy path, I’d like to hear about it.
Get in touch