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

Open
#310 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start with frontend/features/studio/components/ValueSetsTab.tsx and probe the @mieweb/ui dev prereleases for a Healthcare/CodeLookup export. Check docs/mieweb-ui-migration/CODELOOKUP_STATUS.md and the 2026-07-20 Doug wave plan for the fallback and upstream-publish path. Done means the integration path or fallback is documented, with the UI-flag scope and follow-up boundaries recorded.

Written by the indexing model from the issue text.

Description

frontend

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/ui@0.6.1 — 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).

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
6h 6m
Merged PRs (30d)
69

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Taleef7/workwell

All issues in Taleef7/workwell

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.