Milestones
List view
CIEL runs fully on the launched platform. (Scope being defined week of 2026-09-15 with Andy + Filipe.)
Due by November 5, 2026•0/1 issues closedCIEL publication model works for users in the new tools. (Scope being defined week of 2026-09-15 with Andy + Filipe.)
Due by October 15, 2026•0/1 issues closedCIEL public face is ready for launch traffic and the joint announcement. - CIEL-branded org page live - CIEL+OCL announcement published
Due by September 24, 2026•1/2 issues closedMapper is a generally available product with subscription-gated AI. - Community and OCL Online editions integrated with the AI Assistant
Due by November 5, 2026Teams can run real, large mapping projects with AI assistance. - Team projects with roles; >1k-row projects perform - Decision memory and concept proposals working end-to-end
Due by October 15, 2026•0/9 issues closedAnyone can try the Mapper immediately, within a safe free limit, with no waitlist. - $match open beyond mapper-approved; preview limit enforced - A preview entry point on the site
Due by September 24, 2026•0/12 issues closedTBv3 is open to all users, with team and usage capabilities visible. - User groups, roles, permissions surfaced in the UI - Users can see their own usage - Alpha-blocking feedback resolved
Due by October 15, 2026•0/2 issues closedReal users can do their everyday work in TBv3 without being forced back to TBv2. - Authoring parity where TBv2 users depend on it — concepts, mappings, repos - v2↔v3 coexistence and a path that invites users over - No dead-ends or data-correctness errors in core browse/author flows
Due by September 24, 2026•32/36 issues closedImplementation of the HEAD-link linked source workflow, enabling collection owners to author content in their collection and see new source concepts immediately — without a release cycle between every edit — then transition cleanly to a locked released version on publish. --- ## Showcase Workflow The PIH team manages the **PIH Dictionary**: a collection that references concepts from the **PIH Source** (content they own and create) and from **CIEL** (referenced but not owned). **The problem today:** When a clinician requests a new concept, the team must add it to PIH Source, release a new PIH Source version, and only then reference it in the collection. The forced release cycle between every authoring action drives teams back to managing content in the source directly, bypassing the collection entirely. --- ### Setup In the PIH Dictionary collection settings, the team designates **PIH Source** as a linked source with HEAD-link enabled. Because PIH Source and PIH Dictionary share the same owner, no special authorization is needed. --- ### Phase 1 — Authoring 1. A clinician requests a new "Viral Load Result" concept with answer options. 2. The dictionary manager opens the **PIH Dictionary** collection and adds the new concept through the collection UI. 3. Behind the scenes, the concept is created in **PIH Source HEAD**. A reference is added to the collection HEAD simultaneously. 4. The dictionary manager views the collection — the new concept is **immediately visible** in the expansion. No source release required. 5. CIEL references in the same collection continue resolving to their pinned released version (CIEL v2026-01), unaffected. 6. The team repeats this for as many concepts as needed, working entirely within the collection view. --- ### Phase 2 — Releasing 7. When the team is ready to publish, the dictionary manager initiates a new PIH Dictionary version. 8. OCL runs a pre-flight check: does the collection reference any PIH Source content that exists only in HEAD (not yet in a released PIH Source version)? - **No unreleased content referenced:** the collection publishes immediately, locking PIH references to the latest released PIH Source version. Done in one step. - **Unreleased content referenced:** a warning appears — *"PIH Source has N concepts referenced here that have not been released yet. Release PIH Source first, then return to publish the collection."* 9. The dictionary manager releases PIH Source (e.g., as v19.3). 10. OCL re-evaluates the collection expansion: all references that were resolving to PIH Source HEAD now lock to PIH Source v19.3. CIEL references remain at v2026-01. 11. The PIH Dictionary is published as a new version. All references resolve to stable, reproducible released versions. --- ### What the user never has to think about - The fact that their dictionary is backed by a source at all — the collection *is* the dictionary - Manually coordinating source and collection releases in the right order - Why new concepts aren't showing up (they do, immediately)
Overdue by 2 month(s)•Due by July 13, 2026•1/10 issues closedFollows up on [CIEL Bridge] [ICD11 E2E on pre-publication dataset](https://github.com/OpenConceptLab/ocl_issues/milestone/51) Similar idea but with Sunny's post-vacation fixes
Overdue by 1 month(s)•Due by July 31, 2026•4/5 issues closed**Goal:** Repeat the ICD-11 E2E evaluation workflow on a real-world country-level dataset (rather than the curated sample dataset used in March), testing the pipeline at greater scale and linguistic/clinical diversity. Results inform the WHO ICD-11 connectathon preparation in May. **Demo Driver:** Joe **Steps:** 1. Obtain and prepare the country-level input dataset (e.g. a national concept dictionary or local mapping dataset from a partner — MSF, Arogya Sri Lanka, or similar) 2. Pre-process dataset as CSV for OCL Mapper input 3. Start a new project in OCL Mapper: - Target repo: `WHO / ICD-11-WHO` - Algorithms: CIEL Bridge, WHO ICD-11 automatch, LLM-as-terminologist - Reranker + AI Assistant enabled 4. Run Auto-match across all algorithms 5. Export results and evaluate: - Re-ranked score distributions - AI Assistant recommendation quality - Cases where algorithms agree/disagree - Human expert spot-check on high-confidence and low-confidence cases 6. Document findings in an evaluation summary 7. Identify issues to resolve before the May connectathon
Overdue by 1 month(s)•Due by July 31, 2026•1/4 issues closedLearning from past mapping decisions to improve auto-match Showcase Story: Demonstrate how OCL Mapper learns from user decisions: 1. Mapper works through dataset, making mapping decisions 1. System captures decisions via #2317 (user accepts/rejects suggestions) 1. Matching memory builds up via #2066 (CAG algorithm learns) 1. New mapping project starts 1. Auto-match uses previous decisions to improve suggestions 1. Mapper sees "Previous Mapping Decisions Panel" (#2102) showing relevant past decisions 1. Accepts suggestion based on past decision → faster, more confident mapping
Overdue by 2 month(s)•Due by June 26, 2026•0/2 issues closedRequesting new concepts or changes when terminology gaps are found (potential candidate for downscoping - may not be fully complete by end of July) Showcase Story: Demonstrate the complete concept proposal workflow: 1. Mapper encounters term that doesn't exist in CIEL 1. Searches thoroughly, confirms concept doesn't exist 1. Creates concept proposal with justification and suggested mappings 1. CIEL maintainer receives notification 1. Maintainer reviews proposal, discusses with submitter via comments 1. Maintainer approves proposal → concept created in CIEL 1. Mapper receives notification and can now map to new concept 1. Mapper saves mapping to their local collection (#2352)
Overdue by 2 month(s)•Due by June 30, 2026•2/2 issues closedTheme: Managing collections when dependencies update (responding to new CIEL releases) Showcase Story: Demonstrate how a CIEL implementer responds to a new CIEL release: 1. Receives notification that CIEL v2026-04 is released 1. Reviews changes via dependency notification system 1. Uses linked source to test new version without committing 1. Previews impact on their collection (before/after comparison) 1. Decides to update via collection dependency update workflow 1. Applies update and creates new collection version 1. Downstream users are notified of collection update
Overdue by 2 month(s)•Due by July 9, 2026•15/23 issues closedCollaborative mapping with team features and improved queue management Showcase Story: Demonstrate how a mapping team collaborates on a large project: * Project manager sets up team project with roles (using User Groups #127) * Assigns rows to different team members * Team members customize their workspace (columns, left panel grouping) * Mappers work simultaneously with smart locking and conflict prevention * Team discusses challenging mappings via enhanced discussion threads * Manager tracks progress via team dashboard * Quality reviewer approves batches of work
Overdue by 3 month(s)•Due by June 4, 2026•9/10 issues closedInitially developed by Italo Macedo (GoInterop), this Milestone is to add priority capabilities to the OCL FHIR Service (`oclfhir3`), like using the $resolveReference operation and multi-tenant support, and initial deployment to OCL Online.
Overdue by 7 month(s)•Due by February 15, 2026•1/2 issues closedTBv3 fully replaces TBv2, and TBv2 can be retired. - Full parity plus the places parity is not enough - v3 design-system refactors complete; canonical URL registry complete
Due by November 5, 2026•95/125 issues closed