List view
**Goal:** Demonstrate that the CIEL Content Curation objective is complete — all ~15,000 CIEL concepts have been through QA review for consistent naming, up-to-date mappings, and systematic fixes. Showcases the OCL AI Assistant concept QA workflow as a reusable, generalizable capability for other sources. **Audience:** Internal team + CIEL/OpenMRS community; potential manuscript/publication content **Demo Driver:** TBD **Steps (proposed):** 1. Show the CIEL QA work queue — confirm it is empty / all concepts marked as reviewed 2. Walk through before/after examples of curated concepts: - A concept where casing was fixed - A concept where a missing ICD-11 mapping was added - A concept where a deprecated mapping was retired 3. Show aggregate statistics: how many concepts reviewed, how many mappings added/fixed, how many deprecated mappings retired 4. Demonstrate the OCL AI Assistant concept QA workflow (Tracker 57) as a standalone reusable tool: - Pick a concept from a different source (non-CIEL) - Run the AI Assistant QA check - Interpret the output and show how a user would act on it 5. Discuss what CIEL being a "more effective bridge terminology" means in practice — show a mapping project benefiting from the improved CIEL content
Due by June 25, 2026**Goal:** Showcase CIEL functioning as a bridge terminology for all supported target repositories — ICD-11, LOINC, and others — using the complete multi-algorithm matching pipeline. Demonstrates the value of CIEL as an intermediary that extends mapping expertise to reference terminologies. **Audience:** Internal team + potential WHO, HL7, and implementer stakeholders **Demo Driver:** TBD **Steps (proposed):** 1. Open OCL Mapper and create a new project with a CIEL-based input dataset 2. **ICD-11 target demo:** - Configure: CIEL Bridge + WHO automatch + LLM-as-terminologist + reranker + AI Assistant (ICD-11 tailored prompts, Tracker 4) - Run auto-match and review grouped candidates by algorithm - Show sorting by re-ranked score across algorithms - Open a candidate and show ICD-11 hierarchy context (Tracker 56) 3. **LOINC target demo:** - Reconfigure project for LOINC target - Run auto-match with CIEL Bridge + semantic search + AI Assistant (LOINC tailored prompts) - Show AI Assistant output with LOINC-specific guidance 4. Walk through the "smart candidate pool formatting" feature — show how the pool is trimmed to fit within LLM context windows (Tracker 4) 5. Show the metadata displayed to users about how each candidate was generated (which algorithm, score, etc.) 6. Demonstrate how results can be saved to a collection (Tracker 40)
Due by June 11, 2026- Due by June 11, 2026
**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
Due by April 30, 2026•0/2 issues closed**Goal:** Demonstrate the complete Future State CIEL release workflow, managed entirely through CIEL Labs v2 and the OCL Terminology Server — replacing the legacy 10-step pipeline involving MySQL, Liquibase scripts, ocl_omrs, and manual interventions. **Demo Driver:** Filipe **Steps:** 1. Make a set of concept edits/additions in CIEL Labs (representing a typical CIEL update cycle) 2. Run QA checks using CIEL Labs (Tracker 42) — confirm no validation errors 3. Initiate a new repo version release on OCL production (Tracker 43): - Review the automated change log generated for this version (Tracker 45) - Release the version 4. Convert the latest CIEL export to required mysqldump formats for legacy Dropbox distribution (Tracker 47): - OCL export → OCL Module → CIEL Admin (OpenMRS v1.11) - Generate mysqldump from CIEL Admin - Run Liquibase scripts from the new mysqldump 5. Upload the mysqldump files to Dropbox for supported OpenMRS versions 6. Verify the new CIEL version is live in OCL production and browsable in TBv3 7. Compare total steps and time against the legacy 10-step workflow — document the delta
Due by April 16, 2026**Goal:** Demonstrate that CIEL source management QA workflows now run fully within CIEL Labs v2 connected to the OCL API backend — replacing the legacy MySQL-based QA scripts. Specifically demonstrates the OpenMRS Validation Query and real-time validation schema. **Demo Driver:** Andy **Steps (proposed):** 1. Open CIEL Lab v2 and navigate to the source management / QA section 2. Run the OpenMRS Validation Query against the current CIEL HEAD: - Show which concepts fail validation and why - Walk through the error categories (e.g. missing required fields, invalid mappings) 3. Demonstrate real-time validation schema feedback: - Open a concept for editing - Introduce a validation error (e.g. remove a required field) - Show the inline validation error appearing in real time - Fix the error and confirm it clears 4. Show the batch concept + mappings REST API — create/update a concept with its mappings in one request (Tracker 46) 5. Demonstrate the automated change log for a new repo version — show what gets recorded automatically when a change is made (Tracker 46) 6. Compare this to the old workflow (step 2 of the current state: "Run QA checks directly on MySQL backend") and highlight what's been eliminated
Due by April 2, 2026**Goal:** Showcase the end-to-end technical workflow for CIEL content curation using CIEL Lab v2 — specifically the QA review workflow for the ~15,000 CIEL concepts remaining for review. Demonstrates how the OCL AI Assistant concept QA workflow can be used as a reusable tool. **Demo Driver:** Filipe **Steps (proposed):** 1. Open CIEL Lab v2 and navigate to the QA work queue 2. Apply filters to identify concepts needing review: - Concepts with casing issues (e.g. inconsistent capitalization) - Concepts missing ICD-11 mappings - Concepts with deprecated mappings 3. Select a batch of concepts to review 4. For a **casing issue**: run the deterministic casing fix script, review output, apply correction 5. For a **missing mapping**: - Open the concept in CIEL Lab - Use the semantic search / MedEmbed small suggestions to find candidate mappings - Optionally, use the OCL AI Assistant to evaluate the candidates - Accept or reject a mapping suggestion and save 6. For a **deprecated mapping**: show how the script identifies deprecated entries and how CIEL Lab surfaces them for review/retirement 7. Show the "second review" (peer review) step for flagged concepts 8. Demonstrate the AI Assistant concept QA check as a reusable workflow (Tracker 57) — run it on a concept and interpret the output 9. Show how completed concepts are marked as reviewed and removed from the work queue
Due by April 2, 2026Goal: Run the full ICD-11 E2E evaluation workflow on a prepared validation/sample dataset and produce a repeatable evaluation of re-ranked scores and AI Assistant outputs. This is a milestone toward the May WHO/HL7 ICD-11 connectathon preparation. Demo Driver: Filipe / Joe Steps (proposed): 1. Load the prepared ICD-11 validation dataset (Tracker 55) — a curated set of CIEL concepts with known ICD-11 ground-truth mappings 1. Run the full multi-algorithm matching pipeline: * OCL CIEL Bridge * WHO ICD-11 automatch (Tracker 51) * Filipe's LLM-as-terminologist (Tracker 52) * Re-ranker: BAAI/bge-reranker-v2-m3 * OCL AI Assistant (Claude, with ICD-11 tailored prompts from Tracker 4) 1. Export the candidate results and re-ranked scores 1. Compare algorithm outputs against the ground-truth mappings: * Which algorithm produced the correct top-1 result? * Where do algorithms agree vs. disagree? * How does the AI Assistant recommendation compare to automatch? 1. Document evaluation metrics (e.g. top-1 accuracy, top-3 accuracy per algorithm) 1. Identify failure cases and document for iterative improvement 1. Share evaluation summary with team
Due by March 19, 2026•0/1 issues closedGoal: Demonstrate the CIEL Lab v2 concept management experience for an implementer audience. This is a mock (non-live-data) showcase intended to validate the UX and concept browsing workflow before the full CRUD-connected version is built. Audience: Internal team + potential CIEL implementer stakeholders Demo Driver: Andy Steps (proposed): 1. Open CIEL Lab v2 and navigate to the concept search/browse interface 1. Search for a CIEL concept by name (e.g. "Malaria") and review the results list 1. Open a concept detail page and walk through the CIEL/OpenMRS-style layout: * CIEL ID + FSN, UUID/external ID * Core metadata (datatype, class, locale) * Names by locale and type * Datatype-specific fields 1. Navigate class-driven associations: * For a Set concept: show its members, click through to a member concept * For a Question concept: show its answers, click through to an answer concept 1. Use breadcrumb / back-navigation to return to the browse context 1. Demonstrate the "missing mappings" filter — filter for concepts with no ICD-11 mapping 1. Walk through what the "add mapping" or "propose mapping" entry point would look like (even if mocked) 1. Show the concept edit entry point (even if not yet connected to the API backend)
Due by March 19, 2026End-to-end (E2E) “Filipe Showcase” workflow delivering the minimal-but-complete Concept Manager experience in CIEL Lab v2 (no full Concept Editor scope). Includes: search/browse CIEL concepts from OCL HEAD; open a concept details page with CIEL/OpenMRS-style layout (CIEL ID + FSN, UUID/external ID, core metadata, names by locale/type, datatype-specific fields); visualize class-driven associations (sets/members, questions/answers) with click-through navigation
Due by March 8, 2026•3/28 issues closed**Goal:** Public-facing showcase of all OCL Mapper capabilities developed during the 6-month CIEL-OCL-Madiro SOW (February–July 2026). Marks readiness for broader community release of the Mapper. Covers team-based workflows, multi-algorithm CIEL Bridge matching, mapping decision memory, UX improvements, and concept proposals. **Audience:** OCL community (OpenMRS, MSF, WHO, HL7, and others); this is a public showcase **Demo Driver:** Joe (Project-Product Manager) — coordinated with whole team **Steps:** 1. **Team-based mapping workflow**: - Project manager creates a new team project and assigns rows to team members - Show smart auto-save, record locking, and audit trail visibility - Show user notification: "What has my teammate updated?" 2. **Multi-algorithm matching & CIEL Bridge**: - Run auto-match with CIEL Bridge + ICD-11 algorithms + reranker + AI Assistant - Show UX for grouping candidates by algorithm, sorting by re-ranked score, and algorithm metadata 3. **Left panel UX**: - Show improved input dataset queue management - Demonstrate grouping, bulk approve, bulk reject, bulk unmap actions 4. **Mapping decision memory**: - Show the "Previous Mapping Decisions Panel" surfacing relevant past decisions - Accept a suggestion based on a past decision — demonstrate faster, more confident mapping 5. **Concept proposals**: - Mapper encounters a term not in CIEL - Creates a concept proposal from within the Mapper - Show that the proposal appears in TBv3 for the source administrator to review 6. **Save to collection**: - Demonstrate saving accepted mappings to a CIEL-based concept dictionary collection 7. **Large project support**: - Show a project with >1,000 input rows loading and saving correctly 8. Wrap-up: summarize the 6-month journey, key metrics, and what's available for the community
Due by July 8, 2026•0/6 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
Due by June 26, 2026•0/3 issues closedRequesting new concepts or changes when terminology gaps are found 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)
Due by May 29, 2026•0/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
Due by May 15, 2026•0/3 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
Due by April 30, 2026•0/5 issues closedCreating and managing collections with references, version control, and previews Showcase Story: Demonstrate the complete workflow for CIEL implementers to: * Create a new collection for their local terminology * Add references using multiple methods (quick add, advanced add) * Preview references before adding * Manage and view references in TBv3 * Lock collections to specific versions * Transform references between versioning strategies * Validate references against schemas in real-time
Due by April 17, 2026•1/12 issues closed**Status:** - Sunny/Filipe showcased on Feb 12 in a local dev environment - We will repeat the same Showcase with 3 changes: (1) In a deployed environment; (2) 50-row CIEL dataset prepared by Filipe instead of 10-row handpicked dataset; (3) Run by Andy instead of Sunny - Dataset for this upcoming showcase: https://github.com/OpenConceptLab/ocl_issues/issues/2340 - Sunny to walk Andy through how to run this showcase (this is mostly about how to configure the custom match algorithms) - This should be just a straight run-through and video recorded - aiming for 5-10min **Goal:** - Demo of the icd11 evaluation end-to-end workflow with a test dataset by Feb 12 - Audience: Local team, but intending to expand to WHO/HL7/whoever - Demo Driver: Andy main (previously Filipe), Sunny support **Steps for End-to-end workflow demo:** 1. Start new Project in OCL Mapper 2. Load Input Dataset: test dataset formatted as CSV 3. Configure project: - Target repo: `WHO / ICD-11-WHO` (Not defined in OCL) - Algorithms: - ocl-ciel-bridge - icd11 llm-as-terminologist - icd11 auto-code - Reranker: BAAI/bge-reranker-v2-m3 (this is the current default re-ranker model for OCL) - Field Mapping: Only match on the name - AI Assistant: - Exclude mapping fields - Model: anthropic/claude-haiku-4.5 4. Auto-match: 3x algorithms, reranker, AI assistant 5. Save project 6. Download project as CSV
Due by February 26, 2026•9/21 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 9 day(s)•Due by February 15, 2026•0/2 issues closedEarliest viable release of version 3 of OCL's TermBrowser. Will contain necessary features for terminology viewing/browsing, some basic features for terminology authoring, and some new features such as a User Dashboard, Following Users and Organizations, etc.
Due by July 17, 2026•36/122 issues closed