.png)
PointClickCare Integration Guide
Connect approved PointClickCare REST APIs with enterprise systems through secure OAuth-enabled workflows, scheduled synchronization, data mapping, and controlled APIs.
PointClickCare integration options at a glance
PointClickCare’s primary integration mechanism is its REST-oriented API program for approved partner and customer applications. Access, resources, scopes, environments, and tenant data depend on the enabled product and PointClickCare provisioning. Integrations use an OAuth 2.0-style bearer-token model, with credentials and token configuration stored securely in Martini. Where event or callback capabilities are not available, Martini can run scheduled incremental reads using documented timestamps, status filters, or other supported selection criteria. Martini workflows can paginate through PointClickCare resources, transform JSON payloads, apply facility and data-minimization rules, and write approved information to downstream applications or databases.
| Integration point | Supported by PointClickCare? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Retrieve facilities, residents, census, and other enabled clinical or operational resources, and submit or update supported resources. Available endpoints depend on the customer’s PointClickCare products, tenant, permissions, and API package. | Martini can consume PointClickCare REST endpoints from workflows, handle pagination and incremental selection, transform JSON payloads, and expose a controlled API façade for internal consumers. |
| Authentication | Yes | Authenticate approved applications using PointClickCare’s OAuth 2.0-style access-token model. Exact grants, scopes, client registration, and token endpoints depend on the provisioned API program. | Martini stores client credentials and token configuration as environment-specific secrets, supplies bearer tokens, and supports workflows that reacquire or refresh credentials before expiration. |
| Scheduled synchronization | Yes | Use scheduled incremental API reads when a suitable PointClickCare event or callback capability is unavailable or limited. Selection may use documented timestamps, status changes, or other supported filters. | Martini scheduler-triggered workflows can maintain watermarks, use overlap windows, paginate through results, perform idempotent upserts, and record reconciliation totals. |
| Webhooks / outbound callbacks | Not confirmed | A general-purpose PointClickCare webhook mechanism for resident, census, clinical, or administrative events was not confirmed. Any product-specific event or callback capability requires separate verification. | If PointClickCare provides a customer-specific callback contract, Martini can receive it through an appropriate API or webhook workflow after authentication, event coverage, and retry behavior are confirmed. |
| Bulk / async / batch APIs | Not confirmed | No universal public PointClickCare bulk or asynchronous API was verified. Product-specific exports or batch capabilities may exist but require confirmation. | Martini can orchestrate a documented batch or export process if PointClickCare supplies one, but the implementation should not assume bulk support across products. |
| File / attachment APIs | Not confirmed | No general public PointClickCare file or attachment API was verified. File exchange may be available for particular products or customer implementations. | Martini can process an approved file-based exchange when the transport, format, encryption, and operational contract are documented by PointClickCare. |
| GraphQL APIs | Not confirmed | No official public PointClickCare GraphQL documentation was verified; the integration should be designed around documented REST APIs. | Martini can consume GraphQL when a PointClickCare product-specific API is separately confirmed, but no GraphQL-based PointClickCare design should be assumed. |
| SOAP APIs | Not confirmed | No official public PointClickCare SOAP documentation was verified for current integrations. | Martini supports SOAP consumption generally, but a PointClickCare SOAP implementation should only be designed if vendor documentation confirms the relevant service. |
| Database / analytics access | No | Direct database access to PointClickCare hosted production data should not be assumed. Approved APIs or vendor-authorized exports are the expected integration methods. | Martini can write API-derived data to approved databases or analytics platforms, but it should not connect directly to PointClickCare’s hosted production database. |
How PointClickCare exposes data and business events
PointClickCare REST APIs
PointClickCare provides REST-oriented APIs for approved partner and customer integrations. The available resources, operations, scopes, and data fields vary by PointClickCare product, API version, tenant, facility access, and customer agreement.
Martini implementation pattern
Martini uses an authenticated workflow to call the enabled PointClickCare REST endpoints, retrieve paginated resources, apply facility and incremental filters, transform the returned JSON, and deliver approved data to downstream applications, databases, or a controlled Martini API.
Implementation sequence
Scheduled incremental synchronization
When a suitable PointClickCare event feed or callback is unavailable, scheduled API reads provide a practical synchronization pattern. The exact timestamp, status, cursor, or filter behavior must be confirmed for each endpoint.
Martini implementation pattern
Martini starts a scheduled workflow, reads the last successful watermark, retrieves an overlapping range of PointClickCare changes, and performs idempotent writes to the target. The workflow stores checkpoints and separates transient failures from permanently rejected records.
Implementation sequence
Customer-specific events or callbacks
A general-purpose PointClickCare webhook mechanism was not confirmed publicly. Some products or customer agreements may provide event notifications or callbacks, but event types, authentication, delivery, retry behavior, and subscriptions require separate confirmation.
Martini implementation pattern
If PointClickCare supplies a documented callback contract, Martini can expose an appropriate receiving API, authenticate the request, validate the event, retrieve the current resource when necessary, and route the result through the same mapping and reconciliation workflow used for scheduled synchronization.
Implementation sequence
Common PointClickCare integration patterns
Pattern 1: Synchronize residents and census data
When to use this pattern
Use this pattern when operational, reporting, or approved healthcare applications need current resident, facility, admission, discharge, transfer, or census information and PointClickCare event delivery is unavailable or insufficient.
Integration direction
Example Mapping
| PointClickCare Field | Canonical Field | Target Field |
|---|---|---|
| residentId | sourceResidentId | resident_id |
| facilityId | facilityId | facility_id |
| status | residentStatus | resident_status |
| admissionDate | admissionDate | admission_date |
Martini implementation pattern
A scheduler-triggered Martini workflow reads the last watermark, calls PointClickCare REST APIs with facility and incremental filters, paginates through results, and maps residents and census changes into staging and final Snowflake structures. It applies data-minimization rules, uses deterministic source keys for idempotent upserts, records reconciliation totals, and routes validation failures or throttling conditions through controlled retry and exception handling.
Martini capabilities used
- scheduled workflows
- API consumption
- pagination and checkpoints
- data mapping
- business rules
- idempotent writes
- error handling
Pattern 2: Distribute approved clinical and medication data
When to use this pattern
Use this pattern when an approved downstream clinical, reporting, or interoperability application requires selected encounters, medications, or assessments that are available under the customer’s PointClickCare product and scopes.
Integration direction
Example Mapping
| PointClickCare Field | Canonical Field | Target Field |
|---|---|---|
| residentId | patientReference | patient_id |
| encounterStatus | encounterStatus | encounter_status |
| medicationName | medicationDisplayName | medication_name |
| assessmentDate | assessmentDate | assessment_date |
Martini implementation pattern
Martini retrieves only the enabled resources and permitted fields, validates resident and facility identifiers, normalizes dates, codes, statuses, and null values, and sends the approved representation to the target API. Business rules prevent unauthorized data transfer, while source identifiers and payload-level outcomes support reconciliation, safe retries, and exception review.
Martini capabilities used
- API consumption
- data minimization
- data mapping
- validation
- business rules
- workflow orchestration
- error handling
Pattern 3: Create operational cases from integration exceptions
When to use this pattern
Use this pattern when PointClickCare synchronization failures, facility discrepancies, rejected records, or defined operational conditions need to be visible to an enterprise service-management team.
Integration direction
Example Mapping
| PointClickCare Field | Canonical Field | Target Field |
|---|---|---|
| facilityId | facilityReference | business_service_or_location |
| resourceType | sourceObjectType | category |
| sourceId | sourceRecordId | correlation_id |
| errorMessage | exceptionDescription | description |
Martini implementation pattern
A Martini workflow classifies PointClickCare responses and integration exceptions, suppresses sensitive payload details, and creates or updates a ServiceNow case with source identifiers and correlation metadata. Transient API failures are retried before case creation, while permanent validation and authorization errors are routed directly to an operational queue.
Martini capabilities used
- workflow orchestration
- conditional routing
- data mapping
- business rules
- API consumption
- error handling
- monitoring
Pattern 4: Expose a controlled PointClickCare API façade
When to use this pattern
Use this pattern when multiple internal applications need consistent access to selected PointClickCare information without each application implementing PointClickCare authentication, pagination, product-specific schemas, and data-protection rules.
Integration direction
Example Mapping
| PointClickCare Field | Canonical Field | Target Field |
|---|---|---|
| residentId | residentReference | residentId |
| facilityId | facilityReference | facilityId |
| status | currentStatus | status |
| lastModified | sourceModifiedAt | modifiedAt |
Martini implementation pattern
Martini exposes a controlled REST API, authenticates internal callers, invokes PointClickCare only for permitted resources, normalizes responses, and applies authorization and field-minimization rules. The façade can centralize caching or checkpoint logic where appropriate and returns consistent errors while preserving PointClickCare correlation information for support.
Martini capabilities used
- API exposure
- API consumption
- authentication and authorization
- data transformation
- business rules
- error handling
Applications commonly integrated with PointClickCare
PointClickCare data can be integrated with named enterprise applications when the customer has the required PointClickCare product access, permissions, and approved data-sharing process. These are architecture patterns rather than claims of universal native integrations, and sensitive healthcare information should be limited to the fields required for each business purpose.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize approved facility, organization, referral, or customer-engagement data with relationship-management processes. | PointClickCare → Martini → Salesforce | Martini retrieves permitted PointClickCare resources through REST APIs, applies field-level data-minimization rules, maps facility and organization identifiers to Salesforce objects, and handles rejected writes through an exception workflow. |
| Microsoft Dynamics 365 | Coordinate approved account, referral, relationship, and operational information with PointClickCare facilities and organizations. | PointClickCare → Martini → Microsoft Dynamics 365 | A Martini workflow performs scheduled incremental reads, normalizes identifiers and statuses, applies business rules for permitted fields, and upserts approved data into Dynamics 365 with retry and reconciliation handling. |
| Workday | Align workforce, organization, and facility reference data with PointClickCare operational processes. | Workday → Martini → PointClickCare | Martini orchestrates the exchange between Workday and PointClickCare APIs, validates facility and organization mappings, excludes unauthorized clinical data, and routes validation failures for review. |
| UKG Pro | Reconcile employee, organization, and workforce-related reference data with facility operations. | UKG Pro → Martini → PointClickCare | Martini schedules source reads, transforms workforce and facility reference values into the PointClickCare API model where write operations are permitted, and records source identifiers for reconciliation. |
| NetSuite | Connect approved facility, billing, financial, or organizational data with ERP processes. | PointClickCare → Martini → NetSuite | Martini retrieves permitted PointClickCare data, maps facility and financial reference values to NetSuite structures, applies write-back rules only to supported resources, and isolates failed transactions for retry. |
| Snowflake | Centralize approved PointClickCare operational and clinical datasets for reporting and analytics. | PointClickCare → Martini → Snowflake | A scheduled Martini workflow extracts paginated PointClickCare data into staging structures, records extraction watermarks and source identifiers, applies schema normalization, and writes curated data to Snowflake. |
| ServiceNow | Create operational cases or service requests from defined PointClickCare exceptions, synchronization failures, or approved operational events. | PointClickCare → Martini → ServiceNow | Martini evaluates PointClickCare responses and exception conditions, creates or updates ServiceNow records through its API, preserves correlation identifiers, and optionally processes status updates where PointClickCare write-back is supported. |
| Epic | Coordinate approved resident or patient-related information across post-acute and broader healthcare workflows. | PointClickCare → Martini → Epic | Martini mediates approved API or interoperability exchanges, validates patient and facility identifiers, minimizes sensitive fields, applies reconciliation rules, and routes unmatched or rejected records to an exception process. |
How to build a PointClickCare integration in Martini
Objective
Establish approved PointClickCare access for the exact product, tenant, facility scope, environment, and API resources required by the integration.
Instructions in Martini
- Confirm PointClickCare provisioning, API base URL, scopes, resource permissions, and test credentials.
- Store client credentials, token configuration, and environment-specific values in Martini secrets.
- Configure OAuth-style bearer-token acquisition and token refresh or reacquisition behavior.
- Separate sandbox, test, and production configuration where available.
Objective
Select a trigger based on the confirmed PointClickCare capabilities and the required freshness of the downstream data.
Instructions in Martini
- Use a scheduler for incremental API synchronization when event delivery is unavailable or limited.
- Use a protected receiving API only when PointClickCare supplies a documented callback or event contract.
- Define facility scope, resource scope, and synchronization frequency.
Objective
Read only the PointClickCare resources and fields permitted by the customer’s product, tenant, agreement, and granted scopes.
Instructions in Martini
- Call the documented PointClickCare REST endpoints from a Martini workflow.
- Implement endpoint-specific pagination, page-size, timestamp, status, or cursor behavior.
- Persist a watermark or checkpoint and use an overlap window when required.
- Preserve PointClickCare resource identifiers, facility identifiers, and source timestamps.
Objective
Coordinate API calls, pagination, filtering, validation, transformation, target writes, and operational outcomes as one maintainable integration flow.
Instructions in Martini
- Separate authentication, retrieval, transformation, target delivery, and reconciliation logic into clear workflow stages.
- Apply facility and tenant authorization boundaries before processing data.
- Route transient failures to safe retry handling and permanent failures to an exception process.
- Avoid writing access tokens or protected healthcare data to logs.
Objective
Convert PointClickCare JSON resources into a canonical or target-specific model while preserving source identity and handling product variation.
Instructions in Martini
- Map residents, facilities, census, encounters, medications, or assessments only when enabled.
- Normalize dates, time zones, codes, statuses, optional fields, and explicit nulls.
- Apply data-minimization rules and exclude fields not required for the business process.
- Use deterministic keys for idempotent upserts and reconciliation.
Objective
Enforce business, authorization, data-quality, and privacy rules before information is written to downstream systems.
Instructions in Martini
- Validate required resident, facility, and source identifiers.
- Reject or quarantine malformed, unauthorized, or incomplete records.
- Distinguish read-only resources from resources for which PointClickCare permits writes.
- Apply retention, masking, and protected-data handling requirements.
Common PointClickCare data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Residents | Synchronize approved resident demographics, identifiers, status, and related care information. | Salesforce, Microsoft Dynamics 365, Snowflake, Epic, approved reporting databases | Martini retrieves the resource through the enabled REST API, preserves PointClickCare and facility identifiers, minimizes fields, validates required values, and performs idempotent downstream upserts. |
| Facilities | Represent skilled-nursing, senior-living, or other participating care facilities and support facility-level filtering and reconciliation. | Salesforce, Microsoft Dynamics 365, Workday, UKG Pro, NetSuite | Martini maps facility identifiers and reference values, applies tenant and facility authorization rules, and uses facility keys to partition synchronization and error reporting. |
| Census | Exchange resident presence, admission, discharge, transfer, and facility census information. | Snowflake, reporting databases, operational applications, approved healthcare systems | Martini retrieves supported census data incrementally, normalizes status and date values, applies overlap-window logic, and reconciles totals by facility and extraction period. |
| Encounters | Distribute resident care or service interactions where the provisioned PointClickCare API includes encounter resources. | Epic, Snowflake, approved clinical or reporting applications | Martini validates resident and facility identifiers, transforms dates and statuses, limits sensitive fields, and routes unsupported or incomplete records to an exception process. |
| Medications | Exchange medication orders, administration, or medication-related information where enabled by the customer’s API scope. | Epic, Snowflake, approved clinical applications | Martini processes only explicitly authorized fields, preserves source identifiers, validates required medication attributes, avoids unnecessary logging of protected data, and applies safe retry rules. |
| Assessments | Distribute clinical or care assessments where the customer’s PointClickCare product and API permissions provide access. | Snowflake, approved reporting platforms, clinical applications | Martini maps assessment schemas into a canonical model, handles optional fields and explicit nulls, records source version or timestamps where available, and supports reconciliation and exception handling. |
Authentication and security considerations
OAuth-style access tokens
PointClickCare integrations use an OAuth 2.0-style bearer-token model. The exact grant, scopes, client registration process, token endpoint, and environment configuration must be confirmed for the enabled API product and tenant.
Secrets and authorization boundaries
- Store client credentials and token configuration in encrypted, environment-specific Martini secrets.
- Request only the scopes required by the workflow.
- Treat tenant and facility access as authorization boundaries in addition to application authentication.
- Separate sandbox, test, and production credentials where available.
Healthcare data protection
- Transfer only the minimum resident, clinical, medication, encounter, or assessment data required.
- Do not write access tokens or unnecessary protected healthcare data to logs.
- Apply customer-approved retention, deletion, access-control, and data-processing requirements to staging and exception data.
Operational considerations for PointClickCare integrations
Pagination and incremental reads
Confirm page sizes, cursors, timestamps, status filters, and maximum result behavior for each PointClickCare endpoint. Store a watermark and use overlap windows with idempotent upserts when necessary.
Rate limits and retries
Confirm tenant-specific quotas and burst behavior. Apply exponential backoff with jitter for throttling and transient failures, limit concurrency, and avoid unnecessary one-request-per-resident patterns.
Idempotency and reconciliation
Preserve PointClickCare resource and facility identifiers. Use deterministic source keys, separate create and update handling, and produce reconciliation totals by facility, resource type, and extraction window.
Schema variation
Resource availability and fields vary by product, API version, tenant, and scope. Design mappings for optional fields and explicit nulls, and track API and schema changes.
Testing and observability
Test with representative tenant and facility data, including authorization failures, throttling, malformed records, pagination boundaries, and duplicate deliveries. Monitor synchronization lag, token failures, record counts, failure rates, and facility-level discrepancies.
Why use Martini instead of scripts or point-to-point integrations?
Centralized integration logic
Martini keeps PointClickCare authentication, pagination, filtering, mapping, business rules, and target delivery in maintainable workflows rather than duplicating those concerns across scripts or applications.
Controlled data handling
Workflows can enforce facility scope, data minimization, validation, protected-data handling, idempotency, and exception routing before data reaches downstream systems.
Reusable APIs and transformations
Martini can consume PointClickCare REST APIs and expose a controlled REST API façade for internal applications, shielding consumers from PointClickCare-specific schemas and token handling.
Operational reliability
Scheduled execution, checkpoints, retry policies, reconciliation, monitoring, and structured error handling provide a more consistent operating model than isolated point-to-point scripts.
Frequently asked questions
PointClickCare is primarily integrated through its REST-oriented APIs for approved partner and customer applications. Martini can authenticate with the OAuth 2.0-style access-token model, retrieve enabled resources such as Residents, Facilities, Census, Encounters, Medications, and Assessments, transform the data, and deliver it to approved applications, databases, or internal APIs. Scheduled incremental synchronization is appropriate when event delivery is unavailable or limited.
Yes. Martini can integrate with PointClickCare by consuming its documented REST APIs, storing credentials and token configuration securely, orchestrating scheduled or API-led workflows, mapping PointClickCare JSON, and writing approved data to downstream systems. A general-purpose PointClickCare webhook capability was not confirmed, so event-driven designs require product-specific verification.
No. A dedicated PointClickCare connector is not required. Martini can integrate using PointClickCare’s confirmed native REST APIs and OAuth-style authentication, with any customer-specific callbacks, exports, or other endpoints handled only when their contracts are documented and approved.
Lonti does not charge an additional per-connector or per-vendor fee to integrate PointClickCare. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from PointClickCare, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment choices.
Use the PointClickCare REST APIs and the API resources, scopes, and operations provisioned for the customer’s product and tenant. PointClickCare uses an OAuth 2.0-style access-token model. GraphQL, SOAP, universal bulk APIs, general file APIs, and direct database access were not confirmed as current general-purpose mechanisms.
A general-purpose webhook or outbound callback mechanism for all PointClickCare events was not confirmed in the supplied research. A specific product or customer agreement may provide event notifications, but event coverage, authentication, delivery, and retry behavior must be verified. Otherwise, Martini can use scheduled incremental API reads.
Martini can maintain a synchronization watermark, retrieve overlapping incremental windows, paginate through PointClickCare responses, preserve source and facility identifiers, and perform idempotent upserts. Mapping workflows normalize dates, statuses, codes, optional fields, and null values while applying facility, authorization, data-minimization, and target-system business rules.
Martini can distinguish authentication, authorization, throttling, validation, transient server, and business-rule failures. Safe transient operations can use controlled exponential backoff and retry, while permanent failures can be routed to an exception process. Deterministic keys based on the source resource, tenant or facility, and PointClickCare identifier help prevent duplicates and support reconciliation.
Related Martini documentation
Workflows
Connect PointClickCare with Martini
Use Martini to build secure, maintainable PointClickCare integrations around approved REST APIs, scheduled synchronization, data protection rules, and enterprise workflow orchestration.