AMA profile discrepancies need three separate clocks
AMA says a profile discrepancy must be submitted within 180 days of purchase or a monitored-profile update notice, that it will report results or delays within 30 business days, and that a revised profile remains available for 30 days. A credentialing workflow should preserve each trigger and deadline separately so a correction can be retrieved and reviewed without rewriting the evidence used earlier.
Editorial figure by Credentialing Current. Source context: AMA Physician Professional Data and Profiles.
Start each clock with its own source event
The direct answer is to model three timers rather than one discrepancy due date. The first controls when a customer can submit the issue: AMA says the filing window is 180 days from profile purchase or, for a profile covered by Continuous Monitoring, 180 days from the email notice that the monitored profile was updated. The second concerns AMA's communication during the investigation: results or a delay notice within 30 business days. The third begins only if the investigation changes the profile: 30 days to access the updated profile.
Preserve the clinician identity, profile type, order number, purchase time, monitoring status, update-notice identifier and delivery time, discrepancy number, filing time, investigation status, results or delay message, revised-profile availability notice, retrieval deadline, retrieval event, and accountable internal owner. Label calendar days and business days exactly as the source does. If a notice was not received or a timestamp is unavailable, keep that condition unresolved and obtain support guidance rather than calculating a confident deadline from a substitute event.
Keep the purchased profile and correction as separate evidence
A discrepancy case begins with the exact profile that the organization purchased or received through its approved access path. Retain that original artifact, clinician identifiers, order and retrieval information, profile date, field or fields challenged, reported value, proposed correction, supporting material, submitter, and submission receipt. The AMA page says its investigation may require contact with one or more primary sources. The organization should therefore distinguish its own report and documents from the AMA investigation status and any later profile revision.
If a changed profile becomes available, store it as a new version linked to the discrepancy rather than replacing the earlier profile. Record the retrieval time, revised fields, unchanged fields, any explanation supplied, reviewer, comparison result, and retained original. An email that reports a result or delay is a case communication. It is not automatically the revised profile, and availability of a new download does not establish that the organization retrieved, reviewed, or applied it.
Route a revised field to the decisions it could affect
A profile correction should create an impact assessment tied to the field, applicable policy, evidence cutoff, and decisions that used the earlier value. Education, postgraduate training, board certification, state licensure, National Provider Identifier, federal or state action information, or DEA registration can feed different workflows and may require different follow-up. Preserve the credentialing file, committee packet, appointment or privilege record, payer-enrollment submission, directory or roster, monitoring case, and other downstream use only where the field and local process make it relevant.
The accountable organization must decide whether a correction is material, whether another primary-source check or practitioner communication is required, and whether a pending or completed decision needs review. Keep the original decision, criteria and evidence cutoff intact; add the later source version, materiality rationale, reviewer, action, approvals, notifications, effective date, and closure evidence. The AMA page describes its profile and discrepancy process. It does not make a hospital, health plan, employer, committee, licensing, enrollment, appointment, or privileging decision.
Test all three clocks and an unavailable download
A representative evaluation should purchase a test profile through an authorized process, create a monitored-profile notice scenario, and calculate the submission window from the correct trigger in each case. Submit a discrepancy, capture the confirmation and case number, model a results message and a delay message, and confirm that the 30-business-day tracking rule does not become a calendar-day timer. Then make a changed profile available and verify the separate 30-day retrieval task, reminder, escalation, access control, and retained download receipt.
The test should also include an update notice that cannot be located, a discrepancy filed near the stated window, a response that arrives without a profile change, a revised profile that is not retrieved before access ends, and a changed field that was used in an open review. Reviewers should reproduce each timer, source event, artifact version, status, internal action, and decision impact without treating a portal status as a completed credentialing outcome. The AMA source supports the attributed access, monitoring, discrepancy, investigation-communication, and revised-profile availability statements; it does not establish an individual profile's completeness, correction, retrieval, downstream use, or outcome.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Credentialing Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.