Skip to main content

Policy versioning and audit trail

Written by Nicole Saidai

The Policy Versioning & Audit Trail feature provides complete transparency and traceability for all changes made to your medical policies. Every edit, update, and publication is automatically tracked, giving you the ability to review historical changes, restore previous versions, and maintain a comprehensive audit log for compliance and quality assurance.

  • Work confidently knowing you can always revert to a previous version

  • Track the evolution of policy logic over time

  • Collaborate with team members while maintaining change visibility

  • Meet regulatory requirements for policy documentation

Accessing Version History

  1. Open any policy document in the Policy Management System

  2. Navigate to the Revision History section in the left sidebar

  3. View the complete version history table showing:

    • Version number

    • Date of change

    • Description of modifications

    • Author (who made the change)

Draft Versions

  • Working copies that are not yet published

  • Can be edited, modified, or discarded

  • Not visible to API consumers or clinical workflows

  • Indicated by "Draft" status badge

Published Versions

  • Official policy versions available for clinical use

  • Accessible via API with specific version number

  • Immutable once published (cannot be edited)

  • Timestamped with effective date

Configuration Versions

  • The dropdown at the top shows the current configuration version (e.g., "2.1 (latest)")

  • This indicates which version of the policy structure you're viewing

To See All Changes to a Policy:

  1. Click on Revision History in the left navigation panel

  2. Review the version history table with columns for:

    • Version: Sequential version number

    • Date: When the version was created or published

    • Description: Summary of what changed in this version

  3. Click on any version row to view the complete policy state at that point in time

How to Add a New Revision

When making significant changes to a policy:

  1. Click "+ Add revision line" in the Revision History section

  2. Enter the Public version number you want to assign

  3. Set the Date when this version becomes effective (mm/dd/yyyy format)

  4. Provide a Description explaining what changed in this version

  5. Click Save

This creates a new entry in the version history and helps stakeholders understand the evolution of the policy.


Audit Log Capabilities

The audit trail provides comprehensive visibility into all policy actions:

What's Tracked:

  • Policy creation and initial authoring

  • All edits to policy text, decision logic, or metadata

  • Version publications and effective date changes

  • User who performed each action

  • Timestamp of every modification

  • Restoration of previous versions

Viewing the Audit Log:

  • Access the full audit log from the policy detail view

  • Filter by date range, user, or action type

  • Export audit logs for compliance reporting

For API Users:

  • Access version-specific policy logic for accurate claim adjudication

  • Ensure prior authorization decisions reference the correct policy version effective at the time of service

  • Support appeals and audits with precise historical policy snapshots

versions.png
Did this answer your question?