Wellsky

Last reviewed: July 2026

Overview

Integuru's Wellsky integration provides production-ready HTTP API access to Wellsky (formerly Kinnser), the home health and home care clinical management platform at kinnser.net, covering 4 actions: get_inbox, get_patient_info, list_patients, and qa_manager_list. All 4 actions carry full richer documentation. 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. Wellsky does not expose an official developer API. Home health tech teams that need patient records, episode data, or QA task lists programmatically have historically relied on manual exports or browser-based scripts. Wellsky also processes protected health information; HIPAA compliance obligations for any integration layer rest with the implementing organization.

The integration covers the core clinical operations surfaces: patient roster retrieval via list_patients, individual patient detail via get_patient_info, internal messaging via get_inbox, and QA task management via qa_manager_list. Home health software teams use these actions to sync patient lists, retrieve episode-level clinical data, and monitor outstanding QA tasks in automated reporting pipelines. See the ClearCare integration for another home care management platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's Wellsky integration covers the patient data and clinical workflow actions that home health tech teams need to automate.

• Patient roster retrieval: Call list_patients with optional filter (last-name letter or #123 for numeric names), show_inactive (boolean to include inactive records), and patient_filter (text search) to retrieve a filtered patient list.
• Patient detail retrieval: Call get_patient_info with episode_id and patient_id to retrieve detailed clinical and demographic information for a specific patient episode.
• Inbox access: Call get_inbox with the required session_cache_key (UUID:8-char-hash format) and optional page, folder, sort_by, sort_order, and rows_per_page to retrieve internal messages from the Wellsky inbox.
• QA task review: Call qa_manager_list with optional search, start_date, end_date, visit_type, and case_manager_id (-1 for all case managers) to retrieve the QA manager task list for review pipelines or compliance monitoring.

---

Setup Notes

Integuru's Wellsky integration authenticates against https://kinnser.net/login.cfm. Integuru manages the session automatically after credentials are configured during setup.

list_patients and qa_manager_list require no mandatory parameters; all their fields are optional filters. get_patient_info requires both episode_id and patient_id. get_inbox requires session_cache_key in UUID:8-char-hash format; all other inbox parameters are optional.

Full richer documentation for all 4 actions is available via the Integuru dashboard after setup.