Hi, I'm Julien

Clinical Orthotist · Systems Engineer · MedTech
Healthcare systems · Edge · Embedded · Physical devices

I am a state-qualified orthotist with four years of clinical experience in France and Canada, followed by a second path into software engineering, Linux systems, edge computing, electronics, and embedded technologies.

I build systems that connect:

clinical needs, software, infrastructure, and physical equipment.

Since January 2026, this self-managed Gitea instance has been my primary environment for active development, infrastructure repositories, technical documentation, and CI/CD workflows.

---

My direction

My work is progressively specializing in healthcare and medical technology.

I am particularly interested in systems that improve:

• clinical workflows;
• medical device integration;
• mobility and rehabilitation;
• autonomy and assistive technologies;
• local and secure healthcare infrastructure;
• communication between software and physical equipment;
• measurement, instrumentation, and real-world deployment.

My long-term direction is to contribute to non-invasive technologies that assist or restore human function.

---

Clinical background

Before working in software and systems engineering, I spent four years as a clinical orthotist.

My work included:

• patient assessment and biomechanical analysis;
• design and fabrication of custom orthoses;
• casting, thermoforming, fitting, and finishing;
• device adjustment and patient follow-up;
• collaboration with physicians, surgeons, and physiotherapists;
• understanding comfort, morphology, materials, and real-world use.

This experience remains central to the way I approach engineering.

A technically successful device is not necessarily a useful device. It must also fit the user, the environment, the clinical need, and the actual workflow.

---

Systems and engineering background

I later trained in software development and progressively moved toward systems engineering and technologies closer to the physical layer.

My current areas of work include:

• Rust systems and backend development;
• Linux-based systems;
• edge and on-premise infrastructure;
• communication with physical devices;
• embedded and IoT experimentation;
• secure deployment and remote maintenance;
• system integration and interoperability;
• technical documentation and reproducible deployment.

I prefer projects where software has a direct effect on a device, a process, or a real-world environment.

---

Enuxia Health

I co-founded Enuxia, a technology project now specializing in healthcare systems.

Enuxia aims to design, integrate, secure, and maintain systems connecting:

• healthcare software and data;
• local and edge infrastructure;
• APIs and interoperability layers;
• physical equipment;
• sensors and embedded systems;
• professionals and real-world workflows.

The technical core includes:

• Linux and local services;
• containerization and automated deployment;
• edge computing and offline operation;
• integration and interoperability;
• secure networking and observability;
• embedded systems, firmware, and device protocols.

The project is being developed progressively, from healthcare infrastructure and system integration toward clinical instrumentation, assistive devices, and active orthotics.

---

Current work

Production Rust systems

Design and deployment of systems using:

• Rust;
• Axum;
• Tokio;
• WebSocket communication;
• real-time decision logic;
• communication with physical readers and devices.

One production system is currently used by an institutional client and connects backend software with equipment deployed in the field.

Healthcare edge infrastructure

Work around:

• Linux-based local servers;
• Docker and service orchestration;
• Proxmox virtualization;
• secure VPN access;
• monitoring and remote maintenance;
• Raspberry Pi and edge nodes;
• offline and locally controlled architectures;
• healthcare-oriented self-hosted services.

Embedded and physical systems

Projects and experimentation involving:

• microcontrollers;
• embedded Linux;
• GPIO;
• sensors;
• communication protocols;
• hardware integration;
• firmware;
• test benches;
• diagnostics and observability.

Digital health education

I also teach digital health topics to Bachelor’s and Master’s students.

Topics include:

• connected medical devices;
• cloud versus edge computing;
• health data sovereignty;
• healthcare cybersecurity;
• interoperability;
• artificial intelligence in healthcare;
• medical device regulation.

---

Technical interests

Systems programming

Rust C Python Linux Axum Tokio

Communication and integration

WebSocket MQTT REST APIs GPIO Device Protocols

Infrastructure and edge

Docker Proxmox Traefik VPN Git CI/CD Raspberry Pi

Embedded and hardware

Embedded Linux Microcontrollers Sensors Electronics IoT

Healthcare and MedTech

Orthotics Biomechanics Medical Devices Digital Health
HL7 / FHIR concepts DICOM concepts Health Data Protection

Applied AI

Local inference and AI may be used when they provide a measurable benefit, particularly for local processing, decision support, or device-related workflows.

They are tools, not the core identity of the project.

---

Engineering principles

Usefulness before technology

No sensor, AI model, or connected feature should be added only to make a system appear innovative.

Field reality matters

A system must work with real users, real devices, imperfect networks, maintenance constraints, and existing workflows.

Local control when it matters

Healthcare systems may require privacy, offline capability, predictable operation, and reduced dependence on external cloud services.

Progressive complexity

Start with a limited and useful system. Validate its value before increasing technical or regulatory complexity.

Honest engineering

Clearly distinguish between:

• production-ready work;
• prototypes;
• experiments;
• skills currently being developed;
• long-term ambitions.

---

Repository organization

This Gitea instance is used for:

• active development repositories;
• infrastructure-as-code;
• Docker and deployment configurations;
• CI/CD workflows;
• embedded and edge projects;
• internal tools;
• technical documentation;
• prototypes and research work.

Some repositories may remain private because they contain client-specific, infrastructure, security, or early-stage project information.

Selected public projects may also be mirrored on GitHub for professional visibility.

---

External profiles

---

Building healthcare technology that understands the field, the device, and the person using it.