CCM care plans: required sections and FHIR R4 mapping
What a chronic care management care plan has to contain, how each section is stored in HL7 FHIR R4 once the plan lives in software, and what Agnotic Technologies builds so care managers can write, review and share plans to your program's requirements.
For care managers and practice leads running CCM, and for the product and engineering teams building care plans into a care management app.
What should a CCM care plan include?
A CCM care plan should hold the problem list, expected outcome and prognosis, measurable goals, symptom management, planned interventions with who is responsible, medications, community services, coordination with outside providers and a review schedule. Agnotic Technologies builds care management software that stores each of those sections as structured HL7 FHIR R4 data.
Last reviewed by the Agnotic Technologies engineering team
Why do CCM care plans break down?
Most programs can write a care plan. The trouble starts when many care managers keep many plans current, month after month.
Plans that drift from the record
The problem list or medications in the plan no longer match the EHR, because one was updated and the other was not.
Goals nobody can measure
A goal written as free text with no measure or due date cannot be marked achieved or missed, so reviews have nothing to check against.
Interventions with no owner
A planned action has no named person or team, so each member of the care team assumes someone else is doing it.
Reviews that slip
The review date sits on a document instead of in a work queue, and a hospital stay or new diagnosis does not reopen the plan.
No proof the patient got a copy
CMS expects a copy to be given and documented. When the date lives in a note or a paper file, nobody can show it across a panel.
Plans locked in free text
Reporting cannot read goals or interventions as fields, and outside providers cannot receive the plan in a form their systems understand.
What do we build for CCM care plans?
Agnotic Technologies builds care plan features to your program's requirements, inside your existing app or as a new care management product. Typical features include:
Structured care plan editor
Every section CMS describes, stored as HL7 FHIR R4 CarePlan, Goal and CareTeam resources instead of a single text field.
Problem list and medication sync
Conditions and medications read from the EHR over FHIR R4 and US Core, with differences between the plan and the record shown to the care manager.
Measurable goal builder
Goals with a measure, a target value and a due date, so status moves to achieved or missed from the data rather than by memory.
Intervention assignment and work queues
Each planned activity carries a performer and a schedule, and lands in that person's queue with reminders.
Review scheduling and event triggers
The next review date sits in the care manager's queue, and admission or discharge events from an HL7 v2 ADT feed reopen the plan early.
Patient copy generation and tracking
A readable copy for the patient, on paper or in a portal, with the date and method recorded each time a new version is shared.
Care team coordination
Outside specialists and agencies held in CareTeam with their role and contact route, and plans exchanged over FHIR R4 with EHRs that support it.
Gap and quality reports
Missing or weak sections flagged using the gap signals in the mapping table below, with panel-level views for care management leads.
How does each section map to FHIR R4?
Use this table when the plan moves from paper into software. The last column is the signal an app or report should raise when the section is missing or weak.
| Care plan section | What to record | FHIR R4 resource and element | Gap signal |
|---|---|---|---|
| Problem list | Each chronic condition the plan covers, with its status, drawn from the full problem list in the record. | CarePlan.addresses (Reference to Condition); Condition.clinicalStatus | A condition is managed in the plan but has no matching Condition in the record, or the record lists one the plan ignores. |
| Expected outcome and prognosis | The likely course for each condition, in plain words the patient can read. | ClinicalImpression.prognosisCodeableConcept, or CarePlan.description for free text | Left blank or copied unchanged from plan to plan, so it no longer reflects the patient. |
| Measurable treatment goals | What the patient and team are aiming for, with a measure and a target date. | CarePlan.goal (Reference to Goal); Goal.description, Goal.target.measure, Goal.target.detail, Goal.target.dueDate | A goal with no measure or no due date, which cannot be marked achieved or missed. |
| Symptom management | The symptoms to watch, what the patient does when they appear and when to call the practice. | CarePlan.activity.detail with reasonReference to Condition or Observation | No action or threshold written, so the patient knows what to watch but not what to do. |
| Planned interventions and who is responsible | Each planned action, when it happens and the person or team responsible for it. | CarePlan.activity.detail (kind, scheduled[x], performer), or CarePlan.activity.reference to a ServiceRequest or Appointment | An intervention with no performer, so nobody owns it. |
| Medication management | Current medications, the reconciliation date and any adherence support. | CarePlan.activity.reference to MedicationRequest; MedicationStatement for what the patient reports taking | Medication list in the plan differs from the record, or the reconciliation date is missing. |
| Community and social services ordered | Services arranged outside the clinic, such as transport, meals or support groups, and their status. | CarePlan.activity.reference to ServiceRequest, with ServiceRequest.performer pointing to the organization or HealthcareService | A service named with no referral record or status, so no one knows whether it started. |
| Coordination with outside providers | Specialists and agencies outside the billing practice, what each is doing and how information is shared. | CarePlan.careTeam (Reference to CareTeam); CareTeam.participant.role, CareTeam.participant.member | Outside providers listed without a contact route or role. |
| Review and revision schedule | When the plan is reviewed, what triggers an early revision and the date the patient was given a copy. | CarePlan.period and CarePlan.status; review visits as CarePlan.activity with scheduled[x]; the shared copy as a DocumentReference | No next review date, or no record that the patient received a copy. |
Paper first or software first?
Start on paper when
You are piloting CCM, the program has a few patients, or you need agreement on what a good plan looks like before any build starts.
Move to structured data when
Several care managers share a panel, plans must be reviewed on time across many patients, or reporting needs to read goals and interventions as fields.
Keep a patient copy either way
The patient still needs a copy they can read. A structured plan should produce a clean, readable copy on paper or in a portal.
How do you keep the plan current?
Set the review date when you write the plan
Put the next review date on the first page, and put the same date in the care manager's work queue.
Revise on events, not only on dates
A hospital stay, a new diagnosis, a medication change or a goal met are all reasons to open the plan early.
Update the record and the plan together
Change the problem list or medications in the record first, then in the plan, so the two never drift apart.
Give and record the copy
Each time the plan changes in a way the patient should know about, give a new copy and note the date in the review section.
What should be true before a plan is filed?
Quality checks for any CCM care plan, on paper or in software. In software, each one can become a validation rule that runs when the plan is saved.
Content
- Every condition in the plan matches the problem list in the record.
- Each goal has a measure and a target date.
- Each intervention has a named person or team responsible.
- Medications were reconciled and the date is recorded.
Sharing and review
- Outside providers involved in care are listed with their role.
- The next review date is set and in the work queue.
- The patient was given a written or electronic copy, and that is recorded.
- The plan is stored where other members of the care team can open it.
Trusted by global innovators
Where do these sections come from?
The section list follows CMS rule text for CCM, and the mapping follows the HL7 FHIR R4 resource definitions.
CMS described the CCM care plan as a comprehensive plan for all health issues that typically includes a problem list, expected outcome and prognosis, measurable treatment goals, symptom management, planned interventions, medication management, community and social services ordered, coordination with outside agencies and specialists, the individuals responsible for each intervention, and periodic review and revision.
Source: CY 2015 Physician Fee Schedule final rule, 79 FR 67547 (govinfo.gov)The same CMS rule requires the practitioner furnishing CCM to give the beneficiary a written or electronic copy of the care plan and to document in the electronic medical record that the copy was provided.
Source: CY 2015 Physician Fee Schedule final rule (govinfo.gov)In HL7 FHIR R4, a CarePlan describes how practitioners intend to deliver care for a patient over a period, and references the Conditions it addresses, its Goals, its CareTeam and the activities that are planned.
Source: HL7 FHIR R4, CarePlanAn HL7 FHIR R4 Goal requires a description and a lifecycle status, and can carry targets with a measure, a desired value and a due date.
Source: HL7 FHIR R4, Goal
Which standards does Agnotic build care management software to?
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
What stays with your team?
- Billing rules
- CCM codes, monthly time thresholds and consent requirements change over time and are not covered on this page. Check the current CMS guidance and your billing team before you bill.
- Clinical content
- Goals, thresholds and interventions are clinical decisions for the billing practitioner and care team, not defaults to copy.
- Your EHR's own fields
- Your EHR may store some sections in its own care plan module. Map those fields to the FHIR elements here before you exchange plans.
- Legal or billing advice
- This page is engineering guidance from a software development services company. Confirm program requirements with your compliance and billing leads.
Which care management services relate to CCM care plans?
- Care management softwareCCM platforms with structured FHIR care plans, time tracking and EHR write-back.
- Chronic care manager AI agentMonthly CCM check-ins drafted for care managers to review.
- Chronic care software solutionsSoftware for CCM and RPM programs across chronic conditions.
- Care coordination softwareShared care plans across practices, agencies and community services.
- FHIR integration servicesExchange CarePlan, Goal and CareTeam resources with EHRs over FHIR R4.