PointClickCare and Post-Acute Care EHR Interoperability: Standards, APIs, and Clinical Data Exchange

PointClickCare is a cloud-based electronic health record (EHR) platform built for long-term and post-acute care (LTPAC) providers, including skilled nursing facilities (SNFs), senior living communities, and home health agencies. Unlike acute hospital EHR and EMR systems that center on episodic inpatient admissions and surgical workflows, LTPAC and behavioral health EHRs organize longitudinal resident records around federally mandated standardized patient assessments, interdisciplinary care planning, and multi-facility transitions of care.

Overview of Post-Acute, Behavioral Health, and Community EHR Architectures

In the United States healthcare informatics ecosystem, clinical documentation requirements diverge sharply once a patient leaves a tertiary acute care hospital. The Improving Medicare Post-Acute Care Transformation (IMPACT) Act of 2014 (Public Law 113-185) mandates standardized patient assessment data reporting across four post-acute care settings: Skilled Nursing Facilities, Home Health Agencies, Inpatient Rehabilitation Facilities, and Long-Term Care Hospitals. Parallel state and federal rules govern home- and community-based services (HCBS), behavioral health, substance use disorder (SUD) treatment, and rural critical access hospitals.

Because each care setting operates under distinct regulatory reporting schemas and reimbursement models, health systems and clinical research networks routinely interface with specialized platform families rather than a single monolithic vendor. Understanding how PointClickCare compares to adjacent post-acute, behavioral health, and rural hospital platforms is essential for health informatics architects designing longitudinal clinical data management pipelines or real-world data (RWD) linkages.

Comparison of Post-Acute, Behavioral Health, and Community EHR Platforms

The table below classifies major specialized EHR platforms by their primary care setting, mandated regulatory assessment or compliance standard, and core interoperability architecture.

Platform / System	Primary Care Setting	Core Regulatory & Assessment Alignment	Primary Interoperability & Data Exchange Focus
PointClickCare	Skilled Nursing Facilities (SNFs), senior living, home health	CMS Minimum Data Set (MDS 3.0), PDPM, ONC 45 CFR 170.315(g)(10)	PointClickCare REST APIs, FHIR R4 / USCDI Connector, Carequality & CommonWell C-CDA exchange, real-time ADT notifications
MatrixCare	SNFs, life plan communities, home health, hospice	CMS MDS 3.0, OASIS-E, Hospice Item Set (HIS)	Carequality/CommonWell document query, HL7 v2 ADT/pharmacy interfaces, FHIR API endpoints
Homecare Homebase (HCHB)	Home health and hospice agencies	CMS OASIS-E, PDGM, 21st Century Cures Act Electronic Visit Verification (EVV)	Point-of-care mobile synchronization, HL7 referral ingestion, Carequality/CommonWell interoperability
Alora Health	Home health care and personal care agencies	CMS OASIS-E, state Medicaid EVV compliance (Section 12006 of Cures Act)	Integrated GPS/telephony EVV state aggregator exports, electronic claim generation (ASC X12 837I/837P)
Netsmart (myAvatar / myEvolv)	Behavioral health, human services, CCBHCs, post-acute care	42 CFR Part 2 SUD consent segmentation, CCBHC quality measures, state mental health reporting	Carequality framework connectivity, HL7 FHIR R4 APIs, bellweather HIE integration, e-prescribing (NCPDP SCRIPT)
Kipu EMR	Addiction treatment, substance use disorder (SUD), behavioral health	42 CFR Part 2 confidentiality, ASAM (American Society of Addiction Medicine) continuum criteria	Laboratory outreach interfaces (HL7 ORU/ORM), CRM admission APIs, MAT dispensing and e-prescribing
Valant EHR	Outpatient behavioral health and psychiatric practices	Measurement-based care instruments (PHQ-9, GAD-7), outpatient psychiatric E/M documentation	Patient portal outcome instrument capture, e-prescribing, clearinghouse EDI claims integration
Therap	Intellectual and Developmental Disabilities (I/DD) and Long-Term Services & Supports (LTSS)	HCBS 1915(c) waiver documentation, Individual Support Plans (ISPs), state EVV mandates	Direct support professional (DSP) service logging, medication administration records (MAR), state Medicaid reporting
TruBridge (formerly CPSI / Evident Thrive EHR)	Rural, community, and Critical Access Hospitals (CAHs)	CMS Promoting Interoperability, ONC Health IT certification, rural inpatient/outpatient quality reporting	FHIR R4 patient and population APIs, C-CDA care summaries, integrated hospital revenue cycle management
MEDHOST	Community hospitals, rural acute facilities, emergency departments	ONC Cures Act certification, CMS electronic clinical quality measures (eCQMs)	Emergency department information system (EDIS) tracking, FHIR R4 APIs, Carequality/CommonWell exchange

How Do Post-Acute and Behavioral Health EHRs Like PointClickCare and Netsmart Integrate With Acute Hospital EHRs?

Post-acute and behavioral health EHRs integrate with acute hospital EHRs through four complementary technical layers: national trust frameworks (Carequality and CommonWell Health Alliance), HL7 v2 event messaging, HL7 Consolidated Clinical Document Architecture (C-CDA) document exchange, and HL7 FHIR RESTful APIs.

1. Admission, Discharge, and Transfer (ADT) Event Routing: Under CMS Conditions of Participation (42 CFR § 482.24(d)), hospitals with electronic event notification capabilities must send real-time notifications to post-acute providers and primary care practitioners when a patient is admitted, discharged, or transferred from an emergency department or inpatient unit. PointClickCare and Netsmart ingest HL7 v2 ADT messages (`ADT^A01`, `ADT^A03`, `ADT^A04`) via regional Health Information Exchanges (HIEs) and national alerting networks to trigger care transition workflows.
2. Query-Based Document Exchange (Carequality and CommonWell): When a hospital discharges a patient to a skilled nursing facility using PointClickCare or MatrixCare, or refers a patient to a behavioral health clinic running Netsmart `myEvolv`, the receiving EHR queries the acute hospital EHR over IHE Cross-Community Access (XCA) profiles governed by Carequality. The hospital returns a structured HL7 C-CDA Continuity of Care Document (CCD) or Discharge Summary containing active problems (SNOMED CT / ICD-10-CM), reconciled medications (RxNorm), allergies, laboratory results (LOINC), and recent procedures.
3. Granular Privacy Filtering for Behavioral Health: Integrating behavioral health platforms such as Netsmart `myEvolv` or Kipu EMR with acute hospital networks requires technical enforcement of federal substance use disorder confidentiality rules under 42 CFR Part 2 alongside HIPAA. Standards such as HL7 Data Segmentation for Privacy (DS4P) and FHIR `Consent` resources allow behavioral health systems to tag restricted SUD records with security labels so they are only disclosed when explicit patient consent parameters are satisfied.
4. Community and Critical Access Hospital Handoffs: Rural and community hospitals running TruBridge (formerly CPSI, developer of the Evident Thrive EHR) or MEDHOST frequently serve as both the acute discharging facility and the operator of hospital-based swing beds or affiliated skilled nursing units. Standardized C-CDA and FHIR R4 APIs bridge inpatient acute charts with downstream post-acute documentation without manual re-keying.

What APIs Does PointClickCare Provide for Long-Term Care Data Exchange?

PointClickCare provides two primary API tiers for clinical interoperability, third-party application integration, and health services research: its partner RESTful API suite and its ONC-certified HL7 FHIR R4 API (`USCDI Connector`).

• ONC Cures Act Standardized FHIR R4 API: To comply with the 21st Century Cures Act certification criterion at 45 CFR § 170.315(g)(10), PointClickCare supports HL7 FHIR Release 4.0.1 profiled to the HL7 FHIR US Core Implementation Guide and the United States Core Data for Interoperability (USCDI). Authentication and authorization follow the SMART App Launch Framework (OAuth 2.0 and OpenID Connect), supporting both patient-facing standalone launches and clinician-facing EHR launches.
• Population-Level Bulk Data Export: For accountable care organizations (ACOs), value-based care analytics, and multi-site clinical research cohorts, the FHIR Bulk Data Access (`$export`) specification enables authorized backend services (authenticated via asymmetric JSON Web Tokens) to retrieve newline-delimited JSON (`ndjson`) files for cohorts of residents without overloading transactional database endpoints.
• Operational and Partner REST APIs: Beyond USCDI core resources (`Patient`, `Encounter`, `Condition`, `MedicationRequest`, `Observation`, `AllergyIntolerance`, `CarePlan`, `DocumentReference`, `Immunization`), PointClickCare’s developer platform exposes operational endpoints for census management, bed availability, progress notes, vitals capture, pharmacy order synchronization, and webhook subscriptions triggered by resident admission, transfer, discharge, or room changes.

How Are PACIO Project FHIR Implementation Guides Improving Post-Acute Care Interoperability?

Historically, even when acute hospitals and skilled nursing facilities exchanged C-CDA documents, critical post-acute functional and cognitive assessment data remained locked in setting-specific formats or unstructured PDFs. When a SNF completes a CMS Minimum Data Set (MDS 3.0) assessment or a home health agency completes an OASIS-E assessment, those standardized items are stored in the CMS Data Element Library (DEL).

The PACIO (Post-Acute Care Interoperability) Project—a collaborative initiative established by CMS, ONC, MITRE, and industry vendors—solves this semantic gap by mapping CMS DEL assessment items to LOINC and SNOMED CT codes and publishing HL7 FHIR R4 Implementation Guides:

• PACIO Functional Performance IG: Standardizes the exchange of patient self-care (eating, oral hygiene, toileting, dressing) and mobility (sit-to-stand, bed-to-chair transfers, walking distances) observations aligned with CMS MDS 3.0 Section GG and the World Health Organization’s International Classification of Functioning, Disability and Health (ICF).
• PACIO Cognitive Status IG: Profiles FHIR `Observation` and `QuestionnaireResponse` resources to represent standardized cognitive evaluations, including the Brief Interview for Mental Status (BIMS), Confusion Assessment Method (CAM), and Patient Health Questionnaire (PHQ-9) recorded during post-acute stays.
• PACIO Advance Directive Interoperability (ADI) IG: Establishes FHIR profiles to represent patient-authored advance directives, living wills, healthcare agent designations, and portable medical orders (such as POLST/MOLST) so life-sustaining treatment preferences travel intact between SNFs, home health agencies, and emergency departments.
• PACIO Transitions of Care (ToC) IG: Packages medication reconciliation, functional status, cognitive status, and advance directives into a unified FHIR `Composition` payload during care handoffs.

Selecting and Evaluating LTPAC and Behavioral Health EHR Data Sources in Research

For clinical trialists, health services researchers, and health system informaticists evaluating post-acute or behavioral health EHRs for pragmatic trials or real-world evidence (RWE) studies, platform capabilities should be verified against four technical criteria:

1. Assessment Instrument Fidelity: Confirm whether the platform captures native item-level responses for CMS MDS 3.0 (SNFs), OASIS-E (Home Health), ASAM criteria (Kipu EMR / SUD), or HCBS Individual Support Plans (Therap), and whether those items map to LOINC codes in the CMS Data Element Library.
2. ONC 45 CFR 170.315(g)(10) Certification Status: Check the ONC Certified Health IT Product List (CHPL) to verify whether the specific vendor module holds active certification for standardized FHIR R4 single-patient and bulk population APIs. Note that historically, non-physician post-acute and behavioral health vendors were excluded from original HITECH meaningful use incentives, meaning certification adoption varies across modules.
3. Electronic Visit Verification (EVV) and Mobile Provenance: For home health and HCBS studies utilizing Homecare Homebase, Alora Health, or Therap, verify how point-of-care mobile timestamps and EVV metadata (mandated under Section 12006 of the 21st Century Cures Act) are logged to satisfy source data audit trail requirements.
4. 42 CFR Part 2 and HIPAA Consent Granularity: When extracting real-world data from behavioral health platforms (Netsmart `myEvolv`, Kipu EMR, Valant EHR), confirm how the system segregates Part 2 substance use disorder records from general mental health records prior to de-identification or Limited Data Set generation.

Frequently Asked Questions

How do post-acute and behavioral health EHRs like PointClickCare and Netsmart integrate with acute hospital EHRs?

They integrate using four primary mechanisms: HL7 v2 ADT event notifications (supporting CMS CoP discharge notification rules), query-based HL7 C-CDA document exchange over Carequality and CommonWell Health Alliance, ONC-certified HL7 FHIR R4 RESTful APIs with SMART on FHIR authorization, and privacy-segmented clinical summaries for behavioral health records governed by 42 CFR Part 2.

What APIs does PointClickCare provide for long-term care data exchange?

PointClickCare offers an ONC-certified FHIR R4 API (`USCDI Connector`) supporting SMART on FHIR OAuth 2.0 and FHIR Bulk Data Access (`$export`), alongside partner RESTful APIs and event webhooks for census, ADT events, vitals, medication orders, allergies, conditions, and care plans.

How are PACIO Project FHIR Implementation Guides improving post-acute care interoperability?

PACIO Project FHIR Implementation Guides map standardized assessment questions from the CMS Data Element Library (such as MDS 3.0 Section GG mobility/self-care items and BIMS cognitive scores) into machine-readable HL7 FHIR R4 profiles for Functional Performance, Cognitive Status, Advance Directives, and Transitions of Care.

Sources

• Office of the National Coordinator for Health IT (ONC), 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program (45 CFR § 170.315(g)(10) Standardized API for Patient and Population Services), ecfr.gov.
• HL7 International & MITRE, Post-Acute Care Interoperability (PACIO) Project: Functional Performance, Cognitive Status, Advance Directive Interoperability, and Transitions of Care FHIR Implementation Guides, pacioproject.org.
• Centers for Medicare & Medicaid Services (CMS), Data Element Library (DEL) and IMPACT Act of 2014 Standardized Patient Assessment Data Elements, del.cms.gov.
• PointClickCare Technologies, PointClickCare Developer API and ONC Health IT Certification Documentation, pointclickcare.com.