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.
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.
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.
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.
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.
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.
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.
A solo project is never really solo. JemmaPass would not exist without the work of these people, projects, and communities.
dev.ohs.fhir:fhir-model:1.0.0-beta03). The Apache-2.0 multi-platform FHIR library is foundational.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.