Laying the Groundwork for Global Reach: Internationalization Across Parthenon's Module Suite

Today was a focused, deliberate sprint on one of the more foundational — and often underappreciated — aspects of building a platform meant to serve researchers worldwide: internationalization (i18n). Across 17 commits, we drafted locale files for ten distinct Parthenon modules, setting the stage for multilingual support throughout the platform.

Internationalization Push: Ten Modules, One Day

If you've been following the Parthenon roadmap, you know that i18n has been sitting in the backlog long enough. Today we made a serious dent in it. The work centered on drafting locale string files for a broad swath of the platform's module surface area — essentially creating the translation scaffolding that will allow Parthenon to be localized into additional languages as the platform matures and its user base expands internationally.

Here's a breakdown of which modules received locale drafts today:

Concept Sets

The Concept Set module is foundational to almost every OHDSI workflow — it's how researchers define the clinical entities they're studying. Getting the i18n keys right here matters because labels, tooltips, and validation messages in this module surface constantly during analysis setup. Today's draft captures the core UI strings for concept browsing, editing, and inclusion/exclusion rule management.

GIS Tools

The GIS Tools module enables geographic analysis of patient populations and outcomes — a capability that becomes especially important for population health and care gap research. The locale draft here covers map layer controls, region selection UI, and spatial filter terminology.

Morpheus

Morpheus handles patient-level prediction and machine learning model integration within the OHDSI ecosystem. The locale strings drafted today cover model configuration panels, performance metric labels, and prediction output displays — areas that tend to have dense, technical terminology that translators will need careful context for.

Imaging Genomics

The Imaging Genomics module sits at an exciting intersection of modalities. The i18n work here is particularly nuanced — genomic and imaging terminology doesn't always translate cleanly across languages, so the English source strings were drafted with that challenge in mind, keeping labels descriptive and avoiding overly idiomatic phrasing.

Standard PROs

Patient-Reported Outcomes (Standard PROs) have their own i18n complexity: the underlying instruments (like PHQ-9 or EQ-5D) are often already translated by their publishers, but the platform UI wrapping those instruments needs its own localization layer. Today's draft addresses the container UI — survey assignment, response tracking, and reporting views.

Strategus

Strategus is the OHDSI orchestration framework that coordinates multi-step analysis packages across nodes. The locale draft here covers pipeline configuration, execution status, and results aggregation panels — all areas where clear, precise language is critical for researchers coordinating distributed studies.

Publish Care Gap

The Publish Care Gap module allows teams to surface care gap findings to downstream stakeholders. The locale strings drafted today focus on the publication workflow — defining gap criteria, reviewing findings, and exporting reports.

Profile Similarity

Profile Similarity enables cohort comparison and patient phenotyping by similarity metrics. The i18n work here covers the comparison configuration UI and similarity score visualization components.

Analysis Wave

Analysis Wave is the orchestration layer for scheduling and sequencing analytical jobs across the platform. Today's locale draft captures the wave configuration interface, dependency graph labels, and execution timeline views.

Cohort Definition

Rounding out the day, Cohort Definition locale strings were drafted — covering the inclusion/exclusion criteria builder, concept set references, and cohort metadata fields. Given how central cohort building is to every OHDSI study, getting these strings right early is a high-leverage investment.

---

Why This Work Matters

It's easy to deprioritize i18n until "later" — and then find yourself refactoring hundreds of hardcoded strings under deadline pressure. By drafting locale files now, while modules are still actively evolving, we're establishing a clear contract between the UI components and the translation layer. Future developers adding features to any of these modules now have a home for their strings from day one.

It also signals something broader about where Parthenon is headed: this is a platform being built for the global OHDSI community, which spans research institutions across dozens of countries. Multilingual support isn't a nice-to-have — it's a prerequisite for genuine global adoption.

---

Technical Notes for Future Contributors

• All locale files follow the standard {module}/locales/{lang}.json structure. When adding new UI strings to any of these modules, make sure the corresponding key is added to the locale file — don't hardcode display strings directly in components.
• The draft locale files currently contain English source strings only. They are intentionally structured to make handoff to professional translators (or community contributors) straightforward.
• Pay attention to string interpolation patterns — several modules use parameterized strings (e.g., "Showing {{count}} results") and translators will need context notes for those tokens.

---

What's Next

With locale scaffolding now in place for ten modules, the logical next steps are:

1. Audit remaining modules that don't yet have locale drafts and bring them up to parity.
2. Wire locale files into the i18n runtime — ensuring the platform's translation loader actually picks up these new files and that language switching works end-to-end.
3. Community translation kickoff — once the English source strings are stable, we can open up the locale files for community contributions from the broader OHDSI network.
4. Terminology review — particularly for Imaging Genomics and Morpheus, a domain expert review of the source strings before translation begins would reduce rework downstream.

It was a quieter day in terms of visible feature work, but the kind of foundational investment that pays dividends across every future release. More tomorrow.