PointClickCare API
PointClickCare is the dominant cloud EHR platform for skilled nursing, senior living, and post-acute care in North America, serving 30,000+ provider organizations with clinical charting, census and ADT management, eMAR, MDS assessments, billing, and care coordination. This page is an independent design exercise that asks what a well-designed PointClickCare API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed PointClickCare API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing PointClickCare product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is PointClickCare?
PointClickCare is the dominant cloud EHR platform for skilled nursing, senior living, and post-acute care in North America, serving 30,000+ provider organizations with clinical charting, census and ADT management, eMAR, MDS assessments, billing, and care coordination. Its product families span Skilled Nursing, Senior Living, Hospital & Health Systems, and Health Plans, with a marketplace of 400+ integrations connecting third-party software and service providers across the care continuum.
An API for a platform like this would naturally organize around its core data entities:
- Resident census and ADT events (admissions, discharges, transfers)
- MDS 3.0 assessments that drive PDPM reimbursement
- eMAR/eTAR medication administration records and physician orders
- Clinical charting and care plans
- Billing, claims, AR, and payer eligibility
- Staffing and payroll inputs
The PointClickCare Integration Challenge
- A developer portal exists, but most documentation sits behind a login, and production access is multi-gated rather than self-serve
- Becoming a partner means a marketplace partnership application, an app authenticity review (around 10 business days), and a Definitive Agreement that may include fees
- Every customer connection requires a per-customer Letter of Authorization before your app can touch that facility's data
- USCDI Connector apps carry a $65 per app, per facility, per month charge billed to the customer
- The free FHIR sandbox is shared, and production parity only comes after partnership approval
- Terms prohibit scraping and bots, webhooks are not publicly documented, and there are no official SDKs, so event-driven workflows are hard to build
What a PointClickCare API Could Look Like
If PointClickCare exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like PointClickCare: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould establish an authenticated session with managed MFA handling
Resident Operations
/residentsWould retrieve resident demographics and current census records
Resident Operations
/adt_eventsWould pull admission, discharge, and transfer events for a facility
Clinical
/assessmentsWould retrieve MDS 3.0 assessments and completion status
Clinical
/emarWould pull medication administration records and active physician orders
Billing
/claimsWould retrieve claims, AR balances, and payer eligibility details
Use Cases
Referral & Census Sync
- Pull ADT events and census changes as they happen - Sync admissions and discharges to downstream systems - Keep hospital and payer partners updated without manual reports
PDPM Revenue Integrity
- Extract MDS 3.0 assessments as they are completed - Audit case-mix groups against clinical documentation - Flag reimbursement-impacting gaps before submission
Pharmacy & eMAR Reconciliation
- Pull eMAR administration records and active orders - Reconcile against pharmacy dispensing data - Surface missed or late administrations automatically
AR & Claims Automation
- Retrieve claims, balances, and payer eligibility - Push billing updates from your RCM stack - Automate follow-up on aging receivables
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require managed credential-based login with automated MFA and session handling
Connectivity
Would build on connects to PointClickCare's cloud application the same way an authorized user does, no partner program required
Response format
Normalized JSON over REST
Rate limits
Managed request pacing tuned to PointClickCare's tolerances
Session management
Would need automatic session refresh and re-authentication
Data freshness
Near real-time reads; configurable polling for change detection
Security
Encryption in transit and at rest; credentials stored in a secrets vault; access limited to data your organization is authorized to view
Webhooks
Latency
Design target: typical reads complete in 1-3 seconds depending on workflow
Throughput
Design target: scales horizontally across facilities and provider organizations
Reliability
Monitored 24/7 with automatic retries and failure alerts
Versioning
Clear versioning and change management would matter as PointClickCare evolves
Frequently asked questions
Typical integrations cover residents and census/ADT events, MDS 3.0 assessments, eMAR and physician orders, care plans, and billing, claims, and eligibility data, normalized into consistent JSON.
Most integrations go from assessment call to a validated, production-ready API in days, not the months a partner application and per-customer authorization process can take.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual PointClickCare product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.