Skip to main content

Independent Health’s Interoperability API Developer Information

What we are providing:

Independent Health has adopted and developed a set of Fast Healthcare Interoperability Resources (FHIR) API resources that deliver standardized data formats to registered application developers.

Independent Health’s Interoperability (FHIR) API Developer Registration provides third-party application developers with access to detailed documentation, registration services, and other developer services related to application programming interfaces (“APIs”) provided by Independent Health or one of its partners.

Independent Health has implemented the FHIR API’s and resources associated with those API’s based on:

The above implementations are based on HL7 FHIR Release 4 framework in pursuant to the Centers for Medicare & Medicaid Services (“CMS”) Interoperability and Patient Access Final Rule (CMS-9115-F).


Our API Functionality:

The Patient Access API allows FHIR compliant application developers to retrieve our current member’s data (with Member approval). Retrieving this data will require the registration of the developer’s application or service through our developer’s registration process.

What Type of Data is Available:

Patient Access API

  • Data related to Explanation of Benefits (EOBs from adjudicated claims)
  • Encounter data from providers
  • Formulary data
  • Clinical data, if available

Provider Directory API

  • Provider and pharmacy directory information

Requesting Access:

Patient Access API

  1. Complete this access form and email to
  2. Upon approval, the required OAuth Client ID and endpoint information will be provided by Independent Health.

Provider Directory API


Patient Access

  • Registration questions:
  • Developer Support (FHIR API questions/communication, APIs, and Swagger Files):
    Phone: 1-877-895-4724
    • If you are having an issue related to one of the APIs, please capture as much information as possible before contacting us.
    • For developer support, please email Developer Support. Remember, do not send member’s personal health information through email. Member specific claims issues or authentication issues (e.g., forgot username or password) will not be resolved through the developer support mailbox.
    • The email to Developer Support should contain the following information:
      • A description of the issue
      • The API being accessed
      • The FHIR resource API(s) that you are having an issue with
      • The response code and error message
      • The time, including time zone, and date of the error
      • Your contact information

Provider Directory


* We are supporting the use case anticipated queries ( for STU v1.0.1.  NOT the STU v1.1.0 anticipated queries (