Guide · Population health

Population health management, explained by the work.

A working guide for practice administrators, MSO leaders, analysts, and data stewards: what the work is, how it branches, who does each piece, what the year looks like, and where it usually breaks.

By Jonan Portal Alvarez, Chief Executive Officer, Alara Healthcare (management services) · Updated September 10, 2026 · About 12 minutes

Start here

What the work is

Population health management is the work of taking responsibility for a defined group of patients, knowing what each of them needs this year, and getting it done. The group is not everyone who walks in. It is the panel a payer or a program has attributed to you, and it is the panel your contract pays on. Everything else in the field hangs off that definition.

The phrase gets used three ways, which is where most of the confusion starts. Public health uses it for the outcomes of a whole community. Vendors use it for dashboards that score a population. Practices paid under value-based contracts use it for something more specific: the operating discipline that turns an attributed panel into visits, documentation, submissions, and closed gaps before the year ends. This guide is about the third meaning, because that is the one that shows up at reconciliation.

Stripped to its parts, the work is three loops that run all year.

Know who

Who is attributed to you this month, under which method, and who arrived or left since last month. If the panel is wrong, every figure downstream is wrong, and nobody finds out until the plan reconciles.

Know what

For each member, what the data says should happen this year and has not yet been shown to happen: a chronic condition not re-documented, a screening not on file, a discharge with no follow-up. Each is a gap, and each branch counts gaps in its own unit.

Get it done

Someone owns each gap, works it, and the closure is measured against the payer's answer rather than the practice's belief. This is the loop most tools skip, and the one that decides whether the first two mattered.

Care management, which many practices already do, is one branch of this: the coordinated follow-up of the highest-risk members. Value-based care is the contract: how you are paid. Population health management is what you do between the two so that the contract pays.

How it branches

The five branches

People who know the work start here and pick a branch. The branches share data and people, but each has its own calendar, its own payer rules, its own unit of work, and its own definition of done. Here they are in the order the data flows.

Branch 1Panel 360
Attribution and the panel
Who are we responsible for, and why did the list change?
The payer's roster names, for each member, the provider who is accountable. Some programs compute attribution from where the member actually received primary care instead. Either way, the panel is read from files somebody sent you, it moves every month, and a member who leaves is learned about one roster late. The panel is not a performance measure. It is the denominator for every measure that follows.
Who owns it
The analyst reconciles the roster against the practice's own records; the administrator signs off on the panel the contract pays for.
Its calendar
Monthly, with the roster. The plan year resets enrollment in January.
Where it breaks
Working from the scheduling system's patient list instead of the attributed panel, so effort lands on people the contract does not pay for and misses people it does.
Read the Panel 360 page Guide: patient attribution
Branch 2Risk IQ
Risk adjustment
Which chronic conditions still need to be documented this year, and what are they worth?
Under the CMS-HCC model, a chronic condition counts toward a member's risk score only when it is documented in a qualifying face-to-face encounter and submitted in the current year. Scores reset every January 1. The work is recapture (re-documenting last year's conditions), suspects (conditions the evidence points to but nobody has documented), and submissions (getting the diagnoses to the payer in a format it accepts), followed by audit readiness, because a code you cannot support is worse than a gap.
Who owns it
Coders and documentation specialists work the queue and prepare suggestions; the provider rules on each one in the visit; the analyst ranks the queue by value and tracks the deadlines.
Its calendar
All year, against submission deadlines, with the pressure highest in the fourth quarter and the count starting again from zero in January.
Where it breaks
Ranking by count instead of value, chasing suspects with weak evidence, and finding out in the fall that half the panel has no visit scheduled.
Read the Risk IQ page Guide: the HCC recapture rate
Branch 3Q-Track
Quality
Which measures are we behind on, for which members, and what will count before the window closes?
Quality is two programs that share a name. HEDIS and Star Ratings gap closure is continuous: the plan reports, for each member and measure, what is not yet compliant, and the practice closes gaps with a screening, a result, a record, or an outreach that meets the specification. MIPS and MVP reporting is annual: the practice chooses measures, collects the year's data, and submits once. The first is a queue with owners. The second is a project with a deadline.
Who owns it
Care coordinators and quality specialists work the queue; the analyst keeps the scoreboard and the benchmark; the administrator chooses the MIPS measures and signs the submission.
Its calendar
The measurement year runs January to December. The MIPS submission window for the prior year opens in January and closes at the end of March.
Where it breaks
Starting gap closure in the fourth quarter, re-sending gaps the plan is still reconciling, and reading an on-screen MIPS score as the score CMS will give.
Read the Q-Track page Guide: the MIPS checklist
Branch 4Data Management
Data
Did the file arrive, was it readable, and is it correct?
Every figure in the other branches traces back to a file somebody sent: enrollment rosters, payer gap files, the year-end risk report, CMS encounter and payment files, claims, EHR extracts, lab results. Those three questions fail independently. A file can land and not be read because the payer added a column. It can be read and be wrong because a source changed how it codes a field. The data branch is where those questions get an owner, a calendar of what each source owes, and a grade.
Who owns it
The data steward, whose job is to say whether a number can be trusted and to prove it.
Its calendar
Continuous. Each source has its own cadence, and a late file is the ordinary state between deliveries, not a fault.
Where it breaks
Treating a file that arrived as a file that was read, and a row that loaded as a row that is correct.
Read the Data Management page Guide: Medicare Advantage payer files
Branch 5Care BridgeIn development
Care coordination and transitions
Who was just in the hospital, and who follows up?
This is the branch most people mean by care management: admissions, discharges, and emergency visits turned into follow-up within days, and the highest-risk members kept on a coordinator's list between visits. It runs on hospital event notifications and claims, and it succeeds or fails on the same thing as the other branches: whether the event becomes a task with an owner before the window closes. On the platform this branch belongs to Care Bridge, which is in development.
Who owns it
The practice's care coordinators and clinical staff, with the analyst supplying the list and the follow-up rate.
Its calendar
Daily. The follow-up window is measured in days, not months.
Where it breaks
Notifications arriving in an inbox nobody works, and follow-up counted as done when the call was attempted rather than when the visit happened.
Care Bridge on the platform page Guide: transitions of care

The Work List is not a sixth branch. It is where the five meet: any gap from any branch becomes an item with an owner, a due date, and a status, and its closure is measured back against the source it came from. Dashboard and Admin serve all five. Putting care gaps to work, the guide

The people

Who does the work

Titles vary by practice. The jobs do not. A small practice combines several of these in one person; an MSO staffs them across many practices. What matters is that every job has a name on it.

Practice administrator or MSO leader

Owns the contract and the calendar. Decides what gets worked first when everything is due, reads the scoreboard against the contract's targets, and signs what goes to the payer.

Population health analyst

Turns files into lists. Reconciles the panel each month, builds and ranks the gap lists by value, measures closure against the payer's answer, projects where the year will land, and can explain why any figure moved. The analyst is the person who knows which of two different open-gap counts you are looking at.

Data steward

Owns the sources. Knows what each payer owes and when, approves a layout change, decides how a new column maps, and grades whether a delivery can be trusted. When a number is questioned, the steward is who answers.

Coder or clinical documentation specialist

Works the risk queue. Reviews the chart for evidence of a condition, prepares the suggestion the provider will rule on, records the outcome, and prepares supplemental submissions the payer will accept.

Care coordinator or quality specialist

Works the quality and follow-up queues. Outreach, scheduling, records retrieval, and the evidence that closes a gap in the plan's eyes rather than only in the chart.

Front desk and scheduling

The branch nobody puts on the org chart. Every gap that needs a visit is only as real as the appointment, so the recall list, the annual wellness visit schedule, and the no-show follow-up are population health work.

The provider

Sees the member's open items in the visit, documents what is clinically true, rules on each suggestion, and decides care. Everyone else on this list prepares the visit. The clinical decision belongs to the clinician and to no one else.

The calendar

What the year looks like

Every branch runs on the calendar year, but their deadlines fall in different months, which is why a practice can be ahead on quality and behind on risk in the same week.

January
Risk scores reset, so last year's documented conditions count for nothing until they are documented again. The quality measurement year starts. New plan-year enrollment lands, and the panel changes more than in any other month. The MIPS submission window for the prior year opens.
Every month
A new roster moves the panel. Plan gap files and claims land with a lag of weeks to months, so a gap closed today stays open on paper until the plan acknowledges it.
By the end of March
The prior year's MIPS submission closes. Scheduling for the year's visits should already be under way, because the members who most need a visit are the hardest to book.
Mid-year
Supplemental submission sweeps and the halfway checkpoint: which measures are on track against benchmark, which members still have no visit, and which conditions have not been recaptured. What is not scheduled by now competes for fall capacity.
Fourth quarter
The last visits that count. Quality gap closure and risk documentation peak together, and the practices that started in January are not the ones working weekends.
After December 31
The measurement year closes, the plan reconciles, and the year's results become next year's baseline. Final submissions for the payment year continue into the following year on the payer's schedule.

The honest part

Where it breaks

In every population health program I have been part of, the tools did the same thing. They pointed at the problem. They returned a risk score, a gap count, a list of members sorted by something, and stopped. Nobody could build a work list from them, assign a gap to the coder, the coordinator, or the front desk, or show the provider the effect in the visit. So the analyst exported the report, built the real list in a spreadsheet, and the work moved by email.

That spreadsheet is the most honest artifact in population health. It is where the work actually gets assigned. It is also where the audit trail ends, where two people work the same member, where last month's version and this month's version disagree, and where the closure rate is whatever the person maintaining it believes.

The distance between pointing and doing has a name in this guide. A gap has been put to work when it has all six of these.

An owner: one named person, not a department.
A due date that comes from the branch's calendar, not from the day the list was made.
A status that separates worked from closed, and closed from acknowledged by the plan.
The evidence behind it, so the owner can see why it is a gap without opening three systems.
A path into the visit, so the provider sees it with the patient in front of them.
A closure measured against the payer's answer, so the practice's belief and the plan's record are reconciled instead of assumed.

Every branch fails the same way when one of those is missing. Risk fails when suggestions never reach the visit. Quality fails when closed gaps are never reconciled against the plan's file. Data fails when nobody owns the layout change. Attribution fails when the panel is somebody's belief instead of the roster.

Tools versus operations

What a platform can and cannot do

A platform is not the work. It is what makes the work assignable, measurable, and repeatable. Here is the honest boundary.

A platform can

Read the files and prove which ones arrived, were readable, and were correct.
Keep the panel current from the roster and store the reasoning behind each attribution.
Compute the gaps in each branch's unit and rank them by what they are worth.
Turn a gap into a work item with an owner, a due date, a status, and its evidence.
Show the provider the member's open items in the visit.
Measure closure against the plan's file, and pace beside quality, so volume alone never passes as work.

A platform cannot

Decide what care a patient should receive. That is the clinician's decision, in the visit, every time.
Fix a source that sends wrong data. It can catch it, grade it, and name the steward; the steward still has to call the payer.
Replace the person who owns the queue. A queue nobody owns is a report with extra steps.
Schedule the visit. The list is only worth what the front desk books.
Make a disputed panel undisputed. If the roster is wrong, that is a conversation with the plan.

This is the boundary Alara Population Health is built on. It shows the problem, hands it to the person who can fix it, and measures whether they did. See the platform

The MSO

Where a management partner fits

A management services organization exists for practices that want the results of this work without building the whole team. It takes the administrative and data side: the panel reconciliation, the file operations, the coding review and submissions, the quality outreach queue, the contract analytics, and the reporting to the payer. It does not take the clinical side. The practice's clinicians decide care, and a management partner has no authority over that.

Alara Healthcare is that kind of partner. It runs the work on Alara Population Health for practices that want it run, and it supplies the platform to MSOs, IPAs, ACOs, and health plans that run the work with their own teams. Either way the fee is set in advance at fair market value, never as a share of revenue and never tied to the volume or value of referrals.

What the services cover, branch by branch, and how the two companies are kept separate: What an MSO does, the guide

Questions people ask

Questions about population health management

What is the difference between population health management and care management?

Care management is one branch: coordinated follow-up for the highest-risk members, usually by a nurse or coordinator in the practice. Population health management is the whole: knowing who you are responsible for, what each of them needs this year, and getting it done across the panel. Most practices that say they do care management are doing one branch well and the others by spreadsheet.

What does a population health analyst do?

Turns files into ranked lists and explains the figures. Each month the analyst reconciles the attributed panel against the roster, rebuilds the gap lists for risk and quality, ranks them by value, measures closure against the payer's acknowledgment, and projects where the year will land. The best ones can say, for any number on any screen, which population it counts and why it moved.

Is population health management the same as value-based care?

No. Value-based care is the contract: how you are paid, on which measures, with how much risk. Population health management is the operating work that decides whether you perform under it. A practice can hold a value-based contract and do none of this work. The reconciliation is where it finds out.

Do you need software to do population health management?

Not to start. A single practice with one person who owns the list can run a year on a spreadsheet. The spreadsheet stops working the month two people work the same list, the payer changes a file layout, or someone asks for the closure rate against the plan's file. Software earns its place when it answers three questions the spreadsheet cannot: did the file arrive and was it right, who owns each gap, and did the plan agree it was closed.

How large does a practice have to be?

Large enough to have an attributed panel and one person who owns the list. Headcount matters less than ownership. Practices that want the results without building the team are what a management services organization is for.

What exactly is a gap?

Something the data says should have happened for a specific member this year and has not yet been shown to have happened. The unit differs by branch: risk adjustment counts conditions awaiting re-documentation, HEDIS counts member-and-measure pairs the plan reports non-compliant, and MIPS counts eligible patients who have not met a measure. That is why two screens can show different open-gap counts and both be right.

Where does the management partner end and the practice begin?

The partner does the administrative and data work: files, panels, queues, coding review, submissions, outreach logistics, analytics, and payer reporting. The practice's clinicians decide what care a patient receives, document it, and rule on every suggestion. Nothing a management partner does changes who makes the clinical decision.

Request a demo See the platform

Bring your own panel to the demo.

We will load a sample roster and gap file and show you where each branch's work lands, and who owns it.

Request a demo +1 (786) 659-1661