How to Automate Ensocare

Ensocare starts working before the patient is ready to go

Ensocare is software for the handover at the end of a hospital stay, when a patient is well enough to leave but not well enough to go home unaided. Its users are hospital case managers, social workers and discharge planners, and their job is to find the skilled nursing facility, rehabilitation unit or home health agency that will take this particular person, with this set of needs, on this day.

It is a harder task than it sounds, because none of those organisations belong to the hospital. Each one decides for itself whether it can take a patient, based on staffing, on clinical needs it is set up for, and on whether the paperwork adds up. A hospital cannot direct any of them.

So the discharge planner works by asking, repeatedly and quickly, and the whole day has a meter running on it. Every extra night is a bed that a person in the emergency department is currently waiting for, and a night the hospital is unlikely to be paid for.

A discharge is agreed in the morning and slips by lunchtime

The referral is only the first move, and it is the one part of the day that behaves predictably.

After the acceptance comes the rest. Somebody looks up whether the facility the daughter asked about has had a bad inspection recently, because the family will ask. Somebody rings the home health agency to find out whether a nurse is genuinely available on Saturday or only in principle. Somebody checks with a pharmacy about a discharge medication that has to be in the house before the first dose is due. Somebody finds out whether the state has decided on a pending long-term care application, because no facility holds a bed on a maybe.

Each of those is a phone call, a hold queue and a callback an hour later. Meanwhile the patient is dressed, the family is in the room, and the ward wants the bed. This is where discharge days actually go.

Ensocare

Ratings that are current today Public inspection findings and star ratings gathered for every facility on the shortlist, so a family is not choosing from a folder printed last spring.

Home support confirmed before the ride Agency and pharmacy sites checked for whether the first visit is staffed and the first dose will be there, before a discharge time is set.

Referral lists built on who says yes Admission criteria read from facilities' own pages, so a referral goes where it has a real chance instead of to everyone at once.

Transition solved the part of discharge that scaled

It is worth crediting exactly what Ensocare took off these teams, because it was the worst part of the job and it is now largely gone.

Transition automates the referral itself. A case manager sends an electronic referral to a verified list of post-acute providers matched to the patient's clinical and non-clinical requirements, rather than faxing the same packet to fifteen places. Providers get a push notification through a provider portal or mobile app, see the referring hospital, the clinical status and the discharge notes, and accept or decline with the dates they can take. Choice lets patients and families look through post-acute options on a tablet at the bedside. Interoperability with the EHR means the receiving organisation gets what it needs to start care rather than a summary typed twice.

All of that runs on Ensocare's own network of registered providers and the messages passing across it.

The pharmacy, the state Medicaid site, the inspection record, the agency's own rota and the plan's provider directory are not on that network. They are ordinary websites belonging to organisations that have never heard of your discharge.

The shortlist a family sees can be current on the day

Picture the same shortlist with today's public record attached to every name on it.

Recent inspection findings and published ratings collected for each facility a family is considering, so the conversation at the bedside runs on what is true this week rather than on a folder printed in the spring. The health plan's provider directory checked, so nobody is steered toward a facility the plan will not cover.

The home health agency's site read for whether the first visit is genuinely staffed for the weekend. The specialty pharmacy checked for stock and a delivery slot, so the first dose is in the house before the patient is. A pending state long-term care determination chased on the state's own portal rather than waited on. Admission criteria read off the facilities' own pages, so the next referral list is built from who actually takes this kind of patient.

One boundary holds throughout. Gathering runs unattended and on a schedule. Changing a record, sending a referral, reaching a patient or a family: none of that happens without a qualified person. Placement is a judgement about a human being, and it stays with the person who has met them.

The bedside conversation deserves better than a printout

A case manager with eight discharges to arrange before five is the person who currently opens a dozen websites to make that conversation accurate.

WebRun is an AI agent that works a real Chrome browser, signed in the way your staff are. It opens the inspection record, the agency's site, the pharmacy portal or the state application page, reads what is there, and brings it back as a short list against the patients on today's board.

It runs on your schedule in your own private environment, sessions are not shared between tools, 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 names exactly what it opens.