Provider agreements are unlike most of a health system contract portfolio. There are thousands of them, each individually negotiated, most with compensation terms that vary by specialty and arrangement type, and many with service obligations that have to be evidenced rather than assumed. No two departments describe them the same way, and no single system holds all of them.
They are also time-bound in ways that matter. Terms expire, renewals arrive automatically, supporting documentation ages, and service commitments accrue whether or not anyone is recording them. Each of those is a date with an owner, and the register exists to make both explicit rather than assumed. The administrative burden is real, and it falls on teams who are also managing recruitment, credentialing and department budgets. The work is not difficult in any individual case. It is difficult at volume, and volume is the permanent condition.
This datasheet sets out how Aavenir holds provider arrangements as a tracked register: what is captured, how service evidence attaches to the agreement, and what the medical staff office and compliance team see when a date or a document approaches its limit. It is written for physician contracting, medical staff and compliance teams in systems where arrangements are spread across entities, departments and the people who negotiated them years ago.
What the register holds
The record is built around the arrangement rather than the document, because a single physician may hold an employment agreement, a directorship, a call coverage schedule and a recruitment arrangement at once. Holding them separately makes aggregate questions impossible to answer, and aggregate questions are the ones that arrive under time pressure. The arrangement view also survives reorganizations, which document-centric records rarely do.
- Arrangement identity, provider, entity, arrangement type, department, start and end dates, and the relationship to any other arrangement with the same provider.
- Compensation terms, the structure, rate basis, any productivity or quality components, and the supporting documentation referenced at execution.
- Service commitments, the duties promised, including hours, coverage schedules, administrative responsibilities and required reporting.
- Supporting documentation, the analyses and approvals relied on at execution, with their date and the refresh cycle that applies to them.
- Term and renewal mechanics, expiry, automatic renewal terms, notice periods and the internal approval path for renewal or amendment.
Held together, these answer the questions that arrive without warning: what arrangements does this provider hold, what is the aggregate commitment, when does each expire, and where is the evidence that services were delivered. For the audit-facing view of the same portfolio, Stark, Anti-Kickback and HIPAA audit expectations covers what a contract system should be able to demonstrate.
Directorship time logs, coverage rosters and administrative reporting are frequently held in departmental files while the agreement sits in the contract system. Separating them means any question about whether services were delivered becomes a retrieval exercise across two organizations. Attaching the evidence to the agreement as it is produced costs almost nothing and removes that problem permanently.
What the platform does
Aavenir holds each arrangement as a structured record linked to the provider and the entity, proposes terms and dates through extraction for review, and runs renewals, documentation refresh cycles and service reporting as tracked obligations. Aggregate views by provider and by department are available without assembling a report, which is the capability most systems lack and most reviews ask for first.
- Provider-centric aggregation. Every arrangement with a given provider rolls into one view, with aggregate commitment and compensation visibility.
- Documentation refresh tracking. Supporting analyses carry their own review cycle, with alerts before they age past the system standard.
- Service evidence capture. Time logs, coverage confirmations and reporting attach to the arrangement that required them.
- Renewal control. Automatic renewal terms surface with enough notice for a deliberate decision rather than a default outcome.
- Department and entity reporting. Open arrangements, expiries and outstanding evidence reported by department, entity and arrangement type.
A five-step rollout for provider agreement tracking
Step 1, Consolidate the arrangement inventory
Bring every arrangement type into one register, including those held outside the central contracting function such as departmental directorships and locum arrangements. Incomplete inventories are the norm at the start, and the gaps concentrate in exactly the arrangement types that generate the most questions.
Step 2, Standardize arrangement types and fields
Agree a common set of arrangement types with the fields each requires, so reporting works across departments and entities. Variation should reflect genuine differences in arrangement structure, not differences in who created the record.
Step 3, Extract terms and dates for review
Run extraction to propose compensation structure, service commitments, term and renewal mechanics, then have physician contracting confirm each one. Review is what makes the register dependable, and it is considerably faster than manual abstraction across a portfolio of this size.
Step 4, Wire evidence capture into the workflow
Connect time log submission, coverage confirmation and required reporting to the arrangement obligations they satisfy, so evidence accumulates as a by-product of normal operations rather than through a retrospective collection exercise before a review.
Step 5, Report on expiries and refresh cycles
Publish rolling views of upcoming expiries, automatic renewals approaching their notice deadline, and supporting documentation approaching its refresh point. Review them in the same forum that handles recruitment and department planning, where the decisions actually get made.
Managing thousands of provider arrangements?
See how Aavenir tracks arrangement terms, service evidence and documentation refresh cycles in one register.
Why aggregate visibility matters
Individual provider arrangements are usually well handled at execution. The difficulty is aggregate: a physician holding an employment agreement, two directorships and a call coverage arrangement across three entities represents a picture that no single document shows. Questions about total commitment, overlapping duties or cumulative compensation require assembling that picture, and assembling it manually is slow enough that it tends to happen only when prompted by a review. A provider-centric register makes the aggregate view the default rather than the exception. That changes what is possible operationally, because department leaders can see existing commitments before making new ones, and it changes what is possible for compliance, because the picture already exists before anyone asks for it rather than being built in response to the request.
Coverage at a glance
The table summarizes the arrangement types the module tracks, the commitments that typically attach to each, and the evidence that supports them. Configuration is per arrangement type, so an employment agreement and a call coverage schedule carry different obligation profiles. Key dates are the field most worth getting right, because almost every avoidable problem in this portfolio is a date that passed without anyone deciding anything.
| Arrangement type | Typical commitments | Evidence tracked | Key date |
|---|---|---|---|
| Physician employment | Clinical duties, productivity targets, restrictive covenants | Performance reporting | Term expiry and renewal notice |
| Professional services | Defined services, rate basis, reporting duties | Service and invoice records | Term expiry |
| Medical directorship | Administrative hours, specified responsibilities | Time logs and activity reports | Documentation refresh |
| Call coverage | Coverage schedule, response requirements | Coverage rosters and confirmations | Schedule period end |
| Recruitment arrangements | Practice commitments, repayment or forgiveness terms | Compliance confirmations | Forgiveness milestone dates |
Provider agreements are managed well individually and poorly in aggregate, which is exactly the opposite of what the questions require. A register that aggregates by provider, attaches service evidence to the arrangement that required it, tracks documentation refresh as its own commitment and surfaces automatic renewals with real notice turns a recurring administrative scramble into routine operations. For the wider commitment picture across the health system portfolio, see obligation management for healthcare.
For related guidance, see The health system guide to physician agreement controls, Physician agreements, compliance pressure points and The provider’s guide to GPO and 340B contract control.
