Read residents from PointClickCare and coordinate care in BloomText conversations from your own software.
Get started for freeSchedule a demo →Yes, with PointClickCare's approval. PointClickCare's FHIR API lets approved apps read residents, care teams, and encounters, and the BloomText API runs the conversations with residents and families. Production access requires a PointClickCare partnership and a per-facility fee.
Your app reads residents, care teams, and encounters through PointClickCare’s API.
It looks up each patient’s BloomText conversation in a simple mapping your app keeps.
It sends reminders and replies with the BloomText API, and reads new patient replies by time range.
PointClickCare stays your system of record. BloomText handles the conversations, and nothing syncs until your app connects the two.
Read the patient from PointClickCare, find the matching BloomText patient by MRN, then send the message to that patient. Store the PointClickCare patient ID as the BloomText patient’s MRN; nothing maps automatically.
GET https://connect2.pointclickcare.com/fhir/R4/<approved-tenant-id>/Patient/<approved-patient-id>Authorization: Bearer <approved-access-token>Accept: application/fhir+jsonUse the base URL, access token, and IDs from your approved vendor environment.
See PointClickCare Patient API specification for the full request.
GET https://api.bloomtext.com/v1/patient-messages?patient_id={patientId}&q=from:patient&page[limit]=50Authorization: Bearer <api-key>POST https://api.bloomtext.com/v1/patient-messagesAuthorization: Bearer <api-key>Idempotency-Key: <unique-request-key>Content-Type: application/json{"to":{"patient_id":"{patientId}"},"body":"Your care conference moved to 2:00 PM today. Reply here with any questions."}Send your organization’s BloomText API key in the Authorization header on every request. POST requests also need Idempotency-Key and Content-Type headers.
PointClickCare’s published FHIR API is read-focused: residents, encounters, care teams, resident contacts, locations, and clinical documents, plus bulk export for system-to-system apps. It has no appointment or messaging resources, so these ideas use BloomText for the conversations and PointClickCare as the source of who, where, and when.
Each resident’s care coordination conversation should hold the nurses, therapists, and attending physician actually assigned to them. Read the resident’s CareTeam from PointClickCare, match each practitioner to a BloomText user, and flag anyone to add or remove when the roster changes.
Uses PointClickCare CareTeam and Practitioner resources
When a new stay starts, post a short note to the unit’s team conversation so the charge nurse, CNAs, and dietary know to expect someone and when the huddle is. The note names the unit and time, not the reason for admission.
Uses PointClickCare Encounter and Location resources
PointClickCare lists each resident’s contacts as RelatedPerson records. Your app links a resident’s responsible party to an existing family conversation in BloomText and posts logistics there: a care conference time, a room move, visiting changes. Staff answer replies in the same thread.
Uses PointClickCare Patient and RelatedPerson resources
When a resident goes out to the hospital, the receiving team needs the continuity of care document fast. Watch for a new CCD in DocumentReference and tell the transfer conversation it is ready to pull from PointClickCare, without pasting its contents into chat.
Uses PointClickCare DocumentReference resource (CCD)
A Bulk app can export a group of residents through the FHIR $export operation. Count current residents per building overnight and post one line per facility to the leadership conversation before stand-up.
Uses PointClickCare Group resource and bulk $export
Patient requests use your organization’s BloomText API key. Posts to a staff team conversation use an org admin’s OAuth token instead, and only reach conversations that admin is part of.
A nightly job that keeps each resident’s BloomText care conversation in step with the active PointClickCare care team.
GET https://connect2.pointclickcare.com/fhir/R4/<approved-tenant-id>/CareTeam?patient=<approved-patient-id>&status=activeAuthorization: Bearer <approved-access-token>Accept: application/fhir+jsonEvery hour, look for stays that started since the last run and post a huddle note to the right unit’s conversation.
GET https://connect2.pointclickcare.com/fhir/R4/<approved-tenant-id>/Encounter?date=ge<last-run-date>Authorization: Bearer <approved-access-token>Accept: application/fhir+jsonPOST https://api.bloomtext.com/v1/me/conversations/{unitConversationId}/messagesAuthorization: Bearer <org-admin-oauth-token>Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"New admission arriving on 2 West this afternoon. Huddle at 3:00 PM at the nurses’ station."}Pull a resident’s messages for a date range when your compliance team needs them on file.
GET https://api.bloomtext.com/v1/patient-messages?patient_id={residentPatientId}&after=2026-08-01&before=2026-09-01&order=asc&page[limit]=100Authorization: Bearer <api-key>In a skilled nursing or senior living building, an agent with PointClickCare data and BloomText can keep care-team conversations staffed correctly, draft family updates for a nurse to approve, and summarize a unit’s threads at shift change.
An org admin creates an API key in BloomText. Your agent’s tools use it to message patients and read their replies, always naming the patient by ID, phone number, or MRN. The key can’t reach staff conversations; for those, the agent uses an org admin’s OAuth token, which reaches only the conversations that admin is part of.
GET https://api.bloomtext.com/v1/organizationAuthorization: Bearer <api-key>You give the agent PointClickCare data through a small tool you write that calls the FHIR API with your approved SMART credentials and returns only the fields the task needs, like care-team members or a resident’s unit. PointClickCare does not document an MCP server or a way to connect outside agents such as Claude or ChatGPT, so the tool is yours to build and host.
For 2 West, get each resident’s active care team from PointClickCare. Check that each resident’s BloomText care conversation includes everyone on that team and list any mismatches. Then read the last 24 hours of messages in those conversations and post a short shift-change summary of unanswered questions to the 2 West team conversation. Do not include diagnoses or medications.Messages the agent sends with the key show the key’s name to staff, and patients see your clinic. An org admin can delete the key at any time. Read the AI agent docs.
Yes. PointClickCare publishes a FHIR R4 API built on US Core, with read and search across 28 resources including Patient, Encounter, CareTeam, RelatedPerson, and DocumentReference, plus bulk export through Group. Requests go to connect2.pointclickcare.com with your tenant ID in the path. Approved Marketplace partners also get PointClickCare’s proprietary APIs, whose documentation is behind the developer portal.
Submit PointClickCare’s partnership application, then create a Developer Program account as a USCDI Connector or Marketplace Partner, turn on two-factor authentication, and register your app. Development apps are auto-approved in the FHIR sandbox, and production apps need PointClickCare approval. The FHIR site lists a flat fee of $65 per app per facility per month for customers on current pricing, and the Marketplace partner agreement charges a fee per facility with a live integration.
Not in the published FHIR API. Its resource list has no Appointment or Communication resource and no subscriptions or webhooks, and writes are limited to creating Groups for export. Plan to read resident data from PointClickCare and keep the conversation itself in BloomText.
Yes. PointClickCare sells Automated Care Messaging, powered by Cliniconex, which sends voice, text, and email notices to residents and families from inside the EHR. Teams use BloomText when they want care-team chat and family conversations in one app, driven from their own software through the BloomText API.
Yes, through tools you build. Your agent reads and sends BloomText messages through the BloomText API, with an organization API key. For PointClickCare, the agent calls your own tool that uses your approved FHIR credentials, because PointClickCare does not document an MCP server or an agent connector.
It can be when every system that touches the data is covered. BloomText turns on API access only for organizations with a signed BAA, and PointClickCare only lets users reach records their accounts are authorized for. Keep family messages to logistics like times and room changes, and confirm the resident has authorized who you share updates with.
PointClickCare's FHIR API is documented publicly, but production apps need PointClickCare's approval. Sandbox apps are approved automatically, and production is billed per app, per facility.
API access is available to organizations with a signed BAA. Book a short call, tell us what you’re building, and we’ll turn on API access so an org admin can create your key. Don’t include PHI when you book.
Links last checked September 21, 2026.
