Service

Pulling payer and state portal data into eClinicalWorks for Puerto Rico FQHCs

Two tabs. One is eClinicalWorks. The other is a payer portal. Your staff copies from one and types into the other. All day.

Member ID. Product. PCP assignment. Effective dates. Then the next patient. Then the next portal.

That is the swivel chair. In Puerto Rico it is still how most FQHC front desks and billing teams work. This page is about taking the chair away.

Why this is a Puerto Rico problem

On the mainland, most clinics solved eligibility with a clearinghouse. A 270 goes out, a 271 comes back, eCW shows green. Done.

The island is not that market.

• Vital coverage runs through MCOs, and the MCO portals hold the answer the clearinghouse does not.
• Medicare Advantage plans are a big share of the payer mix, each with its own portal.
• "Active" does not mean assigned to your centro. PCP assignment lives in the portal.
• Patients change MCO or product and the insurance tab in eCW still shows last year.

So the desk logs into portals after eCW comes back green. Every morning. And when the check is wrong, it is not just a denial. It is a visit filed with the wrong insurance status for UDS reporting and a sliding fee discount program decision you cannot defend.

What is live today: portal eligibility into the chart

This part is in production. It is the same workflow behind our eligibility verification in eClinicalWorks page.

Every night, MediBOT:

1. Reads tomorrow's schedule.
2. Opens each patient chart.
3. Checks the payer portals that answer for this market: Assertus, IMC, MCS, PSM, Triple-S.
4. Writes the verified result back to the chart in eCW.
5. Leaves a consolidated report for the desk.

The morning becomes exceptions only: inactive, unable to verify, PCP mismatch, product mismatch. Walk-ins still belong to a human.

When a portal changes its screens or a mapping goes stale, the fix is proposed and a person approves it before it ships.

What we scope for your workflow

Eligibility is the portal pull we run in production. Every center has more portal data it retypes. We build those per center, through an automation assessment:

• Prior authorization status from payer portals into eCW.
• Payer care gap and quality lists pulled into the chart before the visit.
• PCP panel and roster data from MCO portals.
• Claim status checks written back for billing follow-up.
• State and Medicaid program portal lookups your team runs by hand today.

We do not sell these as finished modules. We map the portal, the fields, where they belong in eCW, and who owns the exceptions. Then we build it and run it in shadow until your team trusts the output.

How it works inside eClinicalWorks

MediBOT gets a named user account in eCW with its own role and queue. It opens the same screens your staff opens and writes structured data where your staff would.

It does not guess. If a portal result cannot be validated against the chart, it opens an exception for a person instead of writing.

How it stays safe

• MediBOT runs inside your own AWS tenant. PHI never leaves it.
• Credentials are held by the resource servers, not by the agent.
• Every action is logged against the MediBOT user, so auditors see who did what.
• Changes to how it works are proposed, then approved by a person.

That is the story you want ready for an HRSA site visit cybersecurity review, and it belongs in your HIPAA security risk analysis.

What staff stop doing

• Logging into five portals after eCW comes back green.
• Recopying member IDs and effective dates by hand.
• Discovering at check-in that the patient changed MCO on the 1st.
• Parking patients on sliding fee "for now" because the portal was slow.

The desk still owns the patient at the window. MediBOT owns the list you already knew was coming.

Proof

Across 3 Puerto Rico community health centers, from December 2024 to July 2026, MediBOT processed 16,990 automated transactions, redirected 1,088 staff hours, and touched 13,059 patient interactions, for an estimated $20,525 in labor savings. That is the combined total across the automations running in those centers. Not one center. Not one workflow.

Millennial Networks has run healthcare IT for 330 centers in Puerto Rico since 2017. We know these portals because our clients' desks live in them.

Who this is for

• FQHCs, CHCs, and other 330 centers in Puerto Rico and the USVI on eClinicalWorks.
• Billing leads and front desk supervisors whose staff live in MCO portals.
• CFOs who want fewer eligibility denials and cleaner insurance status at the visit.
• Mainland centers with a portal their team still works by hand.

FAQ

Which payer portals does MediBOT check today?

For eligibility, MediBOT works against the Puerto Rico payer portals Assertus, IMC, MCS, PSM, and Triple-S, reads the next day's schedule overnight, and writes the verified result back to each chart in eClinicalWorks.

Can it pull other portal data into eCW, like prior auth status or care gaps?

Yes, as scoped work. Prior authorization status, payer care gap lists, PCP rosters, claim status, and state or Medicaid program portal lookups are built per center through an automation assessment. We map the fields and exceptions first, then build and run it in shadow.

Why do Puerto Rico clinics still check portals when eCW has eligibility?

The native eCW check sends a 270 through your clearinghouse. In Puerto Rico, the MCO portals hold details the 271 often misses, like PCP assignment to your centro, product changes, and MCO switches. That is why desks still open portals after eCW shows green.

We are on the mainland. Is this for us?

Most mainland clinics already automated eligibility through a clearinghouse, so start with eClinicalWorks optimization. If your team still retypes data from a payer or state portal, that specific workflow is a fit for an automation assessment.

Does MediBOT store our portal passwords?

Credentials are held by the resource servers inside your AWS tenant, not by the agent, and every action is logged against the named MediBOT user in eCW.

How do we start?

Book a discovery call. Tell us which portals your staff logs into every day and roughly how many patients they check. We will tell you what runs tonight and what needs an automation assessment.

Book a discovery call

List every portal your team opens in a normal day. Next to each one, write what they copy into eCW. That list is the project.

Book a discovery call or ask for an automation assessment. We start with eligibility, which runs in production today, then scope the next portal. See how it works 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