Systems architect — healthcare interoperability, IT cartography & infrastructure automation
Architecte SI · interopérabilité e-santé · cartographie du SI
I work at GCS SIRSCO, a French regional health IT consortium, where I design and run the information systems shared by several hospitals. Most of what I build lives at the intersection of three things: hospital interoperability, knowing exactly what you run (cartography), and automating the boring parts.
Everything here is either a tool I actually use in production or a sandbox I built to de-risk something before rolling it out.
- 🏥 Interoperability — HL7 v2 / MLLP, ADT & MDM flows, DICOM, EAI integration
- 🗺️ IT cartography — NetBox as the single source of truth: applications, business domains, flows, impact analysis
- 🔐 Security by default — mutual TLS on clinical flows, SSH hardening, authentication mapping for French digital-health compliance
- 🤖 Automation — Ansible, Docker Compose, reproducible stacks over click-ops
| Project | What it does | Stack |
|---|---|---|
| netbox-it-landscape | NetBox plugin bringing application-landscape cartography natively into NetBox: business/application/flow views, KPI dashboards, cascade impact simulator, REST API, EN/FR UI. | Python · NetBox 4 · Django |
| it-landscape | Standalone mapping tool for hospital information systems — business, application, network and flow views, incident simulation, data-quality center. | Next.js 15 · Zod · NextAuth · Docker |
| mllp-safetunnel | Secure HL7/MLLP tunnelling between an EAI and a hospital EHR using Stunnel and mutual TLS — no plaintext clinical data on the wire. | Python · Stunnel · mTLS · Docker |
| minimal-linux-ops-stack | Reusable Ansible baseline for Debian/RHEL provisioning, driven from a web UI (Semaphore + Gitea), with tag-scoped templates. | Ansible · Semaphore · Gitea · Docker |
Hospital IS architecture · HL7 & IHE interoperability · NetBox-driven cartography · securing clinical flows · making infrastructure boring and reproducible.