EHR for Primary Care

What should an EHR for primary care do differently?

An EHR for primary care should track a whole patient panel, not just today's schedule. It needs care gap rules from USPSTF and ACIP guidance, chronic disease registries, multi-problem visit notes, a results inbox with owners, and workflows for transitional care management, chronic care management and Annual Wellness Visits.

Generic encounter templates assume one reason for the visit. A primary care follow-up often covers blood pressure, a diabetes check, a refill and an overdue screening in the same note, and each item needs its own assessment, plan and diagnosis code.

How does a primary care day run through the EHR?

A primary care day moves through five handoffs, and each one depends on data the previous step produced. When one step lives outside the record, staff fill the gap by hand.

• 1. Huddle: Before clinic, the care team reviews a pre-visit list built from the day's schedule: open care gaps, results waiting for review, recent hospital discharges and refills due. The list should come from structured data, not from someone reading charts the night before.
• 2. Rooming: The medical assistant reconciles medications and allergies, records vitals and runs screening questionnaires such as the PHQ-9, so the scores file as discrete values. Standing orders let the assistant queue a vaccine or screening order for the clinician to sign.
• 3. Visit: The clinician documents each problem with its own assessment and plan, linked to an ICD-10-CM code. Orders, e-prescriptions and referrals are placed from the problem they belong to, which keeps the reason for each order on record.
• 4. Inbox: Results, refill requests, portal messages and outside documents land in pooled queues with a named owner. A nurse or medical assistant closes what protocols allow, and only the rest reaches the clinician.
• 5. Outreach: Between visits, staff work registry lists: patients overdue for a visit, chronic conditions out of control, recent discharges that need a call. Each attempt and its outcome is recorded so the next person sees what happened.

The record has to carry all five steps for the same patient. A product that handles the visit well but leaves the inbox and outreach to spreadsheets moves the work around instead of removing it.

Care gaps, registries and the panel

A care gap engine compares each patient's age, sex, conditions and history against screening and immunization rules, then lists what is due. The rules come from published guidance: USPSTF recommendations for screening and the CDC immunization schedules built on ACIP recommendations.

• Rule inputs: Date of birth, sex recorded for clinical use, active problems, dated procedure history, immunization history from the state registry, and exclusions such as a documented prior procedure or a recorded patient refusal.
• Outside results: A colonoscopy or mammogram done elsewhere must be entered as a dated, coded procedure. A scanned report with no structured date leaves the gap open and keeps the patient on the recall list.
• Registry views: Lists of patients by condition and control status, such as diabetes with the last A1c above the practice's chosen threshold or no A1c in the past year, shown with the last visit date and the assigned care manager.
• Attribution: The panel is the set of patients the practice is responsible for, and it can differ by payer contract. Store the attribution source and date for each patient so registry counts can be reconciled with payer reports.

Quality measure logic is a separate layer. Electronic clinical quality measures have published specifications, and the measure engine reads the same structured fields the care team fills in. A value that only appears in narrative text will not count toward the measure.

Which billing codes shape primary care workflows?

Care management codes decide which timers, contact logs and consent fields the EHR must hold. Each code family has its own timing and documentation rules, published by CMS.

• Transitional care management: CPT 99495 and 99496 require an interactive contact with the patient or caregiver within 2 business days of discharge, then a face-to-face visit within 14 days for 99495 or 7 days for 99496 (CMS MLN Transitional Care Management Services booklet).
• Chronic care management: Medicare pays CCM under CPT 99490, 99439, 99491, 99437, 99487 and 99489 for patients with two or more chronic conditions, with monthly care management time recorded by staff and date (CMS MLN Chronic Care Management Services booklet).
• Advanced primary care management: HCPCS G0556 to G0558 have been payable since 2025 and bill care management as a monthly bundle, so the EHR tracks enrollment and the service elements rather than minutes.
• Remote physiologic monitoring: The CY 2026 Physician Fee Schedule final rule (CMS-1832-F) added 99445 for 2 to 15 days of device data and 99470 for the first 10 minutes of management, alongside 99453, 99454, 99457 and 99458.
• Annual Wellness Visit: Medicare covers an initial Annual Wellness Visit (G0438) and subsequent visits (G0439), each with a health risk assessment the practice can collect before the patient arrives.

In the build, each code family becomes a structured record: eligibility, consent where the code requires it, contact or time entries with staff and date, and the visit or month that closes the episode. Billing staff then work from the record rather than from memory.

Which interfaces does a primary care EHR depend on?

Five external connections carry most of the data a primary care team acts on. Each needs a named owner, a test environment and a monitoring alert before go-live.

• Reference labs: HL7 v2 ORM or OML orders go out and ORU results come back, with LOINC codes on each result so flowsheets and care gap rules can read them. Local lab codes that were never mapped leave trends empty.
• Immunization registry: ONC certification criterion 45 CFR 170.315(f)(1) covers transmission to immunization registries. State registries use HL7 v2 VXU messages for updates and QBP queries to return a patient's history, so the practice sees doses given elsewhere.
• Hospital event notifications: Under the CMS Conditions of Participation at 42 CFR 482.24(d), hospitals must send admission, discharge and transfer notifications to the primary care practitioner the patient identifies, often through an HIE. That feed starts the TCM clock.
• Referrals: An outgoing referral needs a tracked status, from sent to scheduled to consult note received, with an owner who chases it when the note does not arrive.
• Third-party apps: Certified EHRs expose a read API under 45 CFR 170.315(g)(10). An app that must write back, such as a tool that files a closed care gap, needs the vendor's own write API or an HL7 v2 interface.

Where primary care EHR projects break

• Scanned outside screenings: Reports filed as images without a coded procedure and date keep gaps open, so the patient gets recall letters for a test already done.
• Every message to the physician: Routing portal messages and refills straight to the clinician skips the protocols that let nurses and medical assistants close routine items.
• No discharge feed: Without hospital event notifications, the practice learns about an admission at the next routine visit, long after the 2 business day TCM contact window has closed.
• Alert stacking: Turning on every care gap and interaction pop-up at once teaches clinicians to dismiss them. Start with a short list and add rules based on override data.
• Split care management tools: When CCM time or RPM readings live in another system, staff copy totals by hand and the audit trail splits in two.
• Stale problem lists: Resolved acute problems left active, and chronic conditions never updated, make registry lists and decision support wrong for that patient.

What should a primary care group test before go-live?

Test with real visit types and real staff roles, not a vendor script. The checklist below covers the paths that tend to fail without anyone noticing.

• 1. Multi-problem visit: Chart a chronic follow-up with four problems, two orders and a refill, and confirm each order carries its diagnosis.
• 2. Well-child visit: Record vaccines, confirm the VXU message reaches the state registry test system, and query the history back.
• 3. Care gap closure: File an outside colonoscopy with its date and code, and confirm the gap closes and the patient drops off the recall list.
• 4. Discharge to TCM: Send a test ADT discharge, confirm a task appears with the 2 business day due date, and log the contact.
• 5. Inbox routing: Send a lab result, a refill request and a portal message, and confirm each lands in the right pool with an owner.
• 6. Access and audit: Confirm each role sees only what it needs, sessions time out on shared workstations, and every chart access is logged with user and time.

The HIPAA Security Rule at 45 CFR 164.312 requires unique user identification and audit controls. Multi-factor sign-in is good practice and appears in the January 2025 HHS proposed rule, but it is not yet a stated requirement.

How Agnotic can help

Primary care groups rarely need a new EHR to fix panel work. Agnotic Technologies builds the pieces around the record: care gap and registry tools over the EHR's FHIR API, lab and immunization interfaces, hospital event feeds that open TCM tasks, and CCM and RPM time logs that file back into the chart.

Agnotic scopes that work to the EHR the group already runs, including what its vendor allows for write-back, so the team knows which parts need an interface and which can run as an app.

Sources

• CMS MLN: Transitional Care Management Services booklet
• CMS MLN: Chronic Care Management Services booklet
• CMS: CY 2026 Physician Fee Schedule final rule fact sheet (CMS-1832-F)
• 42 CFR 482.24: Condition of participation, medical record services (patient event notifications)
• 45 CFR 170.315: ONC certification criteria, including (f)(1) immunization registries
• ASTP/ONC: Standardized API for patient and population services, 45 CFR 170.315(g)(10)
• 45 CFR 164.312: HIPAA Security Rule technical safeguards
• HHS: HIPAA Security Rule notice of proposed rulemaking (January 2025)