Policies don't go live automatically—they go through scheduled implementations. The Implement tab controls when and where each policy version becomes active: which lines of business it covers, how it's displayed to members and providers, and when internal review tools start using the updated criteria.
Schedule implementation controls policy activation
The implementation interface manages the rollout of approved policies to production systems. Key configuration elements include:
Configuration version – Select which policy version to implement. Policies may have multiple draft configurations in progress; this dropdown specifies which approved version goes live.
Health plan and line of business – Define the scope of the implementation. A single policy might apply to all lines of business (Commercial, Medicare, Medicaid) or only specific ones. Some policies may be implemented differently across plans.
Public library display options – Control what members and providers see on your public-facing policy website:
Implementation and expiration dates – Set when the policy becomes active and when it sunsets. Implementation dates ensure policies don't go live until effective dates specified by clinical committees. Expiration dates automate policy retirement, triggering review workflows before policies lapse.
Review tool activation – Separate date controls for when internal clinical review systems (UM platforms, nurse reviewer workflows) start using the new policy logic. This may differ from public display dates—internal systems might activate policies earlier for training or later for phased rollouts.
Why separate implementation controls matter
Not every policy goes live everywhere at once. Regulatory requirements, contractual obligations, and operational readiness vary across lines of business and geographic markets.