What it does
Programs maintain the lists of diagnoses and procedures that learners pick from when logging cases. Items sit in categories, carry a clinical code, and can optionally set a minimum required count. Institutions also keep a shared case code library. It can be populated in bulk from CSV files, with a full audit of every import.
Who it's for
Program administrators curate their program's diagnosis and procedure lists and categories; institution administrators manage the institution-wide code library visible across programs.
How it works
Program catalogs. The Diagnoses & Procedures page lists each item with its name, code, category, requirement count, and active status, split across Diagnoses and Procedures tabs. Add items one at a time or several at once, then edit them. Items sit in typed categories — a diagnosis item in a diagnosis category, a procedure item in a procedure category — and mixing types is rejected. You can also set display order, deactivate unused items, and turn an item into a tracked requirement by setting a requirement above zero.
Clinical code systems. Items carry a code and code system that fit their type. Diagnoses accept ICD-10, ICD-11, SNOMED, or local codes. Procedures accept CPT, HCPCS, SNOMED, or local codes. An invalid pairing — a CPT code on a diagnosis, for example — is rejected.
Grade links. From the catalog screen, you can link a category to grade targets. Approved case counts in that category then feed the linked grade. You get a preview before linking, plus per-link sync controls.
The institution case code library. Under settings, institution administrators manage a shared, institution-wide Case code library. Select Add code for one code at a time, or Import codes to load a CSV file. Imports run as tracked batches: each records the file name, rows inserted, updated, or failed, and a status (pending, validating, completed, completed with errors, or failed) under Recent imports.
Before you start
You need the program's template-management permission to edit a program catalog, or the same permission at institution scope to edit the institution code library.
Know your item's category first — a diagnosis needs a diagnosis category, and a procedure needs a procedure category. The platform rejects a mismatch.
Decide the code system for the item (ICD-10, ICD-11, SNOMED, or local for diagnoses; CPT, HCPCS, SNOMED, or local for procedures) before you save.
Do this
Open Diagnoses & Procedures (
/cases/diagnoses) → you should see the Diagnoses and Procedures tabs with your program's items.Select the Diagnoses or Procedures tab, depending on which list you're adding to → the list filters to that item type.
If the category you need is missing, select the New Category button → you should see a dialog to name the category.
Select the Add Diagnosis or Add Procedure button → the New Diagnosis or New Procedure dialog opens.
In the dialog, fill in Category, Code, and Name, and set a Requirement count if this item should count toward a minimum, then select Save → the item appears in the list with an active status.
You're done when
✓ The item shows on the Diagnoses or Procedures tab with its code and category.
✓ Learners logging a case in this program see it in the matching picker.
✓ A requirement count above zero shows up as tracked progress in requirement reports.
Boundaries and limits
Editing a program catalog requires the program's template-management permission. The institution code library needs the same permission at institution scope, but its items are readable by all institution members.
Code systems are validated per item type — you can't save a diagnosis with a procedure code system or vice versa.
An item's type must match its category's type; the platform rejects mismatches at save time.
Minimum required counts can't be negative; zero means the item is available for logging but not tracked as a requirement.
Deactivating or deleting an item is a soft removal — existing case logs that reference it keep their history.
CSV import is available for the institution code library; batch records stay as an audit trail, and each import reports failed rows rather than silently skipping them.
Common questions
Q: What's the difference between the program catalog and the institution code library? A: The program catalog is what learners in that program pick from, and where requirement minimums live. The institution library is a shared code list managed centrally and visible across programs.
Q: Can I bulk-load our diagnosis list? A: The institution code library supports CSV import with per-batch reporting of inserted, updated, and failed rows. Program catalog entries can be added several at a time.
Q: If I deactivate a procedure, what happens to logs that used it? A: Nothing changes on existing logs. The item stops being offered for new logging.
Q: Can a category's case counts affect grades? A: Yes. A category can be linked to grade targets so approved case counts contribute to a grade, with a preview of the effect before you activate the link.
Related articles