Martin Jurkiewicz

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.

Portrait of Martin Jurkiewicz

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

  1. Nov 2025 – Present

    Technical Project Manager

    Own clinical AI capabilities across product, engineering and integration, from story definition and architecture through implementation, testing and release, contributing directly to products and technical components where useful. Focused on making hospital data usable through the integration suite and its on-prem Recare Gateway over HL7 v2, FHIR and APIs.

    Key achievements

    1. Ongoing

      Hospital integration delivery

      Improved FHIR compliance, reliability and pipeline stability for aftercare integrations, and owned requirements and delivery for the integration with one of Germany’s largest rehabilitation providers.

    2. Apr 2026 – Present

      Recare Operator

      Designed the full architecture and technical requirements for an attended RPA solution that writes data back into hospital systems where no API exists, including the execution API, security model and observability.

    3. Jul 2026

      Healthcare Hackathon winner

      Built an AI prototype that pre-fills the mandatory German stroke registry questionnaire, with 71 fields across 11 sections, from hospital FHIR data using source highlighting and confidence indicators.

    4. May 2026

      Realistic FHIR test environment

      Built a Medplum-based demo KIS with a FHIR server on AWS and Docker, a HIS-like interface, and an AI pipeline that generates complete synthetic-patient FHIR bundles for end-to-end tests and demos.

    5. Feb – Apr 2026

      Recare Voice

      Served as interim Product Manager and deputy Tech Lead, building the clinical AI scribe from zero to its first pilot and its DMEA demo.

    6. Jan – Feb 2026

      AI suite integration

      Defined and implemented the integration architecture for structured and unstructured clinical data in LLM workflows. The pilot now runs in three hospitals of one of Germany’s largest hospital groups, with rollout planned for more than 80.

  2. Oct 2024 – Nov 2025

    Senior Solution Designer, Interoperability

    Led development of HL7 FHIR APIs on Oracle Cloud Infrastructure and medical terminology support for the i.s.h.med EHR, enabling regulated app and service integration.

    Key achievements

    1. Jun – Aug 2025

      First i.s.h.med Interoperability pilot

      Led the first pilot implementation of i.s.h.med Interoperability at Universitätsklinikum Würzburg (UKW).

    2. Jun 2025

      ISiK level 3 attestation

      Led i.s.h.med Interoperability, the product’s FHIR API, to ISiK level 3 attestation by gematik.

  3. Oct 2022 – Oct 2024

    Application Designer, Clinical Systems

    Designed and delivered clinical applications for operating-room documentation, additional medical master data and patient exports, integrated across the Helios i.s.h.med ecosystem.

    Key achievements

    1. 2024

      Clinical master-data application

      Designed and built a new application from scratch to document additional clinical master data, including pregnancy status and therapy limits, with integration across the entire Helios i.s.h.med ecosystem as a core requirement.

    2. Q4 2023 – Q2 2024

      Pre-anaesthesia assessment documentation

      Led the design and delivery of a new digital pre-anaesthesia assessment workflow for operating-room care.

    3. 2023

      ZGK segment in i.s.h.med MCI

      Led the implementation of the new ZGK segment in the i.s.h.med Medical Communication Interface.

    4. Continuous

      Helios Patientenexport

      Led multiple releases of the Helios patient-export capability.

  4. May 2020 – Oct 2022

    SAP Consultant, i.s.h.med

    Support hospital digitalization from inside the clinical application landscape.

    Key achievements

    1. 2020 – 2022

      Clinical application consulting

      Consulted on i.s.h.med clinical applications and hospital digitalization, grounded in day-to-day hospital operations and implementation constraints.

Contributions

  • pyrofile

    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.

  • agent-stuff

    A public collection of practical commands used in coding-agent workflows.

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.