What’s New This Release

FHIR CarePlan Read + PDF Access

Care Plans can now be retrieved via the FHIR API, including a direct link to the finalized Care Plan PDF.

External systems can:

• Pull structured CarePlan data in valid FHIR format
• Retrieve a linked PDF through a secure, time-limited URL
• Search and retrieve all Care Plans for a specific member

Access is scoped to the requesting organization and requires proper API permissions.

FHIR Patient Read (Internal Member ID)

Members can now be retrieved as standardized FHIR Patient resources using their Pear Suite Member ID.

External systems can:

• Query a member using their ID
• Receive a valid FHIR Patient JSON response
• Receive standardized error responses for invalid or missing IDs

All responses are securely scoped to the organization tied to the API key.

Lock Completed Activities After Provider Sign-Off

Activities tied to a provider Review Request can now be automatically locked once signed.

When locking is enabled:

• Completing and signing the Review Request locks the associated Activity
• Status, start/end times, responsible user, and in-activity responses can no longer be modified
• Billing configuration remains editable so claims can proceed

Locked Activities are enforced across UI, API, and bulk actions, and clearly marked as read-only. This supports payer requirements that mandate finalized documentation prior to claim submission.

Shared Unit Limits Across CPT Codes

Organizations can now configure a shared unit-based billing limit across multiple CPT claim configurations.

When configured:

• Units billed under any linked CPT configuration count toward a single shared cap
• Once the shared limit is reached, enforcement applies across all associated configurations

This ensures contracted unit caps are enforced consistently across related billing structures.

Bi-Directional Health Data Exchange

Pear Suite now supports outbound health data events and cross-system patient identification.

New capabilities include:

External Patient Identifier Mapping

• Maps partner system IDs to internal Pear Suite Member IDs
• Automatically stores identifiers from inbound FHIR and HL7v2 payloads
• Viewable on the Member profile (read-only)

Outbound Event Infrastructure

• Emits events when:
  • Member demographics change
  • Care Plan snapshots are created
• Designed to support webhook or SFTP-based downstream integrations

External systems can:

• Query Pear Suite using their native patient identifier
• Receive updates when key member data changes

This enhances interoperability with Health Information Exchanges (HIEs), health plans, and partner systems.