Millennial Networks

    eClinicalWorks

    eClinicalWorks UDS reporting for 330 centers: why eBO is not the submission

    UDS is not a February project. It is the residue of every visit you already saw.

    If your plan is "run the eBO tables after the holidays and clean what is red," you are already late. EHB validation does not care that the report looked green in eClinicalWorks. It cares whether the visit was true: insurance at the date of service, the measure in the chart, the FTE that payroll cannot invent.

    This is written for the QI lead, CIO, and billing director at a 330 center in Puerto Rico or the USVI who already lives in eCW.

    UDS is produced every visit, not in February

    Uniform Data System is the annual report a Health Center Program grantee files with HRSA. The tables are not the work. The work is the encounter.

    Insurance status. Provider. Location. Service. Language. Zip. Sliding-fee category. Structured labs. Problem list. Blood pressure. A1c.

    If the front desk guessed the payer, if the satellite dropped mid-note, if the A1c lived in a PDF instead of the order, February will not save you. You will export fiction.

    A 330-center stack that cannot talk UDS will still "keep the servers up." The board will still ask why Table 4 does not match finance.

    UDS is an operations problem. Treat it like one.

    What eCW actually ships vs what a 330 center still has to defend

    eClinicalWorks publishes a real UDS package. Use it. Do not confuse it with the submission.

    What the vendor actually ships:

    • eBO UDS reports for ZIP, Tables 3A, 3B, 4, 5, 6A, 6B, 7, and 9D.
    • Exception reports that flag mapping, configuration, and provider errors. Updated for the calendar year.
    • Clinical Quality Worksheet: a flowsheet so a provider can see structured items that are still missing for the visit.
    • To-Do UDS alerts for gaps in care on the pre-visit list.
    • UDS+: a FHIR patient-level path. A vendor capability. Not a substitute for clean visits.

    What you still have to defend:

    • The insurance line that was last year's commercial product while the patient handed you Plan Vital plastic.
    • The hypertension denominator whose problem list is a decade of duplicates.
    • The diabetic A1c that never left the scanned document.
    • The Table 5 FTEs that were copied from job titles.
    • The Data Audit Report flags from last year that nobody mapped into this year's build.

    Green in eCW is a starting point. Dead in Triple-S, missing in the chart, or invented in payroll is still a finding.

    Table 4 insurance mix: if eligibility is a morning portal hop, Table 4 is already wrong

    Table 4 is not a finance report. It is insurance status at the visit.

    A 330 center has to know, at the window, whether this person is insured, underinsured, or uninsured. Get that wrong and you mis-file the visit and you apply or withhold a discount you cannot defend.

    Three ways Table 4 becomes fiction:

    1. You bill a payer that is not active. Denial. The UDS line still went out as insured.
    2. You register an insured patient as uninsured and slide the fee. Faster at the window. Wrong insurance mix. Wrong when HRSA asks how you verify coverage before you discount.
    3. You hold the visit until portals answer. Access drops. Health outcomes take the hit. The patient with health-related needs who already fought for this slot is the one who leaves.

    Mainland eCW shops treat eligibility as a 270/271 ping. Puerto Rico and the USVI are not that market. Coverage sits with Medicaid MCOs. How FQHC front desks verify eligibility in eClinicalWorks names the stack: Assertus, IMC, MCS, PSM, Triple-S.

    If eligibility is still a morning portal hop, Table 4 is only as good as whoever had time to finish the clicks.

    Tables 6B and 7: health outcomes, not a dashboard screenshot

    Table 6B is quality of care. Table 7 sits next door: hypertension control, diabetes control, BMI. These are health outcomes. Not a screenshot of a dashboard you showed the board.

    Denominators live in the chart. Numerators live in structured fields.

    Dirty problem lists wreck the hypertension universe. Labs stuck in documents wreck A1c. Eligibility-driven no-shows move the rate because the patient never sat down.

    eCW gives you the Clinical Quality Worksheet and the To-Do list. Those tools only help if someone works them before the visit, not in a reporting panic.

    MediBOT already publishes the operator prompts QI actually types:

    • Diabetic patients with A1c over 9, by provider panel.
    • Table 6B controlled hypertension versus last year.

    That is overnight staff reading the chart you already have. Production notes are in MediBOT in production. Official measure specs still govern. A prompt is not a numerator.

    Table 5 FTE vs payroll: the EHR will not do this for you

    Table 5 is not an eCW census. It is hours.

    FTE is hours worked divided by the center's full-time standard for that position. Report by work performed and licensure, not by job title. Include employees, contracted staff who are not paid by unit of service, volunteers, and residents. Do not shrink clinical FTE for vacation or CME. Do not import a Medicare intermediary definition of full time and hope it matches UDS.

    Payroll gives dollars and headcount. eBO Table 5 gives whatever was mapped. Neither notices a "care coordinator" who spent half the year as an MA. If Table 5 and Table 8A cannot be reconciled, that is operations, not a reporting week.

    Island constraint: bilingual documentation, satellite connectivity, sliding-fee category at the visit

    A mainland UDS checklist will not mention the west site on generator, a last-mile that fails while San Juan is still seeing patients, or a front desk that has to document in the language the patient actually used.

    Puerto Rico and the USVI add three constraints the extract cannot fix later:

    Bilingual documentation. Language on the visit is a UDS field. If the chart defaults to English because that was the template, Table 3B is already off.

    Satellite connectivity. A note that never left the exam room is not a visit you can report. Retrievable records are a Chapter 10 problem and a UDS problem at the same time.

    Sliding-fee category at the visit. The discount class belongs on that date of service. Parking an insured walk-in on sliding fee "for now" is how Table 4, the sliding fee discount schedule, and cash all lie together.

    Magaly López, Health IT Specialist at the PR Primary Care Association (HCCN for Puerto Rico and the Virgin Islands):

    As Health IT Specialist for the 330 Centers in Puerto Rico and the Virgin Islands, I have seen how Millennial's services have been fundamental in strengthening the technology infrastructure across our clinics. Their team has been a key ally in modernizing systems, enabling more agile, secure, and efficient care.

    How MN works the file: eCW optimization plus MediBOT data that already lives in the chart

    Millennial Networks is healthcare IT and MSP for FQHCs and CHCs in this region. Founded 2017. Ten-year mark: January 2027. Humans First, Tech Second. eClinicalWorks partner on our site. Use that as a filter, then ask whether the team can sit in the same chart as your QI lead.

    We do not treat UDS as a reporting engagement that starts in January.

    The file is:

    1. Build. Clinical Rules, Smart Forms, eBO mapping, exception reports that someone actually works.
    2. Coverage decision overnight. Eligibility written back to the chart so Table 4 is not a morning guess. MediBOT is digital staff with a named eCW account. At SANOS, those automations have been in production since January 2025 against eClinicalWorks and five payer portals.
    3. Structured clinical data. Problem list cleanup, lab values in the order, care-gap lists for 6B and 7. When it cannot validate, it does not guess.
    4. Operations wrap. Access, uptime, satellite restore. A table you cannot extract is not a table.

    At Corporación SANOS, César Montijo, Executive Director, described side-by-side work through restructuring, a new EHR, and automation of processes that were eating the day. CommuniCare Health Centers in San Antonio is named on medibot.health: analytics delivered, agent in pilot, inside their own AWS. PHI does not leave the tenant.

    Who this is for

    • QI, CIO, and billing leads at FQHC, CHC, and other 330 centers in Puerto Rico and the USVI.
    • Teams whose EHR is eClinicalWorks and whose payers are island Medicaid MCOs.
    • Leadership that treats UDS as every visit, not a reporting scramble after the holidays.

    FAQ

    What is eClinicalWorks UDS reporting

    It is the work of producing Uniform Data System tables from the eClinicalWorks chart: eBO extracts, exception reports, the Clinical Quality Worksheet, and the visits underneath them. The vendor ships the reports. The 330 center still has to defend insurance status, structured clinical data, and FTE that payroll will not calculate for you.

    Does eBO submit UDS to HRSA

    No. eBO prepares tables and exception lists inside eClinicalWorks. Submission still goes through HRSA's Electronic Handbooks, including UDS+ where that path applies. A green eBO run is not a filed report, and it is not proof the visit was true.

    Why does Table 4 not match finance

    Table 4 is insurance status at the visit. Finance is cash and claims after the fact. If eligibility was a morning portal hop, if an insured patient was slid "for now," or if Plan Vital plastic sat on last year's commercial line, the two files will disagree. Fix the coverage decision. Do not force the tables to kiss in a spreadsheet.

    Can MediBOT produce UDS tables

    MediBOT does not invent numerators. It is digital staff with a named eCW account: verified eligibility, structured labs it can validate, problem lists against an approved map, care-gap questions from your own data. Official specs still govern.

    Book a discovery call

    Bring last year's Data Audit Report flags and this year's eBO extracts. We will tell you what is mapping versus operations.

    Request a discovery call. Talk to Alberto. Thirty minutes.

    Millennial Networks · Metro Office Park Lot. 6, Suite 204, Guaynabo, PR 00968 · 4850 Tamiami Trl N, Suite 301, Naples, FL 34103 · 787-945-2260 · corp@mnetpr.com