Freelance Integration Developer | Apache Camel + Quarkus LIS Integration Gateway

About Vitestro

Founded in 2017 in Utrecht, Vitestro is pioneering the future of blood collection with the Aletta® Autonomous Robotic Phlebotomy Device™ (ARPD™). This groundbreaking medical device combines advanced multi-modal imaging (near-infrared, ultrasound, and Doppler ultrasound) with robotics and AI to perform the entire diagnostic blood draw procedure autonomously.

By addressing critical healthcare staffing shortages and improving patient experience, Vitestro is transforming one of the most common and essential medical procedures. With more than 90 team members and growing rapidly, we are scaling our impact. As we placed our first devices with customers, we are now expanding our team to ensure successful implementation and long-term reliability.

At Vitestro, we are committed to continuous innovation and improvement.

The Assignment

Vitestro is building the LIS (Laboratory Information System) integration gateway that connects hospital laboratory systems to our venipuncture device platform. We have selected Apache Camel on Quarkus as the target architecture: a stateless, container-per-hospital gateway that can run centrally in AWS or on-premise at a hospital, with hard OS-level data isolation between tenants and zero-code onboarding of new hospitals via configuration.

Our internal Platform & Connectivity team does not have the capacity to deliver this build within our commercial timeline, so we are looking for an experienced freelancer/contractor (or small team) to build the initial gateway. A permanent Integration Engineer will take over operation, maintenance, and hospital-by-hospital rollout once the gateway is delivered — so a clean, well-documented handover is a hard requirement of this assignment, not an afterthought.

Key Deliverables

• Design and build the universal, stateless Camel + Quarkus gateway image: one codebase, hospital identity/config/transformations externalized and injected at container boot

• Implement the reliability properties required for clinical use: guaranteed delivery, idempotent consumption, redelivery and dead-letter handling, end-to-end traceability and replay, no silent data loss

• Implement the security and compliance baseline: hard container-level tenant isolation, mTLS with dynamic certificate retrieval from Secrets Manager, and the LogMasker component (PII/PPID/BSN masking before logs leave the container)

• Build the configuration-driven onboarding mechanism: hospital-specific JSON mapping tables and credentials streamed from S3/Secrets Manager at container startup, with zero code changes per hospital

• Deliver the gateway as a deployable OCI/Docker image, validated to run both centrally in AWS (ECS/Fargate) and — as a target capability — inside a hospital's own on-premise infrastructure

• Deliver a first working end-to-end connection to at least one GLIMS-based hospital as proof of the onboarding mechanism, to de-risk the "configuration, not code" claim before handover

• Set up CI/CD and infrastructure-as-code for the gateway, so environment and route configuration are version-controlled and reproducible

• Validate the published Quarkus native performance assumptions (boot time, idle memory footprint) against our actual route/component footprint, and flag any deviation from the architecture document's assumptions

Handover Requirements (critical)

• Full technical documentation of the gateway architecture, route structure, and configuration schema — written so an integration engineer without prior Camel exposure can maintain and extend it

• A working example/template for onboarding a new hospital, documented step by step

• Runbook for common operational scenarios: certificate rotation, failed delivery/dead-letter recovery, adding a new LIS variant

• Structured knowledge-transfer sessions with the incoming Integration Engineer before contract end

• Codebase and infrastructure-as-code left in a state that a mid-level backend engineer can operate without ongoing dependency on the contractor

Out of Scope

• Ongoing hospital-by-hospital rollout after initial validation (owned by the incoming Integration Engineer)

• Device/IoT fleet management (provisioning, OTA updates, telemetry) - separate workstream

• Long-term maintenance and support beyond the agreed handover period

This is a full-time engagement expected to run approximately three to six months, starting mid-September 2026. Technical delivery is targeted for end of 2026, followed by testing and stabilization through Q1 2027 to support go-live with our first Dutch GLIMS hospitals, with the engagement concluding around mid-March 2027. The project wraps up with a full handover of the integrations and runbooks to peers at Vitestro.

What You’ll Bring

• Proven production experience with Apache Camel, or demonstrable depth with a comparable enterprise integration framework (e.g. Spring Integration, MuleSoft, Red Hat Fuse) with genuine willingness and ability to ramp up on Camel quickly 

• Strong experience with Quarkus, or comparable experience with another JVM native-image/cloud-native framework (e.g. Spring Boot with GraalVM, Micronaut) 

• Solid Java backend development background 

• Experience with container-based multi-tenant architectures and OS-level isolation patterns 

• Experience with mTLS, certificate lifecycle management, and secrets management (AWS Secrets Manager or equivalent) 

• AWS experience: ECS/Fargate, S3, Secrets Manager, CloudWatch 

• Experience delivering in a regulated/compliance-sensitive environment (healthcare, finance, or similar) is a strong plus — GDPR/NEN 7510 awareness specifically 

  Demonstrated ability to write documentation and hand over cleanly to a team that will operate what you built — this assignment ends with a handover, not with you staying on
  

How We Work

At Vitestro, ownership is not a slogan - it is an expectation. We trust people to take responsibility, make decisions, and drive work forward.

We believe breakthroughs happen when talented people combine dedication, accountability, and teamwork. That means:

• We take initiative rather than wait for direction.
• We focus on execution and delivering results.
• We proactively remove blockers and help each other succeed.
• We challenge ideas, not people.
• We continuously learn, improve, and raise the bar.
• We celebrate team success over individual heroics.

We move fast, but we do so thoughtfully. We care deeply about quality because the technology we build ultimately impacts patients and healthcare professionals.

If you are looking for an environment where you can make a significant contribution, take ownership of meaningful work, and be surrounded by highly motivated colleagues, we'd love to meet you.

Practical information:

• Start: As soon as possible

• Duration: Start 6-month freelance assignment

• Location: Utrecht (hybrid).

• Workload: 32- 40 hours per week.

• Contract type: Freelance / Contractor.

• Language: English.

• Opportunity to be key shaper of a new global industry niche: autonomous medical robotics 

Are you excited? 

We totally understand that and so are we! By joining us, you can play an active role in changing the future of health care. Excited to join our revolution? Then we’d love to hear from you! 

For recruitment agencies – we are currently happy with the way we manage our process and fill our vacancies with our own efforts. Consider this as an answer to your offering via email, call, LinkedIn, etc. – we do not require your support now! Thank you.