How to Automate ECP

A resident's day is documented from the med pass out

ECP, from Extended Care Professional, is an all-in-one platform for assisted living: memory care and independent living communities, group homes, adult family homes and IDD providers.

The building is somebody's home, and everything else follows from that. There is no discharge at five o'clock. A resident who has lived there four years has a care level that has drifted upward, a daughter who visits on Sundays, a medication list that changed twice this year, and a monthly invoice that is supposed to reflect all of it.

So the record has to be three things at once. It is the clinical file a state surveyor will read. It is the operational picture of who needs what on this shift. And it is the basis for the bill, because in assisted living the amount a resident pays depends on how much help they need.

The wait for one form holds up a whole move-in

Occupancy is the number the operator watches, and it moves slowly and then all at once.

An enquiry arrives on a Saturday from a listing site the community pays for. A tour is booked. Then a physician's report is needed, and a TB test, and a negotiated risk agreement, and a Medicaid application that has to be filed on a state site and then checked on that site for weeks. Meanwhile the residents already there keep changing: one comes back from hospital needing more help than before, one has a medication the pharmacy has not sent, one has a lease renewal date nobody wrote down.

Every item on that list is a person in the office with a browser open on a website belonging to a hospital, a pharmacy, a state agency or a referral company, retyping into ECP what they found there.

ECP

Applications that stop going quiet Pending Medicaid and waiver cases watched on the state site, with anything static for three weeks raised to the office.

Weekend enquiries answered on the weekend Leads pulled from every listing site into one pipeline, so a family that asked on Saturday is not waiting for Monday.

Charges that match what was delivered Ancillary vendor invoices compared against what was captured in ECP, so a service provided is a service billed.

ECP ties the med pass straight to the invoice

The platform joins up the parts most communities run as separate systems, and the joins are the good part.

eMAR takes medication orders directly from pharmacy partners and builds each resident's record from them, then checks the eight medication rights at every pass, surfacing overdue and not-charted doses, duplicate medications, PRN over-dispensing, psychotropic flags and controlled substance counts. The EHR carries care plans and assessments. Charge Capture then triggers a charge the moment a service is documented, Level-of-Care Billing recalculates as acuity changes, Ancillary Service Tracking picks up laundry, transportation and medication management fees, and General Ledger Export drops the result into the accounting system.

At the front of the funnel, the CRM captures leads from web, phone and referral sources, schedules tours with calendar sync, and raises automated follow-up tasks after every interaction, with Move-Ins carrying a prospect's data forward and pre-populating the document packet at acceptance.

That is a genuinely closed loop, and it closes around ECP's own data. The Medicaid application on a state website sits outside it. So does the hospital's discharge summary, the review a family left last night, the pharmacy's own portal, and the licence renewal the state is waiting on.

The lead, the licence and the pharmacy each live elsewhere

Each of those sites has an address, a login and a page that changes without telling anyone.

Pending Medicaid and waiver applications watched on the state site, with anything that has not moved in three weeks raised, because the resident has been in the building the whole time. Licence and survey portals checked for a status change or a new citation rather than waited on.

New enquiries collected from every listing site into one pipeline before the weekend ends, so a family that asked on Saturday hears back on Saturday. Reviews read and summarised for whoever answers them. The pharmacy's portal checked for orders never filled against an eMAR record that says they should have been. Ancillary vendor invoices matched against what was captured as a charge, since a transportation fee provided and never billed is money given away.

The boundary in a licensed community is firm. Gathering and comparing can run unattended. No care level is reassessed, no medication record is altered, and anything going to a resident's family or to a regulator is drafted and held for a person in the building to read and send.

The browser work leaves the office, the judgement stays

Three people run the office of a typical community, and one of them is the executive director who is currently writing up a fall. Every extra login comes out of that.

WebRun is an AI agent working an ordinary Chrome browser, signed in with the accounts your office already has. It opens the state portal, the pharmacy site, the listing site or the review page, reads what is there, and brings back a list with the resident or the prospect attached.

It runs on your schedule in your own private environment, sessions are not shared between workflows, and a workflow can be locked to an explicit list of sites. You can watch a run and stop it.

The workflows below are already built, and each one names what it opens.