VitaBoard
Log inGet started
In Platform admins

Catalog curation

Keeping the shared test-type, drug, condition, and specialty lists clean.

Several parts of VitaBoard draw on canonical, platform-wide lists so that values line up across doctors, patients, and charts:

  • Test types — orderable exams and the vitals catalogue
  • Drugs — for prescriptions
  • Conditions — for the health record
  • Specialties — for doctor discovery
  • Reference ranges and growth standards — for abnormal flagging (seed data; a curation UI is planned)

The propose → review flow

Every list follows the same lifecycle:

  1. A doctor (mid-order) or a patient (mid-entry) can propose a new entry when the one they need is missing. It's usable immediately, as pending.
  2. A super-admin reviews the queue and approves, rejects, or merges it.
  3. On approval the entry gets its canonical slug and becomes a first-class list item (and, for specialties, a search facet).

Merging duplicates

A shared, user-extendable list drifts — "Blood Pressure" and "BP" arrive as separate entries. Merge repoints every record that referenced the duplicate onto the canonical entry and retires the duplicate. This is the main ongoing curation task; do a pass whenever real usage adds noise.

Anti-spam guard: each user has a cap on outstanding pending proposals, and a case-insensitive name check dedupes the common case before a proposal is even created.

Why it matters for charts

Health trends only line up when the same real-world measurement always uses the same code. Merging near-duplicate test types after the fact is how that stays true.

Was this page helpful?