Configure fields to match your taxonomy
The metadata configuration interface provides a library of customizable fields organized by category: health plans, line of business, policy fields (source, type, creation date), clinical attributes (specialty, dates for review cycles), and operational tracking.
Each field can be tailored to your organization's needs. Add the dropdown values your staff actually use. Remove options that don't apply. Hide entire fields if they're not relevant to your workflows.
Example: Specialty configuration
The Specialty field might include values like Musculoskeletal, Cardiology, Radiology, and Surgical services. Your organization can add subspecialties (Interventional Cardiology, Pediatric Surgery), remove categories you don't manage, or rename values to match your internal taxonomy. The "+ Add" option lets you expand lists as your policy portfolio grows.
Fields you don't use can be hidden entirely with a single click, keeping the interface clean for policy authors and reducing decision fatigue during policy creation.
Why customization matters
Metadata only works if it reflects how your teams actually think about policies. If clinical reviewers search by "Ortho" but your dropdown says "Musculoskeletal," they'll struggle to find what they need. If your authorization system routes by "Auth Type" but Policy Studio calls it "Authorization Category," integration becomes friction.
Align your metadata schema with existing operational workflows, UM system taxonomies, and public-facing website structures. The goal is consistency across all touchpoints—internal tools, provider portals, member websites, and API integrations.
What fields do clinical reviewers filter by when searching for policies?
What dropdown values exist in your UM system today?
How are policies organized on your public website?
What metadata do your APIs require for integration?
Document these taxonomies, then configure Policy Studio's metadata fields to match. This preparation ensures policy authors tag content correctly from day one, and downstream systems can consume metadata without translation layers.