Nirmitee.io

WellSky integration · United States

WellSky API Integration for Home Care and Hospice

We build WellSky integrations for home care, hospice and post-acute products. WellSky is a family of products with different routes: WellSky Personal Care has the Connect API with creates, updates and webhooks, and WellSky Hospice and Palliative publishes a read-only FHIR R4 API for EHR partners. We confirm which product and access each customer has, then build on the documented route.

Book a scoping call ↗See WellSky routes by product →
  • Connect API
  • WellSky Personal Care
  • Hospice FHIR R4
  • Webhooks
  • OAuth 2.0
  • Agency ID
  • ClearCare

One vendor name, several WellSky APIs.
  1. 01Find the product

    Personal Care, Hospice and Palliative and Home Health are separate products with separate documentation.

  2. 02Get access

    Personal Care uses client credentials under WellSky's Connect API agreement; hospice FHIR apps register through WellSky's form.

  3. 03Build to the rules

    Agency ID on every call, a trailing slash on every path, one object per call and webhooks instead of polling.

Evidence you can check

The problem

Sound Familiar?

Agencies and the vendors that serve them hit these four problems before anything else.

Referrals retyped into WellSky

A hospital referral arrives in your intake tool, and someone types the client, the contacts and the referral source into WellSky again.

"WellSky has an API" means three different things

Personal Care, Hospice and Home Health are separate products with separate routes, and nobody on the call knows which one your customer runs.

Caregiver apps that do not close the loop

Your caregiver app records the visit, but clock-in and clock-out still have to be reconciled by hand in WellSky.

No signal when something changes

Your product polls WellSky for new clients because nobody set up the notifications the API offers.

Use cases

What It Looks Like When It Works

Four use cases, each shown as the screen your team works in. Clients and agencies are fictional; the API behavior follows WellSky's published documentation.

A Referral Becomes a WellSky Client Without Retyping

Today

Intake staff copy referral details from one screen into WellSky Personal Care.

With the integration

The client, the emergency contact and the referral source are created through the Connect API, the returned IDs are stored, and a patient.created notification confirms the record.

What we build
  • Matching against existing clients before any create
  • Patient, RelatedPerson and ReferralSource calls with the agency ID on each request
  • A Subscription so WellSky notifies your product of new and changed records
Referral to WellSky Personal Care log: client matched, created, contact and referral source linked, webhook confirmed
Illustrative screen with fictional clients: referral to WellSky Personal Care log: client matched, created, contact and referral source linked, webhook confirmed. Tap to open full size.

Caregiver Visits That Reach WellSky

Today

Coordinators compare the caregiver app with WellSky and fix clock times by hand.

With the integration

Clock-in and clock-out from the caregiver app are written to the visit in WellSky, and a missed visit shows up for the coordinator instead of being discovered on payroll day.

What we build
  • ClockIn and ClockOut calls tied to the scheduled visit
  • Missed and late visit rules your coordinators agree
  • One object per call, inside WellSky's rate guidance
Caregiver visit list showing clock-in and clock-out sent to WellSky, a visit in progress and a missed visit
Illustrative screen with fictional clients: caregiver visit list showing clock-in and clock-out sent to WellSky, a visit in progress and a missed visit. Tap to open full size.

Hospice Records in Your Care Coordination App

Today

Your team asks the hospice for faxed care plans and medication lists.

With the integration

A registered app reads the patient, care plan, care team, medications and conditions from WellSky Hospice and Palliative over FHIR R4. Updates stay in WellSky, because the published hospice API is read only.

What we build
  • Application registration through WellSky's form and license terms
  • US Core resource mapping into your product
  • Clear labels in your app for data that is read only
Hospice record read from WellSky Hospice FHIR R4 API: patient, care plan, care team, medications, conditions, no write back
Illustrative screen with fictional clients: hospice record read from WellSky Hospice FHIR R4 API: patient, care plan, care team, medications, conditions, no write back. Tap to open full size.

The Right Route for Each WellSky Product

Today

A project starts on the assumption that every WellSky customer has the same API.

With the integration

Discovery confirms which WellSky product and contract each customer has, and picks the Connect API, the hospice FHIR API, a WellSky conversation or an authorized fallback before any build.

What we build
  • A product and contract check per customer
  • Written confirmation of access before build starts
  • Login-based automation only with WellSky's terms and the customer's written authorization
Discovery table of WellSky products with the documented route, what each allows and the integration plan
Illustrative screen with fictional clients: discovery table of WellSky products with the documented route, what each allows and the integration plan. Tap to open full size.

First call

Questions We Will Ask You on the First Call

The answers decide the route, the timeline and the access you need from WellSky. You do not need them all before we talk.

Which WellSky product does each customer run?

Personal Care, Hospice and Palliative, Home Health and CareTend have different routes and documentation.

Does the customer's WellSky contract include API access?

Connect API access is granted with credentials and an API agreement, so we confirm it before scoping.

Do you need to write, or only read?

Personal Care supports creates and updates for many objects; the hospice FHIR API we found is read only.

Which records start the workflow?

Referrals, clients, caregivers, visits or billing items each map to different endpoints.

Should WellSky notify your product of changes?

Subscriptions send the resource type and ID to your webhook, which beats polling.

How many agencies will you connect this year?

Each agency needs its own credentials and agency ID, so onboarding has to be repeatable.

Who matches duplicate clients?

A create without matching produces duplicates; someone must own the review queue.

What happens if WellSky has no route for a workflow?

We check exports and, only with WellSky's terms and the customer's written authorization, login-based automation.

The short answer

Does WellSky Have an API? Yes, per Product

WellSky publishes different APIs for different products. The WellSky Personal Care Connect API, formerly ClearCare, is a REST API with FHIR-style resources: an agency exchanges a client ID and secret for a bearer token, then creates, updates and searches clients, contacts, care plans, documents, charges and invoices, records visit clock-in and clock-out, and subscribes to change notifications. WellSky asks integrators to stay under 100 requests a second and not to use the API for batch jobs. WellSky Hospice and Palliative publishes a FHIR R4 API within US Core for EHR partners, with read operations only. We found no public API documentation for WellSky Home Health, so we confirm that route with WellSky.

Who it is for
Home care, hospice, referral, caregiver, billing and analytics products that serve agencies on WellSky.
What we build
Connect API clients, referral and client sync, visit verification, webhooks, hospice FHIR reads and the onboarding steps for each agency.
The outcome we design for
Supported agency workflows connected through the access WellSky grants, with a repeatable onboarding checklist. These are intended outcomes, not a promise about WellSky's decisions.

WellSky routes by product

WellSky APIs by Product, and What Each Allows

Read from WellSky's published documentation on October 26, 2026. Access, terms and fees are set by WellSky and the customer's contract.

WellSky productDocumented routeWhat it allowsWhat to plan for
WellSky Personal Care (ClearCare)Connect API, REST with FHIR-style resourcesCreate, update and search clients, practitioners, related people, allergies, medications, documents, charges, care plans, conditions, goals, invoices and referral sources; search appointments and locations; clock in and clock outClient ID and secret per agency, agency ID on calls, trailing slash on every path, under 100 requests a second, no batch use
Personal Care change notificationsSubscription resource with webhooksNotifications with the resource type and ID, for example patient.created or referralsources.changedA public HTTPS endpoint and a fetch-back of the changed record
WellSky Hospice and Palliative (Consolo)FHIR R4 API for EHR partners within US CoreRead: Patient, AllergyIntolerance, CarePlan, CareTeam, Condition, Device, Encounter, Location, MedicationRequest, Observation, Organization, Practitioner, PractitionerRole, Procedure, and Patient $everythingApplication registration through WellSky's form, WellSky's API license agreement, no write operations
WellSky Home HealthNo public API documentation foundConfirm with WellSkyAsk WellSky about interfaces before scoping
Other WellSky products (for example CareTend, community services)Product-specific APIs listed by third partiesVariesConfirm documentation, access and fees with WellSky

WellSky's Connect API documentation records changes through September 2026. Third-party sites rate WellSky's developer portal poorly; we build from WellSky's own documentation and confirm access per customer.

What we build

What Our WellSky Integration Builds

Pick the workstreams your product needs. Each one ships with a specification, test runs and an owner.

01

Referral and Client Sync

Referrals from your intake product become WellSky Personal Care clients, with contacts and referral sources, after matching against existing clients so a create never duplicates a record.

Patient · RelatedPerson · ReferralSource

02

Visit Verification

Caregiver clock-in and clock-out written to the scheduled visit, with missed and late visits sent to coordinators under rules they agree.

ClockIn · ClockOut · Encounter search

03

Care Plans and Clinical Detail

Care plan activities, conditions, goals, allergies and medications kept in step with your product where the Connect API supports it.

CarePlan · Condition · Goal · MedicationStatement

04

Billing Items

Charge items and invoices created and read for billing and reporting, with allocation rules confirmed against the agency's own setup.

ChargeItem · Invoice

05

Hospice Records Over FHIR

A registered app reading patients, care plans, care teams, medications and conditions from WellSky Hospice and Palliative.

FHIR R4 · US Core · Patient $everything

FHIR integration services →
06

Webhooks, Monitoring and Support

Subscriptions for the events your product needs, fetch-back on every notification, request pacing under WellSky's guidance, alerts and a runbook.

Subscription · rate guidance · alerts

Integration monitoring and support →

Buyer decisions

WellSky Integration Options Compared

Use the documented API for each product first. A product can need more than one route.

OptionBest fitStrengthsWhat to plan for
Personal Care Connect APIHome care intake, scheduling, caregiver and billing productsCreates, updates and webhooksCredentials per agency and WellSky's API agreement
Hospice FHIR R4 APICare coordination and patient apps reading hospice recordsStandard US Core resourcesRead only; application registration
Interfaces confirmed with WellSkyHome Health and other products without public docsA supported route once confirmedTime to get answers from WellSky
ExportsMigrations and analytics backfillsNo build on WellSky's sideManual steps, no ongoing sync
Login-based automationWorkflows no WellSky route coversWorks where the API stopsWellSky's terms, the customer's written authorization and strict controls

We say so when WellSky's documented routes cannot do what you need.

Integration boundaries

WellSky Integration Boundaries: Who Owns What

We write the split down before the build starts.

The agency

Requests or provides API credentials, approves the data you access and owns its WellSky configuration.

WellSky

Owns its APIs, terms, access decisions and fees. We build to the published interfaces.

Your product team

Owns what your product does with WellSky data and how it appears to users.

The integration layer (ours)

Clients, matching, webhooks, pacing, redacted operational logs and alerts. Defects in this layer are ours to fix.

Security and PHI

A BAA is available for agreed work involving PHI. We encrypt in transit and at rest, keep credentials in a vault and keep raw payloads out of operational logs.

Deliverables

WellSky Integration Deliverables

Everything lands in your repository and your runbook.

01

Route and data map

Which WellSky product and route serves each workflow, with field maps per resource.

02

Integration code in your repository

Connect API and FHIR clients, matching, webhooks and pacing, with agency configuration kept out of the code.

03

Agency onboarding checklist

Credentials, agency ID, webhook endpoint and the checks to run for each new agency.

04

Test evidence

Recorded runs covering creates, duplicates, webhook delivery, permission errors and rate limits.

05

Monitoring and runbook

Redacted operational logs, failure alerts and a support runbook.

Delivery phases

WellSky Integration Timeline

Initial planning estimate: 6 to 10 weeks to a first live agency, subject to WellSky access, credentials and workflow validation. Discovery confirms the product and access before you commit to a release date.

  1. 01

    Discovery and access

    Weeks 1 to 2

    Product and contract confirmed per customer, credentials or registration requested

  2. 02

    Build

    Weeks 2 to 6

    Clients, sync, webhooks and matching built and tested

  3. 03

    Agency validation

    Weeks 5 to 8

    First agency connected, data checked with the agency team

  4. 04

    Go-live and hypercare

    Weeks 7 to 10

    First agency live, monitoring on, onboarding checklist handed over

Cost drivers

What Drives WellSky Integration Cost

Use the scoping call to pin down the workflow, the access you need and what goes into a scoped proposal. These are the factors that move cost.

WellSky products

Each product has its own route, so covering Personal Care and Hospice is two connectors.

Workflows

Referrals, visits, care plans and billing each add mapping and tests.

Write access

Writes need matching, reconciliation and review steps that reads do not.

Agencies per year

A repeatable onboarding checklist matters most when you add many agencies.

Fallback routes

Exports or login-based automation add their own controls and tests.

Support level

Monitoring and on-call support are priced per connection.

Book a call ↗

Proof

Post-Acute and EHR API Work You Can Check

Client names are withheld. These published guides show how we approach EHR API work; they do not prove WellSky approval or a live agency integration.

Published engineering guide

EHR Automation Without API Access

How we decide between APIs, RPA and computer-use agents when a product's API stops short, and the controls each needs.

Read the guide →

Published engineering guide

Multi-EHR API Comparison

How major EHRs expose their APIs, and what that means for a product that must serve several of them.

Read the guide →

Service we deliver

PointClickCare Integration

Our post-acute integration work for skilled nursing and senior living, the setting many WellSky and MatrixCare vendors also serve.

See PointClickCare integration →

Security

ISO 27001:2022 Certified, BAAs Signed

We are ISO 27001:2022 certified and sign Business Associate Agreements for work that touches patient data.

FAQ

WellSky Integration: Questions Buyers Ask

Does WellSky have an API?

Yes, per product. WellSky Personal Care has the Connect API with creates, updates, searches and webhooks. WellSky Hospice and Palliative publishes a read-only FHIR R4 API for EHR partners. We found no public API documentation for WellSky Home Health, so we confirm that route with WellSky.

What is the WellSky Personal Care Connect API?

It is WellSky's REST API for the product formerly called ClearCare. Resources follow FHIR naming, such as Patient, Practitioner, CarePlan and DocumentReference, and the base URL is connect.clearcareonline.com. WellSky publishes it with a changelog and an API agreement.

How do you authenticate to the WellSky Connect API?

The agency's client ID and secret are exchanged for a bearer token through OAuth 2.0, and the token goes in the authorization header. WellSky notes that Connect API permissions are not role based, so access is controlled per credential.

Does WellSky support webhooks?

The Personal Care Connect API does. A Subscription sends your webhook the resource type and ID when, for example, a patient or practitioner is created or a referral source changes, and your product fetches the record back.

What are the WellSky API rate limits?

WellSky does not throttle explicitly but asks integrators to stay under 100 requests a second, and says the API is built for real-time calls on one object at a time, not batch operations.

Is the WellSky hospice API read only?

The WellSky Hospice and Palliative FHIR R4 API we reviewed lists read operations only, including Patient $everything. Updates stay in WellSky Hospice unless WellSky offers another route for your use case.

Can we write visit times to WellSky?

In WellSky Personal Care, yes. The Connect API documents clock-in and clock-out operations tied to the visit, which is how caregiver apps close the loop on visit verification.

What if WellSky has no API for our workflow?

We first confirm with WellSky and check exports. Login-based automation is a last resort, used only where WellSky's terms and the customer's written authorization allow it, with an audit trail.

Do we need partner status with WellSky to integrate?

Not always. Personal Care access runs on credentials under WellSky's Connect API agreement, and hospice FHIR apps register through WellSky's form. We confirm the access path for your product and customers during discovery.

How long does a WellSky integration take?

Our initial planning estimate is 6 to 10 weeks to a first live agency, subject to WellSky access and workflow validation. Later agencies follow an onboarding checklist.

How much does a WellSky integration cost?

Cost depends on the WellSky products, the workflows, write access, how many agencies you add, any fallback routes and the support level. A BAA is available under our ISO 27001:2022 certified management system. After a scoping call we send a scoped proposal with the access dependencies listed.

Next step

Plan Your WellSky Integration

Tell us which WellSky products your customers run and the workflows your product needs. An engineer replies with the likely route per product and the open access questions.

Book a call ↗Send your WellSky details →

Start with your workflow

Tell Us About Your WellSky Integration

Share the WellSky products, the workflows and your target date. Use de-identified examples only. Read by an engineer, answered within one business day.

Please exclude patient data and credentials. We use these details to respond to your inquiry. Privacy policy

Thank you. Your inquiry has been received. Our team will review your requirements.

Standards and Primary Sources