What an employer eligibility file should contain, how new hires and departures should flow into your EMR, and how to catch a wrong or partial file before it touches billing.
An employer eligibility file is the roster an employer, or its benefits vendor, sends a direct-care practice on a schedule, listing who is covered, from when, and until when. When the file feeds straight into the practice's EMR, new hires are enrolled and departing employees are terminated on the dates in the file, and nobody retypes a roster.
When it doesn't, the roster drifts. The employee who left in March is still on April's invoice, and the new hire who calls to book isn't in the system. Employer contracts renew on trust in the invoice, and drift erodes it one line item at a time.
Rosters drift because employment changes every week and the practice hears about it last. Hires, departures and new dependents start in the employer's HR or payroll system, and an emailed spreadsheet waits on someone remembering to send it.
The stakes are rising as more employers buy primary care directly. In the KFF 2025 Employer Health Benefits Survey, 7% of firms with 50 or more workers that offer health benefits said they contract directly with an organization to provide primary care, and 67% of covered workers were in self-funded plans. Each of those contracts is a roster that has to stay right.
A usable eligibility file identifies each person, ties dependents to the employee, and carries the dates that decide coverage. At a minimum, ask the employer or its file sender for:
Agree on these fields before the contract starts. Most roster problems trace back to a file that never carried a term date or a plan name.
In SigmaMD, Eligibility Sync processes each file automatically and updates the employer's roster: existing employees are updated, new ones are added, and everyone in the file appears in that employer's Eligibility Sync tab (Eligibility Sync Overview). Setup is a one-time request. The practice tells SigmaMD support which employer to connect and who will send the file, and SigmaMD configures the connection (Steps to Establish Connectivity).
A new hire should get a chart and a membership on their benefit start date, with dependents attached, without anyone at the practice touching the record.
In SigmaMD, automatic enrollment does exactly that, per employer (Automatic Enrollment with Eligibility Sync). The practice picks a default location and clinician for charts created from the file. The membership then starts on the benefit start date, or the hire date when there is none. Future dates wait until the date arrives, so no chart looks active before coverage begins. Dependents are added to the employee's membership as extra seats, youngest first, up to the plan's seat limit.
The cases that need judgment stay with the practice. If an employee matches an existing patient, SigmaMD does not create a duplicate chart. It emails the practice admins so they can link the records from the Eligibility Sync tab (How to Enroll and Link Patients to Group Plans).
A termination should end the membership, and dependents' coverage with it, on the term date in the file, while leaving the care team time to close out care.
In SigmaMD, automatic termination cancels the membership at 11:59 pm on the term date, or the benefit end date when there is no term date (Automatic Termination with Eligibility Sync). Charges for later cycles come off the employer's draft invoice. Two settings match the contract:
An employee who simply drops out of the file is not terminated. That is deliberate: a partial file would otherwise cancel memberships in bulk. Only a term date or a benefit end date ends a membership automatically.
A wrong file should be held before it changes anything. A roster sent for the wrong employer can look perfectly valid row by row.
In SigmaMD, a file is held for review, with no records changed, when many of the people in it already belong to another employer of the practice, or when its number of employees changes by more than 50% from the previous file. The employer's Eligibility Sync tab shows a banner with the reason, and practice admins get an email with a link to the file. They can download it, process it, or discard it and ask for the correct one. A held file enrolls no one.
When a file or some of its rows fail, SigmaMD emails practice admins, plus up to five extra recipients per employer, such as the file sender. Their copy leaves out member names and asks for a corrected file.
An employer that offers more than one membership, for example one for PPO members and one for HSA members, can send a single file as long as each row carries the plan name. In SigmaMD, the plan name in the file is matched against the employer's membership plans, and each employee is enrolled in the matching one. A plan name that matches nothing is skipped with an error email, never guessed.
| Roster task | Manual updates | Eligibility Sync in SigmaMD |
|---|---|---|
| New hire | Chart and membership created by hand when someone remembers | Enrolled on the benefit start date, with a chart |
| Dependents | Added seat by seat | Added to the employee's membership up to the seat limit |
| Departure | Canceled after the invoice is disputed | Canceled on the term date, plus any grace period |
| Several plans | Sorted from a spreadsheet column | Routed by plan name in the file |
| Wrong or partial file | Noticed when patients call | Held for review before any record changes |
| Bad rows | Forwarded to the employer by hand | Error email to admins and up to five extra recipients |
No. A small employer with a handful of employees can run without one. In SigmaMD, a practice can create an employer enrollment link that lets employees sign themselves up for the employer's plan (Steps to Create an Employer Enrollment Link), or enroll them by hand. Eligibility Sync earns its keep once keeping the roster current becomes a weekly job.
The chart created from the file is a normal SigmaMD chart, so the new member can book and be seen right away. At the first visit, SigmaMD Scribe records the conversation with the patient's consent and drafts the note in the practice's own template for the physician to review and sign. When a new member's prior records arrive by fax, Sigma AI summarizes them, including abnormal results and requested follow-ups, before anyone reads every page (Summarizing Documents with Sigma AI).
For winning the contract in the first place, see 5 strategies to attract employer partnerships, how to measure healthcare ROI for employers, and how direct-care practices work with third-party administrators.
A recurring roster from an employer or its benefits vendor listing who is covered under its direct-care contract, with dependents, plan names and coverage dates.
No. In SigmaMD, only a term date or a benefit end date in the file triggers an automatic termination. Someone who stops appearing in the file keeps their membership until the practice acts.
No. In SigmaMD, automatic enrollment and automatic termination are separate settings for each employer and are off by default, so a practice can automate one employer and keep another manual.
If employer contracts are part of your practice, book a demo of SigmaMD and bring a sample roster. We will show you how it enrolls, terminates and flags a bad file.
A 30-minute walkthrough to review your workflow in SigmaMD and answer your questions.
Book a demo