About Easydocks

What Easydocks is for

Easydocks is for operators running several PDD-funded group homes in Alberta who are still working on paper. Two houses or ten, support staff rotating across them, and a funder who can ask for any file on any day. It was not built for a single-home operator with no cross-house visibility problem, for acute or clinical settings, or for an organization already running something it is happy with. Replacing what works is a poor reason to buy software, and I will say so on the call.

What it does not do

Easydocks is a documentation product, and there are whole categories of work it deliberately leaves alone. Better to know which of them before the call than during it.

• Easydocks does not do funder billing or claims. No invoice, no claim submission, and no rate table anywhere in it.
• Easydocks does not run payroll. It holds the record of the shift, and produces no timesheet and no hours for anybody to pay against.
• Easydocks does not do clinical charting or prescribing. It carries a medication reminder as a scheduled task on the shift, and a medication error as an incident category, and it stops at the edge of that.

Scheduling is not on that list. Rostering and the open shifts a worker can pick up are part of the product, and they sit alongside the record instead of in a separate place you have to keep in step with it.

The boundary is deliberate. Documentation that holds up the day somebody asks for it is a hard enough problem to be worth doing properly, and every hour spent widening the product is an hour not spent on the record itself.

The problem it was built around

The failure this targets has nothing to do with people being careless. Care documentation gets written at the end of a long shift, by somebody tired, onto paper that exists in exactly one building. The record ends up as complete as the day allowed, and the gaps only become visible when somebody outside your organization goes looking for them. The job of the software is to make the record easy to produce in the moment it happens, and hard to lose afterwards.

How it is built

Three properties hold everywhere in the system. Cash entries, Critical Incident Reports, and abuse reports cannot be updated or deleted, because the database itself refuses, so a correction becomes a new record and the original survives. Every entry carries the person who wrote it and the moment they wrote it. Access follows the houses a person supports, applied when the data is fetched, before anything reaches their phone.

Who you are contracting with

Easydocks is provided by Blueprint Solutions Corp., an Alberta corporation based in Calgary, Alberta. It is a small operation. You should learn that here, on the website, instead of working it out from the signature line of the service agreement.

What that means for you is answered in the contract rather than in reassurance. You can export everything while the account is active. The format is documented, so the file opens without Easydocks. Handing your data back when you leave is an obligation in the service agreement. The continuity questions still open are listed, still open, on the security page.