Direct Primary Care (DPC) is all the rage in benefits circles. Employers see it as a way to cut costs, boost satisfaction, and give employees the kind of doctor relationship that feels personal. And they're not wrong. On paper, it's a dream. But after years of building and fixing benefits systems, I've run into a reality that almost nobody talks about: DPC breaks every data flow your HRIS, TPA, and stop-loss carrier rely on. It's a claims-free model dropped into a claims-driven world, and the friction is real.
Let me show you what I mean, starting with the stuff that keeps benefits administrators up at night, the stuff that never makes it into the glossy vendor brochures.
Your HRIS Doesn't Know What to Do with DPC
Traditional health plans work like clockwork. Eligibility files travel from your HRIS to the carrier. Claims files come back. Utilization reports get generated. Everyone knows who's enrolled, what they used, and what it cost. DPC flips that script completely. Instead of a per-claim cost, you pay a flat monthly fee. No CPT codes. No encounter data. From your system's perspective, it looks like a Netflix subscription, not a health plan.
Most HRIS platforms aren't equipped to handle that. The result is a manual mess: spreadsheets, emailed updates, and portal uploads that need to be done by hand. When an employee leaves or changes status, the DPC clinic might not know for days or weeks. That's a HIPAA exposure waiting to happen. A terminated employee is still receiving care because the system never updated.
What you can do: Make your DPC vendor prove they can support standard eligibility formats (like 834 files) or at least offer an API that your middleware can talk to. If they can't, you're signing up for a compliance headache, not an innovation.
COBRA and the Excepted-Benefit Question
Employers sometimes treat DPC as an excepted benefit to sidestep ERISA and COBRA, but that treatment is not automatic. An employer-sponsored DPC arrangement can be treated as a group health plan, and bundling it with an HRA or a high-deductible health plan strengthens that analysis. For employers with 20 or more employees, that means COBRA applies. Your enrollment system needs to track DPC as a separate coverage tier, calculate its own COBRA premiums, and handle changes in status. I've yet to see a benefits administration platform do this out of the box. It usually involves custom scripts and a lot of testing.
And then there's billing. DPC fees are monthly, but your payroll runs biweekly. Getting the deduction code right, reconciling it against open enrollment elections, and handling leaves of absence is a puzzle that most teams have to solve themselves.
- Ask your DPC vendor if they have a COBRA-ready module or documented process for terminations.
- Check with your benefits admin platform (Workday, ADP, Rippling, etc.) whether they can handle a monthly deduction with real-time eligibility sync.
Stop-Loss and the Missing Primary Care Data
If you're self-funded, your stop-loss carrier needs claims data to set premiums and assess risk. Primary care visits are a key part of that picture, but under DPC, those visits generate zero claims. The carrier sees a member with no primary care utilization and often assumes that person is super healthy. In reality, they might be seeing their DPC doctor every other week. Those visits are just invisible to the carrier's model.
To fix this, you need a shadow claims file: a monthly extract from the DPC clinic showing visit counts, diagnoses, and risk scores. But few DPC providers automate this. The burden falls on your benefits team to manually export and format data for the TPA. That's time-consuming and prone to mistakes.
Negotiate this upfront. Before you sign, require the DPC clinic to produce a monthly flat-file extract (de-identified enough to protect PHI, but detailed enough for underwriting) that your TPA can ingest automatically. Some larger advanced primary care networks are beginning to offer this. Many do not. Don't assume it's included.
Compliance: ERISA, HIPAA, and ACA All Have Opinions
Each of these frameworks interacts with DPC in ways that your benefits systems must handle, and the complexities are rarely discussed.
Under the Hood of ERISA
If your DPC sponsorship is funded through an HRA, it may be considered a group health plan. That means you need a formal plan document, a summary plan description, and claims procedures, even though no claims will be filed. Your enrollment system must generate the right notices.
The HIPAA Handshake
DPC clinics are covered entities under HIPAA. When a clinic handles your employees' data on behalf of the plan, a business associate agreement should sit between the plan and the clinic. The bigger issue is how eligibility data travels to them. Standard SFTP from your HRIS is fine. But if the clinic's onboarding portal is a basic web form, imagine the risk: employee names, dates of birth, maybe even diagnosis codes flying over an unencrypted connection. Verify encryption in transit and at rest.
ACA Reporting Traps
DPC fees rarely count as minimum essential coverage. You still need to offer a qualifying health plan to avoid penalties. Your enrollment system must clearly mark DPC as supplemental, not a replacement. I've seen employers check the wrong box on Form 1095-C because their system treated DPC as a health plan. That can trigger fines.
Best practice: Have a compliance consultant map your exact arrangement, then audit your enrollment system for every reporting touchpoint.
You're the Integrator
Most DPC vendors are small clinics with basic tech. Even the bigger networks have simple member portals that don't support modern HRIS integration. The integration work falls on you. You become the system integrator.
Here's a practical checklist to reduce the pain:
- Conduct a tech review during vendor selection. Ask about real-time eligibility via API, 834 file support, and HIPAA-compliant data exports.
- Use a middleware layer, a benefits admin platform like PlanSource or bswift, to normalize DPC data into the same format as your medical plan.
- Build a reconciliation dashboard that shows DPC membership, utilization (from shadow claims), and cost trends alongside traditional claims. This gives you one story to tell your CFO and stop-loss carrier.
DPC and HSAs: The 2026 Rule Change
One DPC compliance question used to dominate every employer conversation, and the 2026 tax law changed the answer. For years, a worker covered by both a high-deductible health plan and a DPC membership faced a catch-22. The DPC arrangement counted as disqualifying coverage, so the worker lost the ability to contribute to a health savings account. That made DPC a hard sell for employers who pair an HDHP with an HSA.
The One Big Beautiful Bill Act, signed July 4, 2025, fixed this effective January 1, 2026. A qualifying DPC service arrangement no longer counts as disqualifying coverage for HSA purposes, as long as monthly fees stay at or under $150 for an individual and $300 for a family, with inflation adjustments starting in 2027. IRS Notice 2026-05, issued December 9, 2025, confirms that HSA funds can also pay the periodic DPC fees tax-free. If fees run above the caps, they can still be reimbursed from an HSA, but the employee loses HSA contribution eligibility for that period.
The change adds a new data flow. Your benefits system now has to track, per employee, whether the DPC fee sits under the cap, because that drives HSA eligibility. That is one more field to reconcile, alongside the eligibility sync and shadow-claims work. Plan for it the way you plan for the rest of the integration.
DPC Is a Great Product. Integration Is the Platform.
I believe in DPC. It can improve access, lower costs, and make employees feel cared for. But the industry has focused so much on the clinical and financial pitch that it forgot about the plumbing. Right now, DPC sponsorship is often held together by manual emails, spreadsheets, and custom scripts.
That's not scalable. To do this right, across multiple locations, with different carriers and underwriters, employers need to demand better systems from DPC vendors. And benefits administration platforms need to extend their capabilities to handle a claims-less benefit.
Until then, the smartest organizations will treat DPC sponsorship as a project, not a plug-in. They'll budget for integration resources, compliance checks, and custom data bridges. The clinics are warm and accessible. The systems behind them need to be just as reliable.