©2018 IDC #US43511218e 3
▪ Secure contract authoring allows users to create the contract with standards and solid,
auditable, and legal control. This includes products that streamline the process of drafting
contracts by allowing end users to choose the appropriate contract structure, enter needed
information, and generate the draft contract in compliance with legal standards and guidelines.
This could include features such as template libraries, redlining, wizards, document
management, address validation, multilanguage support, Microsoft Word/Excel add-ins,
flexible fields and clauses, and PADU (preferred, acceptable, discouraged, unacceptable)
language delineation.
▪ A workflow encourages collaboration and compliance and routes the draft contract and
revisions to the right people for approval, with complete tracking of who made what change in
which version. This could include features such as workflow diagramming, third‐party contract
support, esignature, rules engines, automated alerts, AI, and machine learning. Ease of use,
wizards, and self-service capabilities are distinguishing characteristics.
▪ Contract reports, dashboards, and analysis provide visibility into the risk and content of the
contract portfolio. Examples include the reporting and alerting of expiration dates of all
contracts, finding all contracts with specific vendors, and identifying contracts with
nonstandard clauses.
▪ Data integration or facilitation makes contract data available to and from other payer systems
such as provider demographic/network systems of record, claims payment, contract modeling,
pricing/fee schedules, retrospective and prospective VBR systems, and provider performance
systems. This integration allows for two closed-loop performance measures: clinical and
financial. This integration differentiates this space from enterprise procurement/contract life-
cycle management [CLM] systems.
To separate vendors in this payer-specific category from other generic procurement/contract life-cycle
management vendors, a vendor had to demonstrate integration with accompanying engines in a payer
paradigm. This integration criteria greatly diminished the field. Therefore, generic CLM, procurement,
and configure-price-quote (CPQ) systems were ignored, focusing exclusively on those that have payer
installations for provider contracting. An exception to this was the inclusion of SAP Ariba, as the
solution was explicitly recommended by IBM in its announcement of the retiring of IBM Emptoris,
causing disruption in the payer market.
ADVICE FOR TECHNOLOGY BUYERS
Gone are the days where a payer contract management system sat in a silo, managed by a tangential
clerical function that only ensured that contracts had only minor variation to standard terms, covered
an HMO or a PPO network, were signed accordingly, and were filed on schedule.
Whether using a "best of breed" approach or one vendor, the silo of provider contract management for
payers has been pulverized, enhanced, distributed, and made more complex. New software
combinations and broader, tighter integrations are required to meet today's complicated payer/provider
contracting environment.
Today, the provider contract is the center of a provider network relationship management dual closed-
loop ecosystem. This ecosystem is where rates, reimbursements, networks, and terms are modeled;
claims are examined continuously for accurate or more profitable reimbursement; directories and
networks are continuously updated; contracts and networks and providers are continuously measured;
and providers are continuously delighted.