Introducing APCM Behavioral Health Add-Ons in Sematic
Sematic now supports G0568, G0569, and G0570 in one guided workflow for candidate review, consent, monthly documentation, Athena write-back, and billing review.
Published September 3, 2026. Source review current through September 3, 2026.
CMS introduced three APCM behavioral-health add-on codes for 2026. The policy creates a new way for qualifying primary care practices to report General Behavioral Health Integration and the Psychiatric Collaborative Care Model alongside Advanced Primary Care Management.
The difficult part is not knowing the code numbers. It is turning patient identification, consent, care planning, monthly service documentation, EHR records, and claim review into one dependable operating process.
Sematic now supports that process for participating athenahealth-connected APCM practices. The workflow covers all three add-ons:
| Code | Care model | When it applies |
|---|---|---|
| G0570 | General Behavioral Health Integration | A qualifying General BHI patient-month |
| G0568 | Psychiatric Collaborative Care Model | The first qualifying month in a CoCM episode |
| G0569 | Psychiatric Collaborative Care Model | A subsequent qualifying month in that episode |
Each add-on is reported with the same practitioner's APCM base service for the same month. Sematic derives the proposed add-on from the patient's setup, monthly documentation, and CoCM episode history. A billing user still makes the explicit decision to include it.
For the complete Medicare requirements behind these codes, read our source-verified guide to APCM behavioral-health add-ons. For the product workflow, use the step-by-step visual guide. This article focuses on how the new Sematic workflow operates.
One path from candidate review to claim
We designed behavioral health as an extension of the existing APCM workflow, not a parallel program staff have to reconcile at month-end.
Review a candidate
Sematic can surface a behavioral-health candidate signal from a supported condition on the patient's synced problem list. Staff can see the matched condition, its source, and the freshness of the available data before deciding what to do next.
The signal is intentionally narrow. It is a prompt for clinical review—not an eligibility determination, enrollment, consent, or charge. A clinician can also configure a supported diagnosis when the appropriate condition is not available as a candidate signal.
Configure the care model
For an appropriate APCM patient, an authorized user chooses General BHI or CoCM and reviews the behavioral-health diagnosis and effective month. General BHI uses the patient's existing APCM billing practitioner and adds a designated continuity team member. CoCM instead uses the practice's configured care-manager, psychiatric-consultant, registry, and weekly review arrangements.
Setup changes apply prospectively. Saved monthly evidence keeps the setup that applied when the work was documented, so a later configuration change does not silently rewrite a prior month.
Capture consent and confirm the record
Practices may capture APCM and BHI consent in one conversation for a new enrollment, or record BHI consent separately for an existing APCM patient. The workflow covers behavioral-health services, relevant specialist consultation, possible cost sharing, and the patient's ability to stop BHI without ending APCM.
Sematic sends the consent record to Athena and requires confirmation before that consent can support billing. If Athena returns an uncertain result, the item moves to review instead of being posted again automatically.
Keep one care plan
Behavioral-health goals, monitoring, coordination, and team responsibilities belong in the patient's existing APCM care plan. Sematic does not create a second plan that can drift away from the primary-care record.
That matters operationally. Primary and behavioral health are integrated in the care model, and the software should reflect the same relationship.
Document a General BHI month in one guided action
For a fresh General BHI month, staff select Document [month] BHI service in the existing Documentation workspace. The guided action captures the service date, one concise patient-specific note, the applicable validated scale and score, and an explicit confirmation that assessment or monitoring, care planning, treatment coordination, and continuity were furnished.
Saving creates the supporting Care Event and immediately attempts to write the monthly summary to the patient's monthly APCM Patient Case in Athena. A clean General BHI month does not require four progress tasks or a separate routine finalization step.
Build detailed CoCM evidence from Care Events
CoCM uses dated, patient-specific Care Events because the initial and subsequent services contain different required areas. One event can cover several areas when the same interaction addressed them; work performed in another interaction remains a separate event.
Sematic shows which areas are covered and which are still missing. The requirements are derived from the patient's episode and include the applicable assessment, registry, psychiatric consultation, collaboration, brief intervention, and outcome-monitoring work.
An existing Care Event can contribute, but Sematic never infers qualifying behavioral-health work from its prose. An authorized user must explicitly identify the areas that the event supports.
Document detailed months in Athena
When every required area is covered, an authorized user reviews the detailed record and selects Document in Athena. This path applies to CoCM and to General BHI months that already contain partial, multi-event, or pre-release documentation. Sematic creates an immutable evidence snapshot and writes a concise summary to the monthly APCM Patient Case in Athena.
The add-on becomes ready for billing only after the exact monthly evidence is complete and its Athena write is confirmed.
Include the add-on at billing review
In individual billing, staff select Include add-on and review any blockers before submission. In bulk billing, staff can choose to include all ready add-ons and review totals by code alongside patients that still need attention.
The choice is explicit in both paths. If a selected add-on becomes stale or fails revalidation, Sematic stops that patient's claim rather than silently submitting APCM alone. Other eligible patients in a bulk batch can continue.
Sematic does not automatically amend a previously submitted APCM-only claim to add behavioral health. Billing staff should make the add-on decision before submitting the base claim.
What we deliberately did not add
The workflow has no second enrollment, separate monthly report, duplicate care plan, timer, or user-managed code sequence. These services are not billed from a diagnosis, a feature being enabled, or a generic statement that the practice has behavioral-health capabilities.
If a billing user does not select a behavioral-health add-on, the ordinary APCM path remains the ordinary APCM path. Sematic does not add a charge automatically.
We also treat uncertain EHR writes differently from definitive failures. A definite failure may be corrected and retried. An ambiguous result requires someone to verify the record in Athena before confirming it. That friction is purposeful: repeating an uncertain documentation or claim action can create a duplicate.
Where Sematic helps—and where the practice decides
Sematic organizes available data, guides consent and setup, structures monthly evidence, writes selected documentation to Athena, checks readiness, derives the proposed code, and prepares the base and add-on charges for review.
The practice remains responsible for:
- Determining whether the patient and practitioner meet current CMS and payer requirements.
- Confirming the diagnosis, medical necessity, actual services furnished, and appropriate code.
- Maintaining qualified staffing, coverage, CoCM team arrangements, and an operating registry.
- Ensuring consent and the legal medical record are accurate and complete.
- Reviewing payer policy, claim conflicts, coverage, edits, denials, and final submission.
At launch, Sematic does not collect or enforce evidence of a potentially required BHI initiating visit. Practices must confirm that requirement through their own process before furnishing or billing the service. Sematic can only surface information available from approved athenahealth departments, so records held elsewhere may also need manual verification.
Availability is enabled for participating organizations after configuration and launch checks. The practice must have the three procedures configured correctly in Athena, and CoCM requires a validated team profile and operating registry. Sematic does not store payer-specific billing policy or guarantee coverage or payment.
A practical way to launch
Start with a controlled cohort rather than the entire candidate panel. Confirm Athena procedure configuration, user roles, consent language, the initiating-visit review process, CoCM staffing when applicable, and where the final notes appear in the chart. Then work several patients through setup, documentation, Athena confirmation, and billing review before expanding.
The goal is straightforward: when billing staff reach month-end, they should be reviewing a complete record—not reconstructing the month across spreadsheets, inboxes, and disconnected notes.
This article describes Sematic's software workflow. It is not legal, coding, billing, reimbursement, or clinical advice. Practices should confirm current CMS guidance, payer rules, state requirements, and patient facts before furnishing or billing services.