PointClickCare Integration: Developer Checklist to Cut Enablement Time

By /

Two official paths lead to a working PointClickCare integration: Marketplace partner apps and the USCDI Connector built on FHIR and SMART on FHIR. Choose Marketplace if you’re embedding a validated partner app; choose the USCDI Connector for custom FHIR access or bulk data exports. Either way, your next move is the same: register on the PointClickCare Developer Program portal and start planning facility enablement now, since that step alone can take weeks.

TL;DR:

  • Accessing the PointClickCare FHIR API requires matching tenant IDs and properly formatted scopes to avoid common integration failures.
  • Facility authorization can take at least two weeks, heavily influenced by coordination and approval processes, especially for multi-tenant rollouts.
  • Running sandbox tests thoroughly and requesting only necessary resources reduce errors and help ensure HIPAA compliance.
  • Registering on the developer program and setting up two-factor authentication are essential first steps before using sandbox credentials.
  • Combining Marketplace integrations with the USCDI Connector can cover both embedded apps and complex data workflows, depending on project needs.

Table of Contents

Marketplace vs USCDI Connector: Which PointClickCare Integration Options Fit Your Build?

Your choice depends on what you’re building and how much control you need over the data layer. Marketplace integrations are pre-validated partner solutions built for embedded workflows. They onboard faster because PointClickCare has already reviewed the connection pattern, and Marketplace listings cover labs, pharmacies, device vendors, and health information exchanges.

The USCDI Connector, by contrast, gives you direct FHIR access under ONC’s USCDI v1 data set, structured around Patient-facing, Provider-facing, and Bulk app types.

  • Choose Marketplace for embedded partner apps, device integrations, or lab/pharmacy connections where a certified solution already exists.
  • Choose the USCDI Connector for custom analytics, bulk data exports, or any workflow that needs granular FHIR resource access.
  • Choose both if your product needs an embedded UI plus a backend data pipeline.

How Do You Register for Developer Access and Sandbox Testing?

Getting sandbox credentials is mostly paperwork and a little planning, in that order.

  1. Apply for the Developer Program. Submit your request through the PointClickCare Developer Program portal, which covers both Marketplace membership and USCDI Connector registration.
  2. Pick your app type. Patient-facing apps run in a patient-authorized context; Provider-facing apps operate inside clinical workflows; Bulk apps pull large data sets for analytics or reporting. Each has a distinct launch context and scope profile.
  3. Set up two-factor authentication. PointClickCare requires 2FA for developer accounts before it issues credentials.
  4. Request sandbox access. You’ll get shared sandbox credentials to test SMART on FHIR flows before touching production data.
  5. Format your scopes correctly. SMART on FHIR scopes must match the resource and access level precisely. A malformed scope string is one of the most common reasons a test call fails before you ever reach a real facility.

What Are the Technical Requirements for the PointClickCare FHIR API?

Every FHIR call against PointClickCare needs a tenant ID appended to the base R4 URL. The pattern looks like https://connect2.pointclickcare.com/fhir/R4/{tenantId}/[resource], and forgetting that segment is the single most common integration failure developers report. Pull the exact list of active endpoints from the published Service Base URLs JSON rather than hardcoding them, since PointClickCare updates that list periodically.

Pro Tip: Bookmark the Service Base URLs JSON and check it before every deployment cycle. Tenant endpoints shift more often than most integration teams expect, and a stale bookmark causes silent failures that look like authentication bugs.

Resources aligned with USCDI v1 that you’ll work with most often include:

  • CareTeam
  • MedicationRequest
  • DocumentReference
  • AllergyIntolerance
  • Patient
  • Condition

The PointClickCare FHIR API supports these resources across Patient-facing, Provider-facing, and Bulk app types under USCDI v1. Two failure modes account for most support tickets: an unformatted or missing tenant ID, and SMART on FHIR scopes that don’t match the resource being requested. Test both against the shared sandbox before assuming a production problem exists.

How Long Does Facility Enablement Take for USCDI Connector Apps?

Enablement is facility-driven, not developer-driven. Each skilled nursing facility or health system has to authorize your integration through its own PointClickCare sales representative before your app can touch real data, and that minimum runs about two weeks, scaling up with the number of facilities and the complexity of the patient records involved.

Plan around these prerequisites:

  • Facility-level approval from the PointClickCare account team, not just your developer registration.
  • A Connected Care Center setup for any patient-facing app.
  • Correctly scoped app permissions matched to the data you’re actually requesting.
  • Two-factor authentication enabled on all developer accounts touching the integration.
  • Awareness that the USCDI Connector has historically carried a monthly fee charged per app per facility, so confirm current pricing directly with PointClickCare before quoting a rollout timeline to stakeholders.

Pro Tip: If you’re rolling out across multiple facilities, build a simple tracking sheet with tenant ID, enablement request date, and sales rep contact for each site. Coordination overhead, not code, is what actually delays multi-tenant launches.

What Best Practices Reduce Integration Errors and Compliance Risk?

Most integration failures trace back to skipped sandbox testing or sloppy token handling, not exotic bugs.

  • Run every workflow through the shared sandbox first, including edge cases like missing fields or unusual tenant configurations.
  • Implement SMART on FHIR authentication with least-privilege scopes. Request only the resources your app actually uses.
  • Build retry logic and structured logging that map error codes back to specific tenants, since a 403 from one facility often means something different than a 403 from another.
  • Handle PHI according to HIPAA requirements throughout the pipeline, with consent tracking and audit logs on every read and write.

Pro Tip: Log the tenant ID alongside every API error you capture. When a facility reports a broken sync six weeks after launch, that log line saves you an afternoon of guessing.

How Does Smart Admissions Use PointClickCare Integration for Referral Workflows?

Smart Admissions ties into PointClickCare through the same FHIR and Marketplace patterns covered above, reading eligibility and clinical data and writing referral status updates back into the facility’s record system. That two-way flow is what turns a manual referral review into something a coordinator can clear in minutes instead of hours.

  • Sandbox-first onboarding, mirroring the shared sandbox workflow developers use for any USCDI Connector build.
  • Facility enablement coordinated directly with the PointClickCare account team, following the same facility-driven process every integrator has to go through.
  • A customer-success handoff once the integration is live, so admissions staff aren’t troubleshooting API scopes on their own.

Faster bed fill isn’t about replacing staff judgment. It’s about clearing the paperwork bottleneck so the judgment call happens sooner.

What’s the Checklist for Launching a PointClickCare Integration?

Getting from planning to a live PointClickCare integration follows a predictable sequence.

  1. Document your use case and pick Marketplace, USCDI Connector, or both.
  2. Register on the Developer Portal, enable 2FA, and request sandbox credentials.
  3. Build your app manifest with the exact scopes and resources you need.
  4. Coordinate with each facility’s PointClickCare rep to collect tenant IDs and confirm endpoints.
  5. Validate every workflow in sandbox, then submit for facility enablement and track rollout status.
Stage Owner Typical Output
Path selection Dev lead Documented use case
Registration Developer Sandbox credentials
Manifest build Developer Scoped app config
Facility coordination Admin/IT Tenant IDs, endpoints
Enablement Facility rep Live production access

What Surprises Most Teams Building Their First PointClickCare Integration?

Nearly every team underestimates the facility-driven part of enablement. The code is rarely the bottleneck; the two-plus week authorization cycle and per-tenant scope quirks are. Teams that validate everything in the shared sandbox and open facility conversations early, rather than after the app is “done,” consistently launch weeks sooner than teams that treat enablement as a formality tacked onto the end.

— Harry

Speed Up Referral Intake With Smart Admissions

Manual referral review eats hours that a well-built PointClickCare integration can hand back to your admissions team. Smart Admissions pairs AI-powered referral management with direct EMR integration, so eligibility checks, clinical assessments, and documentation move automatically instead of sitting in someone’s inbox.

Smartadmissions

If faster bed fill and less manual review sound like the outcome you’re chasing, see how facilities are cutting occupancy delays with automated admissions. Start a trial and see how quickly your intake workflow tightens up once PointClickCare integration is handling the paperwork.

Sources

Scroll to Top