🏆 For Judges / The maker
🧑 The maker · Wallonia × Shikoku

A solo project. A lived premise.

JemmaPass is built by one person in rural Belgium, drawing on three Shikoku Henro pilgrimages (2016–2023) and ten days as a solo volunteer in the Noto Peninsula earthquake response of January 2024. This page is the human context behind the engineering.

🧑
Claude
Claude Heyman
Solo developer · 三度の遍路 · independent build
🇧🇪 Wallonia, Belgium 📍 Couvin / Bruly-de-Pesche 🚶‍♂️ Henro × 3 (2016–2023) ⛑️ Noto 2024 volunteer · 10 days solo

Background. Software engineer with 20+ years building backend systems, AI integrations, and standards-compliant enterprise platforms. Currently working on ServiceNow development for the Belgian SPF Finances (federal finance ministry's external customer support portals), with JemmaPass developed independently on personal time.

Why this project. I have walked the 1,200 km Shikoku 88-temple pilgrimage three times — in 2016, 2017, and 2023 (the third pilgrimage being the year I met my future wife Misako, whom I married six months later in Japan). On each Henro I walked among pilgrims who carry chronic medication, who don't speak Japanese, who get separated from their group on remote mountain trails. The same fragility kept appearing: paper records get lost, cellular signal disappears in valleys, French-language ICE cards mean nothing to a Japanese ryokan owner or shrine warden. Pilgrims become medically illegible the moment they leave their home health system — and pilgrims are far from the only population in this situation.

The trigger event. On January 1, 2024, I was in Tokyo preparing to ship my wife's belongings to Belgium and finalize her visa, when the Noto Peninsula earthquake (M 7.6 JMA / M 7.5 USGS) hit. Ten days later I was on the ground in Himi (Toyama Prefecture), on the coast neighbouring the Noto Peninsula, as a solo volunteer registered with the Himi City Disaster Volunteer Support Center (氷見市災害ボランティア支えあいセンター) — sleeping in my rental car between shifts. I saw triage teams meet evacuees whose medication records were either buried under collapsed homes or stored in a cloud they couldn't reach because cell towers were down. I saw fluent Japanese rescuers struggle to communicate with foreign tourists. I came home with a question I couldn't shake: what would it take to make every patient legible to every rescuer, everywhere, with or without infrastructure?

The build. JemmaPass is the answer to that question, built in one month of focused development for the Gemma 4 Good Hackathon, drawing on prior R&D in on-device AI architectures (LiteRT, MediaPipe, edge inference) and refined through multiple AI Council review cycles (Gemini, ChatGPT, DeepSeek, Grok, AI Studio, Claude) for architectural validation. Every line is mine — every architectural decision is grounded in something I personally needed but did not have on Shikoku or in Noto.

🚶‍♂️ Three pilgrimages · 三度の遍路

What I learned walking 3,600 km (2016–2023)

1
First Henro · 2016

I walked alone, with no Japanese. Cellular signal disappeared for hours in the mountain valleys. I walked among pilgrims with chronic conditions improvising every day, foreign tourists with no way to communicate medical needs. The lesson: paper is fragile, language is a wall, and offline matters more than people realize.

2
Second Henro · 2017

Lower-density season, often no cellular signal for hours. I started experimenting with offline tools — pre-downloaded maps, offline translation apps, paper backups of everything. The lesson: connectivity is a luxury. Resilience starts with assuming the cloud isn't there.

3
Third Henro · 2023

This time I started thinking like an engineer. I sketched a notebook architecture for an offline health passport. I drew diagrams in temple courtyards. (This was also the year I met my future wife Misako, whom I married six months later in Japan — a personal note that shapes the Belgium ↔ Japan dimension of this project.) The lesson: this is buildable. The pieces exist. The fusion does not. I should make it.

4
Noto Peninsula earthquake · January 2024

I was in Tokyo preparing my wife's relocation to Belgium when M 7.6 struck. Ten days later I drove solo to Himi (Toyama Prefecture), on the coast neighbouring the Noto Peninsula, to volunteer with the local disaster response — sleeping in my rental car between shifts. The lesson: my hypothetical "what if a foreign pilgrim got hurt?" became a daily reality for hundreds of evacuees. I have a moral obligation to ship this thing.

Official volunteer badge issued by Himi City Disaster Volunteer Support Center (氷見市災害ボランティア支えあいセンター), activity date January 23, volunteer name クロード (Claude), issuing authority Himi Social Welfare Council.
📷 Volunteer badge issued by the 氷見市災害ボランティア支えあいセンター (Himi City Disaster Volunteer Support Center) — activity day 1月23日 (January 23) · volunteer name クロード (Claude) · issued by 氷見市社会福祉協議会 (Himi Social Welfare Council).
🛠️ How it was built

A solo personal project

JemmaPass is developed independently under my own name as a personal R&D project — not on behalf of any employer or organization. The intellectual property, source code, and submission belong to me personally.

My day job is ServiceNow development for the Belgian SPF Finances (federal finance ministry's external customer support portals on the Yokohama platform). JemmaPass is built on evenings, weekends, and personal time, completely outside the scope of that engagement. It draws on years of personal research into on-device AI architectures — LiteRT, MediaPipe, Gemma variants, edge inference patterns — accumulated before the Gemma 4 release made the architectural fusion technically feasible.

The thesis: privacy-preserving, edge-based, standards-compliant software is the future of consumer trust. JemmaPass collects no telemetry, runs no advertising, sells no data — by mission, not by promise.

🙏 Gratitude

Standing on the shoulders of giants

A solo project is never really solo. JemmaPass would not exist without the work of these people, projects, and communities.

🤖
Google DeepMind
Gemma 4 team
For shipping Apache-2.0 multimodal AI that genuinely runs on consumer devices. The April 2026 Gemma 4 release made JemmaPass technically feasible.
⚙️
LiteRT-LM team
Google AI Edge
For the native function-calling runtime that makes 68 typed @Tool surfaces possible. The miniaudio integration debugging guide saved my week.
🩺
HL7 IPS Working Group
FHIR R4 IG v2.0.0
For establishing a stable patient summary standard. Dave deBronkart ("e-Patient Dave") for the September 2024 Connectathon POC that proved patient agency was possible.
💊
DDInter team
Central South University
For curating and openly publishing 302,516 drug interactions in DDInter 2.0. Without this database, JemmaPass would have no clinical safety layer.
🌐
SNOMED International
IPS Free Set · July 2024
For the IPS Free Set under CC BY 4.0 with multilingual refsets. The 25+ language clinical display layer rests on their curation.
📚
NLM / UMLS
2025AB · RxNorm 2026-04
For the Metathesaurus and RxNorm — the cross-system terminology bridges that let SNOMED, ATC, and RxNorm interoperate cleanly.
🏛️
WHO Collaborating Centre · Oslo
ATC/DDD Index 2026
For maintaining the ATC hierarchy. The class-level allergy cross-reactivity logic in JemmaPass depends entirely on their taxonomic work.
🐉
Open Health Stack community
ohs-foundation
For the Kotlin FHIR data model (dev.ohs.fhir:fhir-model:1.0.0-beta03). The Apache-2.0 multi-platform FHIR library is foundational.
🤝
Anthropic Claude
AI Council member
For multi-cycle architectural reviews and the rigorous factual audit that caught and corrected several inflated claims before submission.
🛕
The 88 Shikoku temples
空海 · Kūkai · 弘法大師
For 1,200 years of welcoming the foreign pilgrim. The walking discipline of the Henro shapes how I think about software resilience.
⛑️
Noto Peninsula responders
January 2024 — ongoing
For the lessons in resilience under impossible conditions. JemmaPass exists because of what we collectively could not do that month.
🐢
妻 · my wife Misako
For her patience
For tolerating late-night build crashes, for explaining the cultural subtleties I'd miss, and for being the reason the Japan ↔ Belgium dimension of this project feels lived rather than imagined.

突破 · Toppa

The kanji 突破 (toppa) means "breakthrough" — literally "to pierce through". It signals that something previously closed is now open. JemmaPass is a small breakthrough for what offline health AI can do on a Pixel 9 today. It is not the final answer. It is a starting point.

If you've read this far — thank you. Whether or not JemmaPass wins a prize, it will continue to develop, and it will remain free for the pilgrims, the refugees, the grandmothers, and the volunteers it was designed for.

← Back to For Judges hub ⌨️ Source ↗ 💬 Discussions ↗