Home care software integrations
Home care software gets asked to talk to payroll, to the NHS, and to whatever system you are leaving behind. Here is what homecareOS connects to today, what it already does itself so that no connector is needed, and what is coming next.
What connects today
Payroll and accounting, NHS clinical records, and data moving in and out. All four are in the product now.
Payroll and accounting exports
Once a pay run is approved it downloads as a file shaped for the payroll system you already use: Sage, Xero, BrightPay, or a generic CSV for anything else.
These are not one CSV with the column headings swapped. Sage wants one row per pay element with the real hourly rate on it. Xero's template has no rate column at all, so hours are bucketed by type instead. Line endings are written CRLF, because the Windows importers at the other end expect them.
Before you download, the screen names any carer with no payroll reference. That reference is the only thing matching a carer to their record in Sage or BrightPay, and the exporter writes an empty cell rather than inventing a stand in. It is a warning rather than a block, because matching by hand on a first run is a legitimate choice.
And if the lines on screen do not add up to the pay run total, the export refuses to run and says why. A partial pay run is the one file you never want reaching a bureau.
NHS and clinical records, in FHIR
Thirteen kinds of record are mapped to HL7 FHIR R4 against UK Core profiles: service users to Patient, care plans to CarePlan, then observations, medications, allergies, health conditions, vaccinations, procedures, equipment, referrals and goals, with carers mapped to Practitioner and family contacts to RelatedPerson.
homecareOS publishes a FHIR CapabilityStatement, which is the machine readable document a clinical system reads to find out what a server supports before it talks to it.
Mapping care records onto UK Core is the part that takes months, and it is done. The endpoints answer to a signed in homecareOS session today, with NHS Identity authentication wired in ready to be switched on for external clinical systems.
Data in, from whatever you are on now
Carers, service users, visits, care plans, background checks, training records and worker registrations all import from CSV, which is the one format nearly every home care platform can produce.
Relationships survive the move, so a visit still points at the right service user and the right carer instead of arriving as a flat list. Every row is stamped with the import that created it, so a bad import is reversed in one step.
Data out, whenever you want it
The finance, quality and absence reports export to CSV, and so do the audit log, mileage claims and the National Minimum Wage check. Invoices, care plans and printable records come out as PDFs. Documents keep their own register with expiry dates attached.
None of this needs a support ticket, and none of it is held back to make leaving harder. An agency that cannot get its own numbers out is an agency that cannot check them.
The phone system is not an integration, it is a screen
Most agencies buy telephony from one supplier and care software from another, then go looking for something to join the two together. The join is where the cost and the fragility live.
homecareOS has the phone system in it: numbers, IVR menus, departments, voicemail with automatic transcription, call reports and blocked numbers. The integration disappears because the second supplier does.
So are most of the things people ask a connector for
Before you look for something to plug in, it is worth checking whether you would still need it:
- Document storage with expiry tracking
- A recruitment portal where applicants upload their own documents
- A family portal, rather than a family mailing list
- Care records and eMAR
- Invoicing and payroll calculation
- Rostering and route planning
The integration list on this page is short partly because the product is wide.
What gets built next is decided by the agencies using it
The Integrations Hub inside homecareOS lists more than thirty named systems, with a vote button beside each one. Votes are counted across every agency on the platform rather than just yours, and the count sets the order we build in. They are queued rather than connected today, so it is worth telling us early if one of them matters to you.
Accounting and payments
Xero, QuickBooks, Sage, FreeAgent, GoCardless, Wise.
Recruitment
Indeed, Reed, NHS Jobs, Care Friends.
Training and workforce
Blue Stream Academy, Care Certificate Online, Skills for Care and ASC-WDS.
Compliance and clinical
CM2000 electronic call monitoring, GP Connect, NHSmail, DBS Online, DocuSign, Adobe Sign, YOURmeds, PainChek.
Calendar, email and storage
Google Calendar, Microsoft 365 and Outlook, Google Workspace, Google Drive, Dropbox.
Messaging and home monitoring
Microsoft Teams, WhatsApp Business, RingCentral, 3CX, Alcove, Canary Care.
Product names belong to their owners and appear here as requested integrations rather than as partnerships.
A connector is a promise to keep it working
Integrations rarely fail loudly. One stops syncing on a Tuesday afternoon and tells nobody, and three weeks later the invoices are short, or the training matrix says a carer is compliant when her certificate lapsed in July.
That is why each one is built and supported properly rather than added to a list, and why we will always tell you where a connector actually stands before you plan around it.
You are not locked in
Your data came in as CSV and it goes out as CSV, and under UK GDPR you have a right to your records in a structured, machine readable format regardless of what any contract says.
We would rather that right never needed exercising than pretend it does not exist. Agencies that have been held to ransom over their own visit history tend to ask about this early, and they are right to.
The ones that come up on every call
For payroll, yes. An approved pay run downloads as a file already shaped for Sage, Xero or BrightPay, ready to import at the other end, with a generic CSV option for anything else. A direct two way sync is the next step rather than the current one: accounting connectors sit in the Integrations Hub inside the product, where agencies vote for which get built first.
Yes, through FHIR. Thirteen record types are mapped to HL7 FHIR R4 using UK Core profiles, and the service publishes a FHIR CapabilityStatement describing what it supports. Those endpoints answer to a signed in homecareOS session today, with NHS Identity authentication wired in ready to be switched on for external clinical systems.
Not yet as a public API key system. The FHIR endpoints are the closest thing and they are session authenticated. If you have a specific system you need homecareOS to push data to, tell us which one and we will say where it sits.
Ask for it, because the list came from agencies asking in the first place. If enough of them want the same thing it moves up the order, and in the meantime almost anything can be handled with a CSV export.
The phone system is built in, including IVR menus, departments, voicemail with automatic transcription, call reports and blocked numbers, so that one you can drop. E-learning and e-signature connectors are on the roadmap rather than in the product, so you would keep whatever you use for those today.
No. The finance, quality and absence reports, the audit log, mileage claims and the National Minimum Wage check all export to CSV, invoices and care plans come out as PDFs, and under UK GDPR you have a right to your records in a portable format anyway.
Tell us what you need to connect to
If there is one system your agency genuinely cannot work without, that is worth establishing before a demo rather than after one. Tell us which it is and we will say where it sits.