From bed6c23b7ca266ec2fbc514f856786c9ec837cc3 Mon Sep 17 00:00:00 2001 From: Nesmesnhnoy Date: Mon, 1 Jun 2026 21:14:26 +0100 Subject: [PATCH] Trim Releases page outline; fix $davinci-data-export entry Demote the per-capability sub-headings (Provider Access, CDS Hooks, etc.) from H3 to bold labels so the GitBook "On this page" outline lists only the component sections: Interop APIs, Prior Auth (ePA) APIs, FHIR App Portal, Security & Authentication, Demo. Fix the $davinci-data-export entry: it is not limited to the provider-download type and does not exclude pharmacy/drug data. It is an asynchronous FHIR Bulk Data export over a member Group, used by both Provider Access and Payer-to-Payer. Co-Authored-By: Claude Opus 4.7 --- docs/releases.md | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/docs/releases.md b/docs/releases.md index e8b1e6d..64ee11c 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -10,30 +10,37 @@ This is the **May 2026** release (tag `2605`); the apps run on an Aidbox FHIR se ## Interop APIs [`2605`](https://hub.docker.com/r/healthsamurai/interop) -### Provider Access +**Provider Access** + - Added the [`$provider-member-match`](api-reference/operations/provider-member-match.md) operation: asynchronous demographic matching with treatment attestation and opt-out consent checks. See [Provider Access](interop-apis/provider-access.md). -- Added the [`$davinci-data-export`](api-reference/operations/davinci-data-export.md) operation (`provider-download` type): a consent-aware export that excludes pharmacy/drug data. +- Added the [`$davinci-data-export`](api-reference/operations/davinci-data-export.md) operation: an asynchronous FHIR Bulk Data export over a member `Group`, used by both Provider Access and Payer-to-Payer. + +**Payer-to-Payer** -### Payer-to-Payer - Added the [`$bulk-member-match`](api-reference/operations/bulk-member-match.md) 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](interop-apis/payer-to-payer.md). -### Provider Directory +**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`](https://hub.docker.com/r/healthsamurai/prior-auth) -### CDS Hooks +**CDS Hooks** + - Added the [CDS Services discovery](api-reference/operations/cds-services-discovery.md) endpoint and the [`order-sign`](api-reference/operations/cds-hook-order-sign.md), [`order-select`](api-reference/operations/cds-hook-order-select.md), [`order-dispatch`](api-reference/operations/cds-hook-order-dispatch.md), and [`appointment-book`](api-reference/operations/cds-hook-appointment-book.md) hooks. - Hooks can be enabled individually via the `CDS_ENABLED_HOOKS` setting. -### CRD +**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](prior-auth/crd.md). -### DTR +**DTR** + - DTR delivers coverage questionnaires and rules to the EHR or the SMART App via the [`$questionnaire-package`](prior-auth/dtr/aidbox-questionnaire-package.md) operation, with client-side FHIRPath prefill. See [DTR](prior-auth/dtr/README.md). -### PAS +**PAS** + - Added the [`Claim/$submit`](api-reference/operations/claim-submit.md) (initial prior-authorization submission) and [`Claim/$inquire`](api-reference/operations/claim-inquire.md) (status check) operations. See [PAS](prior-auth/pas.md). - Added the [`$submit-attachment`](api-reference/operations/submit-attachment.md) 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. @@ -41,17 +48,20 @@ This is the **May 2026** release (tag `2605`); the apps run on an Aidbox FHIR se ## FHIR App Portal [`2605`](https://hub.docker.com/r/healthsamurai/fhir-app-portal) -### Developer Portal +**Developer Portal** + - Register SMART apps with configurable scopes and supported search parameters, including DSI (decision-support intervention) transparency fields. See [Developer Portal](fhir-app-portal/developer-portal.md). - 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 [Authentication](api-reference/authentication.md). -### Admin Portal +**Admin Portal** + - Enroll and manage members (patients) from the portal via a verification-email signup flow. See [Admin Portal](fhir-app-portal/admin-portal.md). - 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 +**FHIR App Gallery** + - Discover, launch, and test registered SMART apps. See [FHIR App Gallery](fhir-app-portal/fhir-app-gallery.md). - Patients can review their connected apps and revoke access.