ClearCare

Last reviewed: July 2026

Overview

Integuru's ClearCare integration provides production-ready HTTP API access to ClearCare, the home care agency management platform at <SUBDOMAIN>.clearcareonline.com, covering 15 actions across client records, ADLs, iADLs, care plans, medications, and prospect management. Five actions carry richer documentation: update_iadls, update_care_plan_all_sections_v1, read_adls, update_client_adls, and update_adls. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public developer API. ClearCare does not expose an official developer API. Home care tech teams that need to read or write client records, care plans, or ADL data programmatically have historically relied on manual data entry or brittle browser scripts. ClearCare also handles protected health information; any integration that touches PHI carries HIPAA compliance obligations for the implementing organization.

The integration spans the full client lifecycle: roster management via list_clients and list_patients, prospect tracking via list_prospects and find_prospect_by_name, client creation via create_client, care plan reads and writes via read_care_plan, update_care_plan, and update_care_plan_all_sections_v1, ADL and iADL reads and writes via read_adls, read_iadls, update_adls, update_iadls, and update_client_adls, and medication management via add_medication. See the Wellsky integration for another home care clinical platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's ClearCare integration covers the client management and care plan workflows that home care tech teams need to automate.

• Client and patient listing: Call list_clients with no parameters to retrieve all active clients. Call list_patients with optional limit, offset, search, tags_filter, and status_filter to retrieve a filtered, paginated patient list.
• Client lookup by name: Call find_client_by_name with a name string (partial matches supported) to locate a client record. Use find_prospect_by_name the same way to search the prospect pipeline.
• Client creation: Call create_client with first_name and last_name required; all address, contact, and portal fields are optional.
• Care plan reads: Call read_care_plan with a client_id to retrieve the full care plan for that client.
• Care plan updates: Call update_care_plan with client_id and any combination of optional section objects (meals, driving, exercise, equipment, transfers, ambulation, care_needs, elimination, medications, demographics, daily_routine, match_criteria, sleep_patterns, mental_behavior, bathing_grooming, medical_conditions). Use update_care_plan_all_sections_v1 for the extended field set with richer docs.
• ADL reads: Call read_adls with client_id and optional type (1 for ADLs, 2 for IADLs) to retrieve activity data. Call read_iadls with client_id to read iADL records directly.
• ADL and iADL updates: Call update_adls with client_id and an activities array to update ADL records. Call update_iadls the same way for iADL records. Call update_client_adls to perform targeted operations (update_notes, update_level_of_need, or update_task) on a specific life_activity_id.
• Medication management: Call add_medication with client_id and a medications array to add medication records to a client.

---

Setup Notes

Integuru's ClearCare integration authenticates against https://<SUBDOMAIN>.clearcareonline.com/login/. Configure your agency subdomain once during Integuru setup; Integuru manages the session automatically.

Actions requiring only a client_id include read_iadls, read_care_plan, update_iadls, update_adls, and add_medication (the latter two also require their respective array payloads). list_clients, list_prospects require no parameters. find_client_by_name and find_prospect_by_name require a name string. create_client requires first_name and last_name.

For update_client_adls, three parameters are always required: action, client_id, and life_activity_id. The remaining parameters apply conditionally depending on which action value is used. Richer docs are available for update_iadls, update_care_plan_all_sections_v1, read_adls, update_client_adls, and update_adls via the Integuru dashboard after setup.