Interoperability APIs

Alignment Healthcare’s Interoperability APIs are based on the Health Level 7® (HL7) Fast Health Plan Interoperability Resources (FHIR®) 4.0.1 standards

Health plan members can provide consent to have their data shared with third-party applications via the Patient Access API. The Provider Directory API facilitates third-party developers to connect to Health Plan provider directories.

Health Plan APIs

The following APIs are available for the following Health Plans:

  • Alignment Health Plan
  • Alignment Health Plan members can provide consent to have their data shared with third-party applications via the Patient Access API.
  • The Provider Directory API facilitates third-party developers to connect to Alignment Health Plan provider directories.

Follow these steps to register your application and obtain authorization to use Alignment Healthcare FHIR APIs.

  • To request API access, click the button below to start the registration process and submit developer/application details. You will need to select the API you wish to use.

    Note:

    • Patient Access API only supports OAuth with PKCE for Authentication
    • Provider Directory API supports web auth authentication with Client Secret

  • Once your application and security review is completed, you will be notified of successful registration, and you will receive notification that API access has been granted.

    After registering for the Provider Directory API, you will be given a Client ID and Client Secret for your application. You will need these (along with the callback URL and scope) to use during authentication.

    Note: If you fail to store your application's Client ID and Client Secret, you will have to restart the application registration process.

  • Start using the Health Plan APIs with your newly registered application.

The Patient Access API relies on the OAuth 2.0 specification and the OpenID Connect Core 1.0 standard for securing connections. The Alignment Healthcare FHIR server supports OAuth 2.0 web application authorization flow for provider and Proof Key for Code Exchange (PKCE) authorization flow for Patient Access.

Note:

  • If your application will be using the Patient Access API, you must register your application and will need to use security protocols to connect to the FHIR server
  • If your application will only be using the Provider Directory API, you need to complete the app registration process to get Client ID and Secret


Once the registration process is completed, you will receive the following information:

  • For Provider Directory API, you will receive Client ID, Client Secret, and connectivity details. You will use the Client ID and Client Secret that you received after registering your application in an exchange with the Identity Server to receive your JSON Web Token (JWT).
  • For Patient Access API, you will get Client ID and connectivity details. While connecting, you will be asked to provide credentials. If successful, your application will be granted access to patient data of the specified member.


Note: Provider Directory API is only supported with Client ID and Client Secret. You will use the Client ID and Client Secret received after registering your application in an exchange with the Identity Server to receive your JSON Web Token (JWT).

To access the Provider Directory API, please register by clicking Request API Access in the Application Registration section above or completing the Contact Us section below.

The Provider Directory API supports the FHIR-approved implementation guide and the following profiles:

Implementation Guides

Supported Profiles

Alignment Healthcare will offer the following support consistent with stated government regulations and current operational guidelines.

General support hours

General support hours are Monday through Friday, 9 a.m. to 4 p.m. Pacific Time. General support is not provided on holidays or weekends. General support hours apply to:

  • Application registration

Registration and response times

The system will accept and respond to application registration submissions from third-party application vendors within the following estimated timeframes:
Registration type Estimated response time
Provider Directory API 5 business days
Patient Access API 5 business days
Type of data Data feed timeframe
Claims 1 business day from adjudication
Encounter data 1 business day from receipt of encounter
Clinical data 1 business day from receipt of data
Provider directory 30 calendar days of a payer receiving provider directory information OR an update to provider directory information

Start the registration process by submitting developer/application details below.



For any questions or concerns regarding registering your application, please contact interoperabilitysupport@ahcusa.com.