Skip to content

Codify/CodeLookup integration + @mieweb/ui upstream contributions (Doug directive 3) #310

Description

@Taleef7

What

Doug (2026-07-19 call): "your system should be using that Codify" — MIE's terminology database (terms → codes), surfaced as the Healthcare/CodeLookup component in the @mieweb/ui Storybook (stories: all-domains / conditions-only / meds-only / labs-only). Also: consider submitting WorkWell-built components upstream to @mieweb/ui.

Findings (2026-07-20)

  • CodeLookup is NOT exported by installed @mieweb/[email protected] — no healthcare subpath; 33 component dirs, none clinical. Storybook at ui.mieweb.org has the full Healthcare set (CodeLookup, HealthSurveillance, ConditionEditor, MedicationList, OrderEditor, ProblemList, AllergyList, Assessment, PresentingProblems).
  • npm carries dev prereleases (0.6.1-dev.167 latest) — probe them for the export; fallback = vendor per the ADR-007 datavis precedent, or ask MIE to publish (mirrors the standing @mieweb/datavis publish ask to Doug).

Plan

  1. Probe dev prereleases for a CodeLookup export (timeboxed).
  2. If available: wire into Studio ValueSetsTab (frontend/features/studio/components/ValueSetsTab.tsx) behind a UI flag; admin terminology-mappings form as follow-up; a backend /api/terminology/search proxy is future work.
  3. If not: docs/mieweb-ui-migration/CODELOOKUP_STATUS.md + upstream publish ask → Thursday talking point.
  4. Upstream-contribution candidates to propose: ChartDataTable (a11y chart tables), ComplianceChip/DeliveryChip chip-tier, RosterMobileCards, NitroGrid SSR-safe seam, OshaReferenceCombobox.

Wave: `docs/superpowers/plans/2026-07-20-doug-wave.md" (PR-7).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions