For AI agents: the documentation index is at /docs/payerbox/llms.txt. A Markdown version of this page is available at /docs/payerbox/releases.md or by requesting it with the Accept: text/markdown header.
Payerbox Docs

Releases

This page tracks notable changes across Payerbox: the Interop APIs, the Prior Auth (ePA) APIs, and the FHIR App Portal. Releases are listed newest first. The apps run on an Aidbox FHIR server; each component heading links to its image on Docker Hub.

July 2026 (2607)

Interop APIs 2607

Payer-to-Payer and Provider Access

  • $davinci-data-export now removes remittance and enrollee cost-sharing data from exported ExplanationOfBenefit and Coverage resources. All money elements are removed including totals, payments, benefit balances, item/detail/subdetail/addItem prices and amounts, adjudication amounts, costToBeneficiary, and subrogation while clinical and administrative content, extensions, and contained resources are retained.

Prior Auth (ePA) APIs 2607

PAS

  • Prior authorization requests can now be routed to an external utilization management (UM) system according to Claim.insurer. The pas-passthrough connector forwards requests to any conformant Da Vinci PAS delegate, using its Claim/$submit and Claim/$inquire endpoints, preserving request identifiers and preventing duplicate submissions during retries. Configure the delivery path with UMTenantConfig. See UM System Integration and PAS.
  • Added an integration with HealthEdge GuidingCare for PAS decisioning. The guidingcare connector uses GuidingCare's REST API and payer-configured ConceptMap crosswalks to translate requests and decisions. See UM System Integration and UMTenantConfig.
  • Configurable lenient FHIR validation can treat display-name and referenced-resource profile mismatches as warnings. Structural, profile, and missing-reference errors remain blocking. See PAS validation strictness.

CRD

  • Configurable lenient FHIR validation can tolerate hook-context references that exist only in the EHR and cannot be resolved by Payerbox. See CRD validation strictness.

Analytics

  • The PAS metrics SQL-on-FHIR package (io.healthsamurai.pas-metrics 0.1.2) is available on request. Contact us to receive the package, which includes 10 ViewDefinition resources and 15 Library resources implementing metrics suggested by the PAS Implementation Guide. See Analytics, flat views, and SQL on FHIR data.

FHIR App Portal 2607

  • MPF pipeline configuration supports publishing the provider-directory index.json file. See MPF Pipeline and the MPF endpoint reference.
  • The app-detail page now includes a Policies and legal links card for the developer's privacy policy and terms of service. Missing values are marked Not provided, and apps requesting patient data without a privacy policy display a warning. See Admin Portal.
  • When declining an app, an administrator can add a free-text note alongside the preset reason; developers see both on the declined app. See Admin Portal.

June 2026 (2606)

A new payerbox umbrella Helm chart deploys the full stack (portals, Interop APIs, Prior Auth, and Aidbox) to Kubernetes. See Deploy.

Interop APIs 2606

Payer-to-Payer

Provider Directory

  • The CMS Medicare Plan Finder (MPF) provider-directory pipeline now runs its scope filters inside the $export query and gzip-compresses the export output. A runnable reference implementation is public in the Aidbox examples. See the MPF Pipeline.

Prior Auth (ePA) APIs 2606

CRD

  • Upgraded to Da Vinci CRD 2.1.0. See CRD.
  • When the decision service returns an error, Payerbox relays its HTTP status and surfaces the original error in the returned OperationOutcome.

DTR

  • Upgraded to Da Vinci DTR 2.1.0. See DTR.

PAS

  • Upgraded to Da Vinci PAS STU 2.1.0, now the default. STU 2.0.1 remains selectable via the PAS_IG_VERSION environment variable. See PAS.
  • Claim/$submit adds a ClaimResponse reference extension on the submitted Claim, linking it to the resulting ClaimResponse.
  • Claim/$submit is idempotent on Claim.identifier: resubmitting a Claim whose identifier already exists returns the existing ClaimResponse and does not create a duplicate prior authorization.
  • Under PAS 2.1.0, an updated prior authorization keeps a single ClaimResponse on the original Claim; Claim/$submit and Claim/$inquire return it for any Claim in the update chain.

FHIR App Portal 2606

Developer Portal

  • Register a backend (bulk data) service with a client secret (client-credentials), in addition to a JWKS URI. See Backend Services.

Admin Portal

  • Redesigned the app review card.

May 2026 (2605)

Interop APIs 2605

Provider Access

Payer-to-Payer

  • Added the $bulk-member-match operation: asynchronous demographic matching with mandatory per-member HRex consent opt-in, returning matched, non-matched, and consent-constrained result buckets. See Payer-to-Payer.

Provider Directory

  • Added a CMS Medicare Plan Finder (MPF) provider-directory export (opt-in per deployment): builds the MPF provider feed and publishes a public index URL per Medicare Advantage contract and reporting year, designed to run on a daily schedule.

Prior Auth (ePA) APIs 2605

CDS Hooks

CRD

  • Custom-response mode (CDS_DECISION_SERVICE_CUSTOM_RESPONSE): the decision service returns simplified per-order decisions and Payerbox assembles the CDS Hooks–conformant response — a CRD STU2 systemActions array the EHR applies automatically, with cards kept informational.
  • Required request headers can be enforced via CDS_REQUIRED_HEADERS. See CRD.

DTR

  • DTR delivers coverage questionnaires and rules to the EHR or the SMART App via the $questionnaire-package operation, with client-side FHIRPath prefill. See DTR.

PAS

  • Added the Claim/$submit (initial prior-authorization submission) and Claim/$inquire (status check) operations. See PAS.
  • Added the $submit-attachment operation (Da Vinci CDeX) for attaching supporting clinical documents.
  • Added asynchronous result delivery: completed decisions are delivered to the EHR as a PAS Response Bundle via a topic-based FHIR Subscription.
  • When additional documentation is submitted via $submit-attachment, the prior authorization is re-queued for review (ClaimResponse disposition "Pending Review").

FHIR App Portal 2605

Developer Portal

  • Register SMART apps with configurable scopes and supported search parameters, including DSI (decision-support intervention) transparency fields. See SMART App.
  • Register backend (system) services for the bulk data APIs; these clients authenticate with a customer-supplied jwks_uri (JWKS URL) rather than a client secret. See Backend Services.

Admin Portal

  • Enroll and manage members (patients) from the portal via a verification-email signup flow. See Admin Portal.
  • Manage admin users: create, delete, reset passwords, and disable 2FA.
  • Audit-event log viewer with search and detail, plus a PHI Access viewer scoped to SMART-app activity.
  • Configurable portal branding and theming, configurable Terms of Service and Privacy Policy, configurable email provider, and single- and multi-organization support.

FHIR App Gallery

  • Discover, launch, and test registered SMART apps. See FHIR App Gallery.
  • Patients can review their connected apps and revoke access.

Security & Authentication

  • Multi-tenant deployments: host multiple organizations on one instance with per-organization data isolation, built on Aidbox OrgBAC. Org-scoped admins manage only their own organization.
  • Role-based access control: admin, developer, and patient roles gate the Admin Portal, Developer Portal, and app gallery.

Last updated: