Sunrise PACE

Documentation

Developer Portal

Sandbox available?

Yes

Info Last Updated

May 11, 2026

Flexpa Endpoint ID

3619d...

Success Rate

The percentage of authorization attempts that successfully complete, from initial redirect through token receipt. This metric directly reflects the reliability and usability of the authorization flow for end users.

No data available

Last 6 months

Authorization Overview

The authorization flow is often the biggest barrier to patient access. This dimension evaluates both the technical implementation and user experience.

Token Type

If an endpoint's access token is refreshable, the Token Refresh API can be used to issue a new access token prior to the refresh token expiring. Otherwise, if the access token is non-refreshable, the user is required to re-authorize the application after the access token expires.

Non-refreshable

Max Auth Period

This is the payer imposed upper bound on the time period for which a user can keep refreshing an access token. Once the maximum authorization period has elapsed, the user is required to re-authorize the application.

No max period

Custom Settings Required?

If an endpoint deviates from the standard authorization flow and custom settings are required. These customizations vary from custom parameters in the authorization or token endpoints, to custom locations for retrieving the patient ID.

Requested scopes

The OAuth scopes Flexpa requests during the authorization flow for this endpoint. These determine what data Flexpa is authorized to access on behalf of the patient.

launch/patientpatient/*.readoffline_accessopenidfhirUser

FHIR API Implementation

The quality and completeness of the FHIR implementation determines the utility of the API for third-party applications and patients alike.

Lines of Business supported

No information

Supported FHIR Resources

Pills with a indicate resources observed in at least one successful sync within the last 6 months across our recent processing history. A resource not marked verified isn't necessarily unavailable — it may simply not appear in any connected user's record (e.g., a patient with no recorded immunizations), or be returned only rarely. Verification is based on what was successfully loaded into Flexpa's data store, including resources derived from EOBs for payer endpoints.

CARIN BB Core Profiles

No information

Other USCDI V1 Profiles

Payers primarily return claims via ExplanationOfBenefit. Flexpa derives Encounter, Condition, Procedure, and Provenance from EOBs — see Claims to Clinical. Some payers also return clinical resources directly; absence here doesn't mean unavailable.

No information