For long-term and post-acute care software teams
Connect your pharmacy, therapy, care-transition or analytics product to PointClickCare. We help you choose between the USCDI Connector and Marketplace partner routes, build the API connection and test census, resident and clinical data facility by facility.
Discuss my PointClickCare integrationFor long-term and post-acute care software companies. Updated October 17, 2026.
USCDI Connector or Marketplace partner
Partnership application and developer portal account
FHIR or proprietary APIs with test data
Customer approval and per-facility activation
Illustrative workflow · scope tailored to your environment
The short answer
PointClickCare's developer program offers two routes. The USCDI Connector gives access to its Cures Act FHIR APIs under a USCDI Connector API access agreement. The Marketplace partner route adds developer tools, sandboxes, sales and marketing support and proprietary APIs, for vendors that want to build and support a certified interface with PointClickCare. Both start with a partnership application, and each facility must be enabled for your app.
Read about integration for skilled nursing facilitiesStart with the real problem
Residents are admitted, moved between rooms, sent to hospital and discharged every day. A product that reads a stale census sends medication, therapy or billing work to the wrong place. Your integration needs reliable change detection, per-facility enablement and staff visibility when a record cannot be matched.
Your starting point
Your product serves residents across many facilities and needs census, demographics, orders or results kept current.
A hospital, health plan or care-management team needs to know when residents are admitted, transferred or discharged.
Your product reports on clinical, financial or quality data across a group of facilities.
The Engineering Engagement
Workstreams are selected around your priorities. Each comes with an output your team can inspect, test and own.
Compare the USCDI Connector and Marketplace partner routes for your product, prepare the partnership application and set up the developer portal account and app registration.
Map the resident, census, clinical and financial data your product needs to the APIs available on your route. Record what each route exposes and what it does not.
Design change detection for admissions, transfers and discharges, match residents across facilities and handle records that arrive late or out of order.
Test ordinary and failure cases in the sandbox, then enable facilities one at a time with the customer. Label sandbox results separately from production evidence.
Expertise is in the decisions
The USCDI Connector suits standards-based FHIR access to Cures Act data. The Marketplace route suits products that need proprietary APIs and a supported, listed integration. The choice changes what you can build and how customers find you.
PointClickCare customers enable integrations for their facilities. Confirm with each customer what their PointClickCare agreement covers before you schedule a rollout.
Name each operation and the system that owns its result. Confirm write availability on your route before designing around it, and treat each facility's configuration as something to test.
Development cost depends on operations, mappings, customer configurations and failure handling. Vendor charges and onboarding lead time are assessed separately from engineering effort.
This service page describes work we can scope. It does not establish a vendor partnership, a marketplace listing, a pre-approved connector or a completed deployment for your customer.
Production permissions, commercial terms and clinical sign-off remain with the appropriate customer and vendor owners. We identify these dependencies during discovery.
From discussion to delivery
Agree the users, data, actions and access dependencies. Return a supported-operation map and an estimate with assumptions.
Build the selected connection and test ordinary requests and failures with authorized test data. Label sandbox results separately from production evidence.
Validate the agreed workflow in the customer environment, assign support ownership and complete the approved cutover.
We agree the scope, dependencies, acceptance criteria and commercial model before implementation. Your existing team can stay involved throughout.
Find the right starting point ↗Yes. PointClickCare runs a developer program with Cures Act FHIR APIs through the USCDI Connector and, for Marketplace partners, proprietary APIs, sandboxes and developer tools. Access starts with a partnership application.
PointClickCare describes it as its solution for customers and third-party vendors building ONC-compliant FHIR API integrations. Use is governed by a USCDI Connector API access agreement.
The USCDI Connector covers standards-based Cures Act APIs. The Marketplace partner route adds proprietary APIs, sandboxes, a partnership manager and sales and marketing support, for vendors that design and support a certified interface with PointClickCare.
Yes. A PointClickCare customer enables your integration for its facilities. We plan rollout facility by facility and confirm what each customer's agreement covers.
No. A Marketplace listing is a decision between your company and PointClickCare. We can prepare the application and build the integration it requires.
We estimate after confirming the route, APIs, data mappings and facility rollout. The proposal separates engineering work, any PointClickCare charges and dependencies that affect delivery.
Yes. We can scope a care-transition workflow between PointClickCare and hospital systems such as Epic or Oracle Health. Access and available data remain specific to each system.
A useful first conversation
Tell us what exists today, who uses it and where the workflow breaks. We’ll discuss the scope, access dependencies and the next practical step.
A product overview and a de-identified workflow are enough to start. No patient records or credentials are needed.
These are independent reference sources, not endorsements. Applicability, platform access and current requirements are confirmed for your project.
