Repository navigation
Quality Assurance
Quality Assurance (QA) keeps CIEL consistent, traceable and trustworthy as it grows. Automation and AI make it easy to add content quickly; QA makes sure that content stays correct.
Automated checks run over every concept, grouped in three areas.
Names and descriptions
- Each concept has exactly one active Fully Specified Name per locale, and no more than one preferred name.
- No duplicate names, and no two active concepts sharing the same Fully Specified Name.
- Name types and locales are written in the standard way only.
- Capitalization, special characters and wording are consistent.
Mappings
- Relationship types and target terminologies are known and written correctly.
- A concept does not carry contradictory or repeated mappings to the same terminology.
- SAME-AS is used only for true equivalence, not, for example, for residual "other/unspecified" codes.
- Mappings to codes that the source terminology has retired are found and updated.
Metadata
- Every active concept has a valid identifier.
- Concept class, datatype and units are valid.
- While editing: quick checks run as a curator edits a concept and block a save that would break a basic rule.
- In bulk: the full set runs across the whole terminology, including retired concepts where they still matter. Findings become worklists for curators.
- Before a release: a release is built only from content that passed.
- Checks that cannot run (for example, a reference list is unavailable) are reported as such, never as "no problems found".
QA rules can be switched on or off by administrators, and each rule's findings are reviewed by a person.
QA is part of the workflow, not a final step. Problems found become new rules or better word lists, so the same issue does not return.
Maintained by Filipe Lopes