Service

eClinicalWorks document management automation for FQHCs: every fax, scan and report filed to the right chart

The short answer

eClinicalWorks document management automation means the incoming pile gets sorted, indexed and filed without a person opening every page. MediBOT works as digital staff inside eCW with its own named user account. It reads each fax, scan and attachment, decides what kind of document it is, matches it to the right patient, indexes it, and files it to the right chart. When the document is a lab result, it also enters the values into the open order. Anything it cannot match with confidence goes to a person. It never guesses.

This page is for the medical records lead, the clinical ops manager, the QI director and the CIO at an FQHC or other 330 center on eClinicalWorks. Puerto Rico, the USVI or the mainland. The fax pile looks the same everywhere.

What lands in the document pile at a health center

Walk to the front office at 8 a.m. on a Monday. This is what is waiting:

• The fax inbox. Hospital discharge papers, outside labs, specialist letters, payer notices. All of it arrives as images, most with a cover sheet and no index.
• Scanned paperwork. Forms patients filled out at the visit, records they brought from another office, signed consents.
• Lab results that arrived outside the interface or failed to match.
• Diagnostic imaging (DI) reports from the imaging center down the road.
• Procedure reports from colonoscopies, endoscopies and other outside procedures.
• Consult notes from the specialists your providers referred to.
• Patient surveys and screening forms, including health-related needs screenings collected on paper.
• Email attachments sent by outside offices to a shared mailbox.

Every one of these needs the same four decisions: what is it, whose is it, where does it go in the chart, and who needs to see it. Today a person makes those decisions one page at a time.

Why unfiled documents cost a 330 center

A document that is not filed to the chart does not exist for the care team.

• The provider opens the chart and does not see the consult note, so the follow-up visit starts from zero.
• The DI report sits unindexed, so the open order stays open and nobody knows the study came back.
• A colonoscopy report that never reaches the chart never reaches your screening measure, so UDS reporting in eClinicalWorks undercounts care your patients already received.
• Paper health-related needs screenings that are not filed cannot drive follow-up.
• The person who knows how to index the fax inbox goes on vacation, and the backlog doubles.

Health outcomes depend on the next step happening. The next step depends on the document reaching the chart.

How MediBOT handles documents inside eClinicalWorks (step by step)

1. Watch the intake. MediBOT watches the sources you point it at: the eCW fax inbox, a scan folder, the document queue, and any shared mailbox you include during setup. It runs nightly, so the morning team starts with a filed inbox instead of a full one.
2. Classify each document. Lab result, DI report, procedure report, consult note, patient survey, referral paperwork, payer notice, or other. Your team approves the category list and the eCW document folders each category maps to.
3. Identify the patient. It reads name, date of birth and account number from the page and matches them against eCW. If two patients could fit, it stops.
4. Index it. It sets the document category, the date of service, the sending facility and the responsible provider, the same fields a records clerk fills.
5. File it to the right chart. The document lands in the correct patient's chart, in the correct folder, attached to the open order when there is one.
6. Enter structured data where it applies. For lab results it extracts the values, validates them against the order and enters them. The detail is on the lab results automation page.
7. Send the exceptions to a person. Unreadable pages, missing identifiers, a patient it cannot confirm, a document type it does not recognize. Each one becomes a single work item for your staff, with the reason it stopped.
8. Leave a trail. Every action is logged under MediBOT's eCW user. Auditors see who filed what and when, the same as for any employee.

The rule behind all eight steps: if it cannot validate the patient, the document type or the destination, it does not write. One traceable queue item at a time.

Document types, one by one

Lab results. Classified, matched to the patient and the open order, values entered. See eClinicalWorks lab results automation.

DI reports. Classified as imaging, matched to the patient and the imaging order, indexed with the study date and sending facility, and filed so the order no longer shows open.

Procedure reports. Filed to the chart and attached to the order, so outside procedures your providers ordered show up where screening and follow-up lists look for them.

Consult notes. Indexed with the specialist and date, and filed to the patient's chart where the referring provider sees it at the next visit.

Patient surveys and screening forms. Indexed by form type and filed to the chart, so paper health-related needs screenings and satisfaction surveys are part of the record and not a stack in a drawer.

The fax inbox. The biggest source. Cover sheets are set aside, multi-patient faxes are flagged for a person, and each remaining document is classified and filed.

Email attachments. For centers that receive records by email, the attachments from the mailboxes you include in setup enter the same intake and follow the same steps.

Results alerts. Telling the care team that a specific result needs follow-up today is a separate build. Results alerts are scoped in an assessment, per center, with your clinical leadership deciding which results qualify and who owns them.

What stays with your staff

MediBOT does the clerical pass. Your team keeps the judgment.

• Providers still review and sign results.
• Nurses still call patients.
• Records staff work the exception list instead of the whole pile.
• Clinical leadership decides the categories, the folders and the rules.

MediBOT does not read a result to a patient, does not make clinical decisions and does not decide what care someone needs. It gets the document to the human who does.

Where this runs: Corporación SANOS and CommuniCare

MediBOT is not a pilot slide. It is running in community health centers today.

At Corporación SANOS, MediBOT automations have been in production since January 2025 against eClinicalWorks and five payer portals, and problem list cleanup is live today. César Montijo, Executive Director, has described side-by-side work through restructuring, a new EHR, and automation of the processes that were eating the day.

CommuniCare Health Centers in San Antonio is the named mainland center: analytics delivered, agent in pilot, inside their own AWS. PHI does not leave the tenant.

Across 3 Puerto Rico community health centers, MediBOT processed 16,990 automated transactions, redirected 1,088 staff hours, and touched 13,059 patient interactions during the measured period from December 2024 to July 2026. That is the combined total across the automations running in those centers, including eligibility, document and results handling, and problem list cleanup. Not one center. Not one workflow. We do not publish per-workflow numbers we have not measured.

See MediBOT in production for how we take an automation from shadow mode to live.

Where document management connects to the rest of eCW

Document management is the intake step. The other automations work on what it files.

• Lab results automation: values from result documents entered into the open order.
• Problem list and diagnosis cleanup: the chart the provider opens is current on diagnoses as well as documents.
• Eligibility verification in eClinicalWorks: coverage checked before the visit, written back to the chart.
• Payer portal automation: payer portal data pulled into eCW. Prior authorization and state portal lookups are scoped in an assessment.
• eClinicalWorks optimization for FQHCs: if the document folders, categories or order setup are wrong, fix the build first. Automation on a broken build files documents into the wrong places faster.

Who this is for

• FQHCs, CHCs and other 330 centers on eClinicalWorks.
• Centers where outside results, consult notes and DI reports still arrive by fax or scan.
• Medical records and clinical ops leads who own the fax inbox and the open-orders list.
• CIOs who need the automation to run under a named, permissioned account inside their own environment.

We have run managed IT for community health centers in Puerto Rico since 2017. The automation runs on an environment we already know how to keep up.

FAQ

What is eClinicalWorks document management automation?

It is software doing the clerical work of the eCW document pile: reading each incoming fax, scan or attachment, deciding what type of document it is, matching it to the right patient, indexing it and filing it to the right chart. MediBOT does this as a named eCW user and sends anything it cannot match with confidence to a person.

Which documents can MediBOT sort and file?

Lab results, diagnostic imaging reports, procedure reports, consult notes, patient surveys and screening forms, referral paperwork and payer notices. The sources are the eCW fax inbox, scan folders, the document queue and the shared mailboxes you include during setup. Your team approves the category list and the eCW folders each category maps to.

What happens when a document cannot be matched to a patient?

It does not get filed. MediBOT opens a single work item for your staff that says why it stopped, such as a missing date of birth, two possible patients or an unreadable page. A person decides. MediBOT never guesses a patient.

Does it replace our medical records staff?

No. It takes the repetitive pass through the pile so your records team works the exceptions and the work that needs judgment. Providers still review and sign results, and clinical leadership sets the rules.

Can it alert a provider when a document needs follow-up?

Results alerts are scoped in an assessment, per center. Your clinical leadership defines which results need follow-up and who owns them, and the automation opens a telephone encounter or task in eCW for that person. MediBOT does not make clinical decisions.

Does PHI leave our environment?

No. MediBOT runs inside your own AWS tenant and works through a scoped eCW user account with the same permission model as staff. Pair it with a current HIPAA security risk analysis so the new account is documented.

How do we start?

Book a discovery call. Bring one week of unfiled documents from the fax inbox and scan folder, and your open-orders count. We will tell you which document types MediBOT can file now, what stays human, and whether an automation assessment makes sense.

Start with one week of documents

Count what came into the fax inbox and the scan folder last week. Count how much of it is still not in a chart. That is your baseline.

Book a discovery call or ask for an automation assessment. We map your document workflow and show you what MediBOT can file tonight. Results alerts are scoped in an assessment and built to your protocol. See the product at medibot.health.

Humans first. Tech second.

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