CalAIM reporting in Salesforce works when you capture a small set of facts correctly at the moment of service: who the member is, which program and plan they belong to, what service was delivered, by whom, and when. Reports for plans, funders and leadership are then views of that data. The reporting formats and due dates come from your contracts with each Medi-Cal managed care plan, so confirm those first. This post is about reporting; for payment models and codes, see CalAIM billing explained.
This is general information, not legal, billing or compliance advice.
Who asks for what
Several audiences want CalAIM data, and each wants something different.
- Managed care plans want data on the members you serve and the services you deliver. DHCS has published data exchange guidance for Enhanced Care Management (ECM) and Community Supports, including a standardized "Return Transmission File" for provider reporting that is separate from claims and invoices (DHCS provider reporting webinar, checked November 2026). That material dates from 2021 and 2022, and plans may require their own formats, so ask each plan what it needs today.
- Funders and county partners want counts and outcomes.
- Your finance team wants services tied to payers so it can match payments.
- Your leadership and board want trends and capacity. See our nonprofit board report template.
Start with the data model
Reports are only as good as the records behind them. A workable CalAIM setup in Salesforce usually tracks:
- The member. One record per person, with a plan membership identifier handled according to your privacy rules.
- The program enrollment. ECM, a housing support, CHW services or another program, with start and end dates and status.
- The plan or payer. Which managed care plan covers the enrollment.
- The service record. Each contact or service: date, type, staff member, duration, outcome.
- The funding source. Derived from the program and plan, not typed by staff each time. We explain this in program management and funding source assignment.
If any of these live in free text or spreadsheets, the reports will need manual cleanup every month.
The reports most teams build
- Active enrollment by program and plan. Who is enrolled right now, and who is about to leave.
- Services delivered by period. Counts by service type, staff member and plan.
- Member activity gaps. Enrolled members with no contact in a set number of days, so staff can follow up before a monthly requirement is missed.
- Outreach and enrollment pipeline. Who has been contacted, who consented, who is enrolled.
- Reconciliation view. Services recorded versus what was billed or paid, so you can spot what is missing.
- Data quality exceptions. Records missing a required field, date or plan.
Start with these before adding dashboards for their own sake.
Where Salesforce helps
- Capture once. A service is entered as it happens, and every report reads the same record.
- Automation for funding source and flags. Rules assign the funding source from the program and flag members who need contact.
- Reports and dashboards by program, plan and period.
- Permissions so staff see only what they need. Reporting data often contains health information, so apply the checks in Salesforce permissions and PHI.
We built program tracking and funding source assignment for a California community health center. Submitting claims or files to a plan is a separate piece of work that we would scope with you.
Where Salesforce does not do it for you
Be wary of anyone who says CalAIM reporting is turnkey. Salesforce does not know your plan contracts. Someone has to translate each plan's requirements into fields, rules and report layouts. The effort depends on how many plans you contract with, how different their formats are, and whether files are sent by hand or by an integration.
If you also receive data from an EHR or exchange, see EHR integration with Salesforce.
A simple way to build it
- Collect the requirements. Get each plan's current reporting template or file specification, and note the due dates.
- Map every requirement to a field. If a required item has no field, add one. If a field has no requirement, ask whether you need it.
- Build the data entry first. Staff should be able to record a service in a minute or two. If entry is slow, data will be late.
- Add validation. Required fields, valid dates, one active enrollment per program.
- Build the reports from real test data. Compare each report against a hand count for one month before you trust it.
- Set a review rhythm. A short monthly check of exceptions catches problems while they are small.
Keep an owner for the system. CalAIM guidance changes, and a report that was right last year may not match this year's template.
Common problems we see
- Funding source chosen by hand, so reports disagree with billing.
- Services recorded days later from notes, so dates are wrong.
- One person, several records, which inflates counts.
- Reports built before the data model is settled, which then have to be rebuilt.
- Everyone can export everything.
Keep privacy in view
CalAIM reports often combine a member's identity with their health and housing needs. Build reports that give each audience only what it needs: aggregate counts for leadership and board, member-level detail only for staff and plans who are entitled to it. Limit who can export reports, and review that permission regularly. If you are unsure whether a particular disclosure is allowed, ask your compliance lead or attorney before you build it.
Frequently asked questions
Is there CalAIM software I can buy?
Yes, there are vendors that focus on CalAIM and Medi-Cal community-based providers, and many organizations use Salesforce instead. The right choice depends on your size, your plans and your existing systems. Ask any vendor which plan formats and reports they support today.
Can Salesforce produce the files a plan requires?
It can, with configuration. The exact layout comes from each plan, and an integration or a scheduled export may be needed.
Do I need Health Cloud for CalAIM reporting?
Usually not for enrollment, service and funding reports. Health Cloud matters when you must store clinical data. See Health Cloud for community health.
How often do the rules change?
Often enough that you should check. DHCS and plans update policy guides, codes and templates, so confirm current requirements with your plans and DHCS.
Can this support CHW services too?
Yes. CHW visits are tracked as services under a program. See community health worker case management software.
Get your reporting in order
If CalAIM reporting takes days each month, we can look at your data model and reports with you. Book a free Salesforce health check.