Sign Up
Login
Try for Free
Login
A diagnosis and problem list update is the dated, authored entry a clinician makes when adding, refining, correcting, or resolving a diagnosis in the medical record, including the ICD-10-CM code that flows onto claims. Clinicians, coders, and CDI teams use it whenever the active diagnosis list changes. Most entries run 50 to 200 words: a diagnostic statement plus the clinical support for it.
The treating clinician who establishes or changes the diagnosis; coders and CDI staff query rather than author
Treating clinician, care team, coders and CDI staff, payers, auditors, and downstream EHR systems
50 to 200 words · 3 to 8 minutes by hand (clinical team estimate)
Structured list plus rationale (compare: amendment entry, progress note assessment)
Whenever a diagnosis is added, refined, corrected, or resolved on the problem list or a claim
ICD-10-CM (US, adopted under HIPAA), ICD-10-CA (Canada), ICD-10-AM (Australia); the amendment format is payer policy, not statute
A diagnosis and problem list update is the entry a clinician makes when a diagnosis is added, made more specific, corrected, or resolved in the patient record, along with the code change that follows it onto claims. It is not a separately standardized legal document in any country. It is a functional entry that sits on two older document families: the problem list, introduced by Lawrence Weed's problem-oriented medical record (first published in 1964, brought to prominence in 1968, the same framework that produced the SOAP note), and the amendment, addendum, and correction entry. In the US, the problem list entered federal policy through the HITECH-era meaningful use program, where CMS defined it as "a list of current and active diagnoses" and paid clinicians to keep it current. You will also hear the entry called a problem list reconciliation, diagnosis addendum, dx change, diagnosis clarification, provider query response, or, in risk-adjustment circles, HCC recapture documentation; Ontario's Cumulative Patient Profile is the provincial cousin.
The distinction that carries this page: the amendment rules everyone treats as law are not law. In the US, the controlling instrument for changing a diagnosis entry is the Medicare Program Integrity Manual, and the CMS transmittal behind it states plainly: "There are no regulatory, legislative, or statutory requirements related to this CR." What it requires, as payer policy enforced through audit, are three properties for any amendment, correction, or delayed entry: identify it as such, date and author it, and preserve the original content without deletion. Two things are stronger than policy. The ICD-10-CM code set itself is adopted under HIPAA, which is law, and coding convention (ICD-10-CM Guideline I.A.19) bases code assignment on "the provider's diagnostic statement that the condition exists," which is why the written statement, not the EHR picklist, is the load-bearing element. The update entry is also distinct from the psychiatric diagnostic evaluation (90791, 90792), the comprehensive service that first establishes a diagnosis: choose that when a new episode begins, and this entry when an existing diagnosis changes.
Anyone who maintains a diagnosis list writes them: physicians and psychiatric nurse practitioners in prescribing practices, psychologists and therapists in insurance-based care, primary care teams managing behavioral health conditions, and the coding, CDI, and HIM staff who query providers in hospitals. In behavioral health the trigger is usually one of three events: an unspecified intake diagnosis reaches full criteria and gains specificity, a scheduled review changes status (when scores drive the change, pair the entry with an outcome measure note), or a payer document needs the current diagnosis restated, from the billing note that ties a service to it to the treatment plan built on it. The update is a record of fact about the diagnosis itself; forward-looking changes to goals and services belong in the plan, and the initial diagnostic case belongs in the evaluation.
Entry header and type. Date of entry, author with credentials, and what kind of entry this is: new diagnosis, refinement, correction or amendment, delayed entry, status change, or resolution. Under the CMS amendment principles the label is the first requirement; a change that is not identified as a change fails before its content is read. Pitfall: editing an earlier note in place. The EHR audit trail will show it, and an unlabeled alteration reads as concealment rather than correction.
Diagnostic statement. The diagnosis in the provider's own words, with severity, episode, and course specifiers. This sentence, not the picklist, is what codes are assigned from: ICD-10-CM Guideline I.A.19 bases assignment on the provider's statement that the condition exists. Pitfall: a code with no statement behind it. A bare F-code on the problem list gives a coder nothing to assign from and an auditor nothing to verify.
Onset, status, and rule-outs. When the condition began or was established, whether it is active, improving, in remission, or resolved, and any rule-outs still pending. Pitfall: rule-out language left on the list so long it hardens into the diagnosis. A rule-out is a question, and the record should show when it was answered.
Clinical support at this encounter. For any diagnosis carried on the day's claim, evidence it was monitored, evaluated, assessed, or treated that day: a score, an examination finding, a medication decision. Pitfall: the copied-forward chronic condition. The recurring root cause OIG cites in risk-adjustment audits is past conditions reported as current, and a diagnosis with no current support is that exact pattern.
Coding mapping. The ICD-10-CM code (or the code your coder will assign), the code it replaces, and the effective dates of each. In behavioral health, DSM-5-TR labels map to ICD-10-CM codes, and the claim needs the ICD-10-CM code. Pitfall: leaving an unspecified code such as F41.9 after the documentation supports specificity; specificity is where medical necessity and risk adjustment are decided.
Problem list action. What happened to the list itself: added, status changed, resolved with a date, or moved to history with the applicable Z-code. Keep the list a list of current and active diagnoses, which is the definition federal policy gave it. Pitfall: history-of used as a parking space. ICD-10-CM directs you not to code conditions previously treated that no longer exist, so a resolved condition either leaves the list or becomes a history code; it does not stay current.
Attestation. Signature, credentials, and date, at or near the time of the change, with the original entry left readable whenever this entry corrects one. Pitfall: signing or amending at audit time. CMS RADV reviewer guidance treats a record amended when the auditor calls as failing the timeliness requirement outright.
DIAGNOSIS AND PROBLEM LIST UPDATE
Patient: ____________ DOB: __________ Date of entry: __________
Author (name, credentials): _____________________________________
Entry type: [ ] new diagnosis [ ] refinement (specificity)
[ ] correction/amendment [ ] delayed entry
[ ] status change [ ] resolution
Linked encounter date: __________
DIAGNOSTIC STATEMENT (your words; the code is assigned from this)
_________________________________________________________________
_________________________________________________________________
Onset/established: __________ Status: [ ] active [ ] improving
[ ] in remission [ ] resolved Rule-outs pending: __________
CLINICAL SUPPORT AT THIS ENCOUNTER (for any diagnosis on a claim)
Monitored / evaluated / assessed / treated today, shown by:
_________________________________________________________________
CODING MAPPING
New or confirmed code: __________ Replaces: __________
Effective date: __________ DSM-5-TR label (if used): __________
Claim affected: [ ] yes [ ] no
PROBLEM LIST ACTION
[ ] added [ ] status updated [ ] resolved (date: __________)
[ ] moved to history (Z-code: __________)
If correcting a prior entry: original preserved and identified [ ]
Signature/credentials: ________________ Date/time: ____________Free to use and share, no signup. The PDF includes a one-page cheat sheet with section-by-section pitfalls and a pre-sign checklist; the DOCX is the blank template, ready to adapt.
Scenario: outpatient behavioral health practice; a psychiatric nurse practitioner refines an intake anxiety diagnosis and resolves an adjustment disorder at a follow-up visit. All details are fictional.
Diagnosis and Problem List Update. Client: R.L., 41 · Date of entry: 08/12/2026 · Author: A. Novak, PMHNP-BC · Linked encounter: office visit, 08/12/2026
Entry type: Refinement of an active diagnosis and resolution of a second diagnosis. New dated entry; no prior note altered.
Diagnostic statement (refinement): Generalized anxiety disorder, moderate. Excessive and difficult-to-control worry across work, health, and family domains, present more days than not since January 2026, with restlessness, sleep-onset difficulty, and irritability. Duration and symptom criteria are now met. Replaces other specified anxiety disorder, documented at intake on 03/04/2026 when the duration criterion was not yet met.
Diagnostic statement (resolution): Adjustment disorder with anxiety, resolved. The precipitating stressor (interstate relocation) ended in February 2026, and no stressor-linked symptoms have been reported or observed since the 05/2026 review.
Clinical support at this encounter: GAD-7 administered today: 14, from 17 at intake. Worry content, duration, and controllability assessed in session against DSM-5-TR criteria. Treatment addressed today: sertraline continued at 100 mg daily; worry-postponement practice reviewed and assigned.
Coding mapping: F41.1 active for today's encounter and forward claims, replacing F41.8, which is end-dated 08/12/2026. F43.22 end-dated 08/12/2026; no further claims will carry it. Original intake entries remain unchanged and readable.
Problem list action: Generalized anxiety disorder added as active with January 2026 onset; other specified anxiety disorder closed as refined; adjustment disorder marked resolved with today's date and retained in past psychiatric history.
Attestation: Entered and signed at the time of the change. A. Novak, PMHNP-BC. 08/12/2026, 4:40 pm.
This sample is fictional and for educational purposes. It does not describe a real patient.
Writing these after every session? BastionGPT drafts complete notes from bullets, dictation, or a transcript.
Generate a note from bulletsThe update entry is ordinary medical-record content: part of the designated record set, releasable to the patient on request, and read by every downstream system that trusts the problem list, from clinical decision support to registries to risk-adjusted payment. Retention is where clinicians most often assume a rule that does not exist. HIPAA sets no retention period for clinical records; its 6-year rule (45 CFR 164.316) covers compliance documentation such as policies. What governs is state and program law, and the spread is wide: Medicare Advantage and Part D records 10 years, Massachusetts hospital records 20 years, Washington hospital records 26 years from creation under a 2025 amendment. Ontario requires by regulation 10 years from the last entry, or 10 years after a minor turns 18. Victoria and New South Wales require 7 years from the last service, or until age 25 for records made while the patient was a child. Build the practice retention policy to the strictest rule that touches you.
On the payer side, the entry anchors the medical-necessity chain: the diagnosis you record here is the one payers read on a prior authorization request before approving care, and the one that decides code-level denials (CARC 11, in X12's words "The diagnosis is inconsistent with the procedure"). The format is a convention; the content, a dated, authored, supported diagnostic statement, is the requirement. Follow the CMS amendment discipline for every change even though it is payer policy rather than statute, and never amend a record after an audit request arrives: RADV reviewer guidance treats audit-time amendments as untimely on their face. Timing otherwise has no federal hour count; the expectation is entries completed and signed at or near the time of service, the same contemporaneity standard behind a start and stop time attestation, with late entries labeled as delayed. A diagnosis change should also ripple forward into the next treatment plan review so the plan and the list tell one story. In Canada and Australia the coding mechanics invert: ICD-10-CA (maintained by CIHI) and ICD-10-AM (published by IHACPA) are assigned by hospital coders from your documentation, not entered by clinicians on claims, so an outpatient diagnosis change reaches the coded dataset chiefly when an admission ends and a discharge summary is abstracted. In Australian behavioral health the diagnosis lives inside the GP Mental Health Treatment Plan, and MBS item 2715 guidance says the plan can be updated at any time while a new plan should generally not be written within 12 months: record the diagnosis change as an update, not a new plan.
The audit record around diagnosis documentation is deep because risk-adjusted payment rides on it. CMS's FY2025 improper-payments data put the Medicare Part C improper-payment rate at 6.09%, or $23.67 billion, most of it attributed to supporting documentation that failed to substantiate the diagnosis data submitted for payment. OIG risk-adjustment audits repeat one finding: in a May 2026 audit (report A-02-23-01020), none of the 97 sampled high-risk acute stroke diagnosis codes were supported by the medical records, with potential net overpayments of $462 million for payment year 2021, and the recurring root cause OIG cites is past conditions reported as current. Behavioral health sits on the same tape: a national OIG audit of psychotherapy claims found 128 of 216 sampled enrollee days failed documentation requirements, an estimated $580 million improper. The BastionGPT Clinical Advisory Board sees the same errors most often in diagnosis and problem list update reviews:
BastionGPT is specifically trained, tuned, and clinically tested on diagnosis and problem list updates.
See how clinicians use it day to day on the AI therapy notes page.
Many BastionGPT users report saving more than 90 minutes per day on documentation.
HIPAA-compliant with a signed BAA on every plan. Your data is never used to train models. BastionGPT drafts, you review and sign.
No statute prescribes one. CMS's own transmittal for the amendment and correction rules states: "There are no regulatory, legislative, or statutory requirements related to this CR." What Medicare requires as payer policy is that any amendment, correction, or delayed entry be identified as such, dated and authored, and preserve the original content. Canadian colleges and the Australian boards require accurate, dated records but no particular format either. The structured entry on this page is a convention that makes those properties easy to prove.
Yes, when the documentation supports it. Under ICD-10-CM Guideline I.A.19, code assignment is based on the provider's diagnostic statement, and auditors compare the documentation to the claim, not to the provider's picklist selection. A coder may assign the supported code on the claim without the provider editing the note. An addendum is needed only when the documentation itself does not support the intended code.
Generally no. If the condition was not established at that encounter, code the signs and symptoms that were present that day and capture the confirmed diagnosis at the next encounter. The exception is a true correction: the diagnosis was documented at the encounter and the code was simply mis-entered. Back-adding diagnoses to closed encounters is the pattern risk-adjustment audits target, and CMS RADV guidance treats records amended at audit time as failing the timeliness requirement.
The psychiatric diagnostic evaluation (90791, 90792) is the comprehensive service that first establishes a diagnosis. The update entry modifies one that already exists: refining specificity, changing status, correcting an error, or resolving it. Billing a new full evaluation to re-establish an existing diagnosis invites denial; a dated update entry costs nothing and keeps the record current.
Claims require the ICD-10-CM code, the code set adopted under HIPAA. DSM-5-TR prints the corresponding ICD-10-CM code beside each diagnosis, so the crosswalk is built in, but the billable code is the ICD-10-CM one. Write the diagnostic statement with its specifiers; the code follows the statement.
That is CARC 11, a code-level mismatch: the diagnosis on the claim does not support the billed procedure under the payer's coverage rules. It often travels with remark codes such as M76 (missing or invalid diagnosis), and it is distinct from CO-50, a medical-necessity denial after clinical review. The durable fix is documentation: a more specific code the record already supports, or an updated diagnostic statement at the next encounter, never a code swapped in without support.
Not as current diagnoses. ICD-10-CM directs coders not to code conditions previously treated that no longer exist; where the history matters to care, the personal-history Z-codes carry it. On the list itself, a resolved condition gets a resolution date and leaves the active list. Keeping everything active for context feels safe, and it is exactly what produces carried-forward unsupported diagnoses, the most common audit finding.
HIPAA sets no retention period for clinical records; its 6-year rule covers compliance documentation such as policies. US retention comes from state and program law: Medicare Advantage and Part D records 10 years, Massachusetts hospital records 20 years, and Washington hospital records 26 years from creation under a 2025 amendment. Ontario requires 10 years from the last entry, or 10 years after a minor turns 18. Victoria and New South Wales require 7 years from the last service, or until age 25 for records made during childhood.
Yes. Paste a transcript or narrative note and it extracts each diagnosis with onset, status, and the supporting language; it maps diagnostic statements to candidate ICD-10-CM codes for your verification; and it checks the finished entry for what auditors read first: date, author, preserved original content, current clinical support, and resolved conditions actually removed. BastionGPT is HIPAA-compliant with a signed BAA on every plan, and your data is never used to train models.
Educational content, not legal or billing advice. Sample notes are fictional. Follow your organization's policies and your board, payer, and jurisdiction requirements.