A hospital pays a monthly stipend to an orthopedic group for emergency department call coverage. The payment is set up in accounts payable against the agreement and runs reliably. The call schedule is maintained by medical staff administration in a separate system. Response time expectations are in the agreement. Whether the coverage was provided as agreed each month is, in most organizations, evidenced nowhere unless a complaint was filed.
That asymmetry is the defining feature of on-call coverage programs. Payment is scheduled and automatic. Delivery is presumed and only documented by exception. Operationally the presumption is usually correct, because coverage failures are noisy and get escalated. The difficulty arises when someone asks for documentation that payments corresponded to coverage actually received, which is a question with an obvious answer and no available evidence.
This article covers the obligations an on-call coverage agreement creates on both sides, how response time commitments should be defined so they can be measured, why simultaneous coverage restrictions go unmonitored, and what contemporaneous documentation the arrangement needs. It is written for hospital contract administration, medical staff administration and compliance teams.
The obligations inside the agreement
Coverage agreements are short documents that create a surprisingly wide obligation set, and the obligations run in both directions. Treating them as a payment instruction attached to a schedule is what leaves most of them unmanaged.
- Availability commitment, the specialty, the periods covered, whether coverage is continuous or by rotation, and the process for arranging approved substitutes.
- Response commitment, the time within which the physician must respond and present, with a defined start point, end point and accepted data source for measurement.
- Acceptance duties, the obligation to accept unassigned patients, provide follow-up care for patients seen while on call, and comply with medical staff policies.
- Exclusivity and simultaneity, any restriction on holding concurrent call obligations at other facilities during the same covered period, with the attestation mechanism supporting it.
- Hospital-side duties, timely stipend payment, provision of facilities and support staff, accurate scheduling and the notification duties the hospital owes in return.
The fifth category is frequently overlooked and matters in disputes. Coverage agreements impose duties on the hospital as well, and a physician group raising a concern about support staffing or scheduling accuracy is invoking contractual terms rather than complaining informally. Recording hospital-side obligations alongside physician-side obligations makes the arrangement symmetrical in the record, which is also how it reads to an arbitrator.
The simplest structural fix is to require a periodic coverage attestation before the stipend is released, confirming that coverage was provided for the covered periods, that any substitutions followed the approved process, and that no concurrent call obligation conflicted. It creates a contemporaneous record at the point of payment, costs almost nothing operationally, and converts a presumption into evidence without implying distrust.
Where coverage programs fail on evidence
The gaps below are documentation gaps rather than clinical or commercial ones. In most cases coverage was provided exactly as agreed, and the organization simply cannot demonstrate it.
- Payment is disconnected from delivery. Stipends set up as recurring payments against a contract continue regardless of coverage, and no step in the payment cycle asks for confirmation.
- Response times have no agreed measurement. Commitments stated in minutes without a defined start point or an accepted data source cannot be monitored, only argued about after an incident.
- Substitutions are informal. Approved substitute processes exist in the agreement and are handled by phone in practice, leaving no record of who actually held coverage on a given date.
- Simultaneity restrictions are unmonitored. The hospital sees only its own schedule, so a restriction on concurrent coverage elsewhere is effectively unenforced without a periodic attestation.
- Valuation records are retrospective. Documentation assembled after a question is asked is weaker than the same documentation created at execution, as set out in the audit checklist.
Closing the evidence gap
Step 1, Inventory coverage arrangements
List every coverage agreement with its specialty, covered periods, stipend structure, response commitment and current term dates, reconciled against what accounts payable is actually paying. Mismatches between the paying schedule and the executed agreement are common, particularly where rates were adjusted by correspondence rather than by amendment.
Step 2, Define measurement before enforcement
For each response commitment, agree the start point, end point and governing data source with the physician group, and record them on the contract. Where the existing agreement is silent, this can be documented as an operating protocol now and incorporated at the next renewal rather than waiting for an incident to force the conversation.
Step 3, Insert attestation into the payment cycle
Add a periodic coverage attestation as a prerequisite to stipend release, owned by medical staff administration and confirming coverage delivery, substitution compliance and absence of conflicting obligations. Keep it brief, because an attestation that takes more than a few minutes will be completed carelessly or late.
Step 4, Capture substitutions in the record
Route approved substitutions through the same system that holds the call schedule so the record shows who held coverage on each date. This is the record that answers questions about a specific incident months later, and reconstructing it from recollection is not credible.
Step 5, Attach documentation at execution
Require the rate determination basis, any independent valuation, the coverage burden data and the governance approval to be attached to the contract record before execution, and refresh them whenever the rate changes. Contemporaneous attachment is the whole point, and it is also the easiest step to enforce with a workflow gate.
Review a coverage arrangement
A working session on one agreement and the evidence it should be generating.
Why this is a contract operations problem
Coverage programs sit awkwardly between functions, which is the underlying reason the evidence gap persists. Medical staff administration owns the schedule and knows who was on call. Accounts payable owns the stipend and pays on a cycle driven by the agreement. Contract administration owns the document and typically sees it at execution and renewal. Compliance owns the documentation standard and usually discovers gaps during a review. None of these functions has a reason to connect payment to delivery, because each is performing correctly within its own scope. The connection has to be made on the contract record, which is the only artifact all four functions share. Holding the coverage obligation there, with an attestation cycle that gates payment and response time exceptions logged against it, turns four separate processes into one arrangement with a history. It is the same pattern applied to other provider commitments in the payer and provider contract automation guide, and the implementation effort is small relative to the exposure it removes.
An evidence model
The table below sets out what each obligation should produce as evidence and who should own it. The pattern to notice is that every row produces an artifact, because obligations that close on assertion do not survive review.
| Obligation | Evidence artifact | Owner | Cycle |
|---|---|---|---|
| Coverage availability | Periodic coverage attestation | Medical staff administration | Before each stipend release |
| Response time | Paging and arrival records with exceptions | Emergency department director | Monthly exception review |
| Approved substitution | Substitution record in the schedule system | Medical staff administration | Per occurrence |
| No conflicting coverage | Physician attestation | Medical staff administration | Periodic |
| Rate reasonableness | Valuation and approval records on the contract | Contract administration | At execution and on rate change |
On-call coverage arrangements are usually performing exactly as intended and documented as though nobody thought about them. The stipend is right, the coverage happens, and the records that would demonstrate both were never created because no single function had a reason to create them. Closing that gap does not require a new program. It requires the coverage obligation to live on the contract record, an attestation that gates payment, substitutions captured where the schedule lives, and valuation documentation attached at execution rather than assembled when someone asks.
For related guidance, see Exclusive professional services agreements for hospitals, Physician and provider agreement tracking for health systems and Telehealth services agreement guide for hospital contracting.
