Skip to content
yves
All tools
Design your categories

Taxonomy Builder

Start from a sector template, edit every category, set escalation floors, and export the taxonomy your institution signs off.

5 min · free · no account

Start from a sector
Your categories
  • appointment-access
  • waiting-time
  • doctor-care
  • nursing-care
  • results-callback
  • billing-clarity
  • facilities-cleanliness
  • pharmacy-supplies
  • staff-conduct
  • other

Ready to sign off

  • 10 categories, 1 escalated to critical, and a tail bucket in place. Take this to your quality lead.

Provisioning SQL

insert into institutions (slug, name, settings)
values (
  '<your-slug>', '<Your Institution>',
  jsonb_build_object(
    'industry', 'healthcare',
    'taxonomy', jsonb_build_array(
      'appointment-access',
      'waiting-time',
      'doctor-care',
      'nursing-care',
      'results-callback',
      'billing-clarity',
      'facilities-cleanliness',
      'pharmacy-supplies',
      'staff-conduct',
      'other'
    ),
    'escalate', jsonb_build_array(
      'staff-conduct'
    )
  )
)
on conflict (slug) do update set settings = excluded.settings;
Have us review it
How this works

Every deployment starts here. The category list decides what your leadership is able to see, so Yves treats it as the first real decision of the project rather than configuration.

The warnings on the right are the same checks our deployment leads run in a taxonomy workshop: eight to twelve categories, a tail bucket that Yves watches, and an escalation floor on anything carrying legal consequence. The SQL is genuine provisioning output.

Run it for real

These tools use the same logic
that runs in production.

Start a trial and point them at your own corpus instead of a sample.