AMA CPT® Disclaimers — Are We Compliant?  πŸ©ΊπŸ“‹

Audit of the product vs. the uploaded license's notice obligations

Source: AMA CPT Data Files License Agreement (draft, 01 Jun 2026) · Appendix E “Notices & Disclaimers” + Appendix A “End User Agreement Terms”

VERDICT: PARTIAL — not yet compliant.
Good-faith start (CPT® trademark + copyright + a paraphrased “not coding advice” line on the PDF & the on-screen billing banner). But 6 required notices are missing or paraphrased. Do NOT tell the AMA we're fully compliant yet. Closing the in-product gaps = one bounded /synexar-task (text only).
⚠️ TWO surfaces, not one
A) In-product display → the app + the PDF report  (Appendix E)
B) End-User Agreement → your customer contract / Terms, outside the app  (Appendix A)
We found nothing for (B) in the repo — separate legal item.
What the AMA license requires What Synexar has today Status
CPT® is a registered trademark of the AMA Present on PDF + on-screen billing banner HAVE βœ“
“CPT copyright [year] AMA. All rights reserved.” Present on PDF (PdfService.cs) HAVE βœ“
Copyright YEAR = title year − 1 (CPT 2026 → “2025”) Code shows “2026” — likely off by one VERIFY ⚠
Fee schedules / RVUs / conversion factors “not part of CPT, AMA not recommending their use” Absent MISSING βœ—
“AMA does not practice medicine or dispense medical services” Absent MISSING βœ—
“AMA assumes no liability for data contained or not contained herein” Absent MISSING βœ—
U.S. Government End Users notice — FAR 52.227-14 / DFARS 252.227-7015 Absent everywhere MISSING βœ—
NCCI / CMS “National Correct Coding Policy” notice (we DO use NCCI bundling) Absent β€” verify if triggered MISSING βœ—
Use the AMA's verbatim wording (§15.4e + §16.1) Synexar paraphrase — OK to add, not to replace FIX ⚠
Shown before first CPT display + copyright on each page PDF renders it once, after content; no splash FIX ⚠
End-User Agreement flow-downs (Appendix A): AMA = 3rd-party beneficiary, name-release, “as is”, “guide only”… No customer Terms / EUA found in repo SEPARATE βœ—

To honestly tell the AMA “we're compliant” — close these:

  1. Engineering · 1 /synexar-task (text-only): add the verbatim Appendix-E block (fee-schedule + “no medicine” + “no liability”), the U.S. Gov FAR/DFARS notice, and the NCCI notice; show the block before first CPT display (app splash + top of CODING section) and copyright per page; fix the copyright year.
  2. Legal · /brad + outside counsel: add the Appendix-A flow-downs to the customer End-User Agreement (AMA as third-party beneficiary, name-release, “as is”/“guide only”).
  3. Then: request the AMA's written product approval (Agreement §15.3) — required before distribution anyway.

Verified by reading: PdfService.cs (AddCptDisclaimer L574-615) · ai-disclosure-banner.component (variant ‘billing’, marked “counsel-pending”) · .pact/pdf-section-order-cpt-disclaimer · no EUA/ToS file in repo. Drop-in verbatim text saved to synexar-runtime/memory/compliance/ama-cpt-appendix-e-notices.md. Legal claims are [verify] for outside counsel.