Terms of Usage for PacificSource APIs
In support of CMS Interoperability requirements, PacificSource supports third-party developer access to public and patient access API endpoints.
Note that any access or usage of PacificSource APIs requires and implies consent with PacificSource API Usage Terms and Conditions.
PacificSource interoperability APIs follow HL7 FHIR specifications in compliance with CMS Standards. The version of FHIR currently supported by PacificSource APIs is 4.01.
Getting started with PacificSource APIs
PacificSource interoperability APIs follow HL7 FHIR specifications in compliance with CMS Standards. The version of FHIR currently supported by PacificSource APIs is 4.01.
Learn how to search FHIR resources
More detailed informatio, including data specification and code examples for each of the FHIR resources made available by PacificSource may be found at the links below:
Resource Type | FHIR Specification |
| Member/Patient | Patient - FHIR v4.0.1 (hl7.org) |
| Coverage | Coverage - FHIR v4.0.1 (hl7.org) |
| Provider | Practitioner - FHIR v4.0.1 (hl7.org) |
| Claim/Explanation of Benefit | ExplanationOfBenefit - FHIR v4.0.1 (hl7.org) |
| Formulary | Medication - FHIR v4.0.1 (hl7.org) |
PacificSource public access APIs for provider and formulary data
PacificSource supports open access to provider and formulary data at the following URI:
The OpenAPI specification for PacificSource provider and formularly API endpoints may be found here:
PacificSource patient access APIs
PacificSource also supports appropriate developer access to APIs for member PHI at the following URL:
Developers wishing to access the PacificSource Patient Access API must register in advance to obtain an API key.
For more information, please email InteropSupport@PacificSource.com.
The OpenAPI specification for PacificSource Patient Access API endpoints may be found here: