Skip to main content

Parthenon Goes Global: Comprehensive i18n Extraction Across the Full Workflow Suite

· 5 min read
Sanjay M. Udoshi MD
Creator, Parthenon
Claude (AI Pair Programmer)
AI Development Assistant

Today was a focused, high-volume internationalization push across Parthenon — thirteen commits dedicated entirely to extracting i18n strings from nearly every major workflow surface in the platform. If you've been waiting for the day Parthenon could speak your language (literally), we made a serious down payment on that today.

The Big Picture: Why i18n Extraction Matters​

Parthenon serves healthcare analytics teams across a wide range of institutions, many of which operate in multilingual environments or have compliance requirements around localization. Before today, much of the UI text was hardcoded inline, making translation impractical and maintenance inconsistent. The work done today lays the structural foundation for full locale support — extracting string literals into translation keys that can be mapped to any target language without touching component logic.

This isn't glamorous work, but it's foundational. Getting i18n architecture right early prevents a painful, bug-prone retrofit later. Today's sweep was comprehensive, touching virtually every major workflow and surface in the platform.

What Was Extracted Today​

Clinical & Investigation Workflows​

The investigation clinical workflows surface received extraction coverage, pulling out strings tied to cohort investigation, patient-level review, and clinical drill-down interactions. This is one of the more text-dense parts of the platform, with contextual labels, status indicators, and action prompts that vary depending on the analytical context.

HEOR & Outcomes Surfaces​

The HEOR (Health Economics and Outcomes Research) workflows were extracted, covering the study design, endpoint configuration, and results summary surfaces. Given that HEOR deliverables are often shared across international stakeholders, having these surfaces localization-ready is particularly meaningful.

ETL & Source Profiler Workflows​

ETL source profiler workflows had their strings extracted — covering data source configuration, mapping status indicators, profiling result displays, and validation feedback. This is a technically rich surface with a lot of state-dependent messaging, so the extraction here required careful attention to dynamic string patterns.

Morpheus Workflows​

The Morpheus module — Parthenon's cohort characterization and phenotyping layer — had its workflow strings extracted. Morpheus surfaces tend to involve a mix of technical OHDSI terminology and user-facing guidance text, making clean key naming here especially important for future translators.

Concept Set Workflows​

Concept set management workflows were extracted, covering the concept search, inclusion/exclusion rule builder, and set versioning interfaces. Concept sets are central to nearly every OHDSI analysis, so consistent, localizable labeling here has a wide downstream impact.

GIS and Tooling Workflows​

The GIS and tooling workflows extraction covers the geographic analysis surfaces and platform-level utility tooling. GIS in particular surfaces location-based health data, where locale-appropriate formatting and labeling is directly relevant to end users.

Publish: Care-Gap Risk Surfaces​

The care-gap risk surfaces under the Publish module were extracted. These surfaces present population-level risk stratification outputs to care management teams — audiences who may be non-technical and for whom clear, localized language is especially important.

Profiles & Patient Similarity Surfaces​

Patient profiles and similarity surfaces received extraction coverage. These are the patient-facing analytical views, where longitudinal records and similarity clusters are surfaced. String extraction here touched a mix of clinical vocabulary labels and UX copy.

Strategus Study Package Surfaces​

Strategus study package surfaces — covering the configuration, execution, and results review for OHDSI network study packages — were extracted. Strategus is a critical integration point for collaborative research, and having its surfaces localization-ready supports the global OHDSI network use case directly.

Imaging & Genomics Surfaces​

Finally, imaging and genomics surfaces had their strings extracted, rounding out the sweep. These are specialized analytical surfaces, but they carry the same obligation toward consistent, translatable UI copy as the rest of the platform.

Technical Notes for Future Developers​

All extraction follows the established i18n key namespace conventions in the codebase. When working in these modules going forward, do not add raw string literals to UI components — all new user-facing text should go through the translation hook (useTranslation or equivalent) from the outset. The extraction work done today establishes the baseline; new additions that bypass the pattern will create drift.

Pay particular attention to dynamic strings — messages that interpolate patient counts, dates, or status values. These require parameterized translation keys and should be reviewed carefully to ensure interpolation variables are correctly scoped in the locale files.

A follow-up pass to add default locale (en-US) values for all newly extracted keys will be needed before any translation vendor handoff can begin. That's the logical next step in this pipeline.

What's Next​

  • Populate default locale files — the extraction creates the key structure; the en-US baseline values need to be confirmed and completed for all newly extracted namespaces.
  • Translation vendor / community handoff — once baseline locale files are clean, selected locale targets (likely starting with Spanish and French) can be queued for translation.
  • i18n QA pass — automated and manual review to catch any missing keys, truncation issues, or RTL layout concerns in the affected surfaces.
  • Resume feature development — with the i18n scaffold now broadly in place, feature work can proceed with localization built in from the start rather than bolted on after the fact.

Today's work won't show up as a flashy demo, but twelve commits of steady extraction across the full platform is the kind of unglamorous infrastructure investment that pays dividends every time Parthenon reaches a new institution or market. Solid day.