Skip to main content

Writing and formatting policy content

Written by Nicole Saidai

The editor uses a familiar WYSIWYG interface—no HTML knowledge required. Format text, insert tables, add links and images, and structure content visually. The system manages the underlying code automatically.

Reusable content blocks ensure consistency at scale

Define standard elements once—disclaimers, regulatory language, age restrictions, clinical definitions—then insert them wherever needed. When you update the source content, every policy that references it updates automatically across your entire library. No manual find-and-replace operations. No version drift.

Section-based organization

Policy content lives in sections: coverage criteria, limitations, prior authorization requirements, source references. Each section supports text, tables, lists, and images. The table of contents updates automatically as you add sections, providing instant navigation for complex policies covering multiple procedures.

Standard formatting that translates everywhere

The editor supports headings, bold, italic, bulleted and numbered lists, tables, hyperlinks to external guidelines, internal cross-references, images for anatomical diagrams, and visual dividers between major sections.

More importantly, formatting is preserved when content is distributed. Bulleted criteria remain bulleted in UM systems. Tables with CPT codes stay structured in API responses. Headers and hierarchy are maintained on public-facing websites. What you build in the editor is what clinical reviewers, providers, and members see—no formatting degradation across channels.

Auto-save and version control

Every change is preserved automatically without manual saves. Version control tracks who edited what and when, with full revision history showing all changes with timestamps and author names. Need to revert? One click restores any previous version.

text editor (3).png
Did this answer your question?