How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Centene

Centene FHIR Patient Access API

The Centene FHIR Patient Access API lets members of Centene health plans access their clinical, financial, and formulary data through third-party applications, as required by the CMS Interoperability and Patient Access Rule.

Documentation Provider Profile APIs.io OpenAPI GitHub

Centene FHIR Patient Access API is one of 12 APIs that Centene publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include FHIR, Patient Access, and CMS Interoperability. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and a getting-started guide.

This API exposes 47 operations across 47 paths, organized into 25 resource areas, and defines 47 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://dev-int-api-gw.centene.com/fhir/v4/patientaccess.

47 operations 47 paths 47 schemas 47 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://iopc-pa.api.centene.com/iopc/pa
Authentication
HTTP Bearer
Resource Areas
25

Authentication & Security 1

Centene FHIR Patient Access API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer).

Paths & Operations 47

Across 47 paths, the API surfaces 47 operations — 47 GET. They span 25 resource areas, including metadata, CareTeam, AllergyIntolerance, Encounter, Device, Condition, DiagnosticReport, Immunization, and 17 more. Each is listed below with its method, path, parameters, and response codes.

metadata 1
GET
/metadata
CapailityStatement
getMetadata → 200
CareTeam 2
GET
/CareTeam
Search all resources of type CareTeam based on a set of criteria
searchCareTeam 3 params → 200400401403404500429501
GET
/CareTeam/{id}
Read the current state of the resource
readCareTeam 1 param → 200400401403404500429501
AllergyIntolerance 2
GET
/AllergyIntolerance
Search all resources of type AllergyIntolerance based on a set of criteria
searchAllergyIntolerance 2 params → 200400401403404500429501
GET
/AllergyIntolerance/{id}
Read the current state of the resource
readAllergyIntolerance 1 param → 200400401403404500429501
Encounter 2
GET
/Encounter
Search all resources of type Encounter based on a set of criteria
searchEncounter 5 params → 200400401403404500429501
GET
/Encounter/{id}
Read the current state of the resource
readEncounter 1 param → 200400401403404500429501
Device 2
GET
/Device
Search all resources of type Device based on a set of criteria
searchDevice 2 params → 200400401403404500429501
GET
/Device/{id}
Read the current state of the resource
readDevice 1 param → 200400401403404500429501
Condition 2
GET
/Condition
Search all resources of type Condition based on a set of criteria
searchCondition 2 params → 200400401403404500429501
GET
/Condition/{id}
Read the current state of the resource
readCondition 1 param → 200400401403404500429501
DiagnosticReport 2
GET
/DiagnosticReport
Search all resources of type DiagnosticReport based on a set of criteria
searchDiagnosticReport 5 params → 200400401403404500429501
GET
/DiagnosticReport/{id}
Read the current state of the resource
readDiagnosticReport 1 param → 200400401403404500429501
Immunization 2
GET
/Immunization
Search all resources of type Immunization based on a set of criteria
searchImmunization 2 params → 200400401403404500429501
GET
/Immunization/{id}
Read the current state of the resource
readImmunization 1 param → 200400401403404500429501
CarePlan 2
GET
/CarePlan
Search all resources of type CarePlan based on a set of criteria
searchCarePlan 3 params → 200400401403404500429501
GET
/CarePlan/{id}
Read the current state of the resource
readCarePlan 1 param → 200400401403404500429501
Goal 2
GET
/Goal
Search all resources of type Goal based on a set of criteria
searchGoal 2 params → 200400401403404500429501
GET
/Goal/{id}
Read the current state of the resource
readGoal 1 param → 200400401403404500429501
MedicationRequest 2
GET
/MedicationRequest
Search all resources of type MedicationRequest based on a set of criteria
searchMedicationRequest 5 params → 200400401403404500429501
GET
/MedicationRequest/{id}
Read the current state of the resource
readMedicationRequest 1 param → 200400401403404500429501
PractitionerRole 2
GET
/PractitionerRole
Search all resources of type PractitionerRole based on a set of criteria
searchPractitionerRole 5 params → 200400401403404500429501
GET
/PractitionerRole/{id}
Read the current state of the resource
readPractitionerRole 2 params → 200400401403404500429501
Location 2
GET
/Location
Search all resources of type Location based on a set of criteria
searchLocation 7 params → 200400401403404500429501
GET
/Location/{id}
Read the current state of the resource
readLocation 2 params → 200400401403404500429501
Procedure 2
GET
/Procedure
Search all resources of type Procedure based on a set of criteria
searchProcedure 4 params → 200400401403404500429501
GET
/Procedure/{id}
Read the current state of the resource
readProcedure 2 params → 200400401403404500429501
Observation 2
GET
/Observation
Search all resources of type Observation based on a set of criteria
searchObservation 5 params → 200400401403404500429501
GET
/Observation/{id}
Read the current state of the resource
readObservation 1 param → 200400401403404500429501
Coverage 2
GET
/Coverage
Search all resources of type Coverage based on a set of criteria
searchCoverage 3 params → 200400401403404500429501
GET
/Coverage/{id}
Read the current state of the resource
readCoverage 2 params → 200400401403404500429501
Practitioner 2
GET
/Practitioner
Search all resources of type Practitioner based on a set of criteria
searchPractitioner 6 params → 200400401403404500429501
GET
/Practitioner/{id}
Read the current state of the resource
readPractitioner 2 params → 200400401403404500429501
Patient 2
GET
/Patient
Search all resources of type Patient based on a set of criteria
searchPatient 6 params → 200400401403404500429501
GET
/Patient/{id}
Read the current state of the resource
readPatient 1 param → 200400401403404500429501
ExplanationOfBenefit 2
GET
/ExplanationOfBenefit
Search all resources of type ExplanationOfBenefit based on a set of criteria
searchExplanationOfBenefit 10 params → 200400401403404500429501
GET
/ExplanationOfBenefit/{id}
Read the current state of the resource
readExplanationOfBenefit 2 params → 200400401403404500429501
Organization 2
GET
/Organization
Search all resources of type Organization based on a set of criteria
searchOrganization 8 params → 200400401403404500429501
GET
/Organization/{id}
Read the current state of the resource
readOrganization 2 params → 200400401403404500429501
List 2
GET
/List
Search all resources of type List based on a set of criteria
searchList 5 params → 200400401403404500429501
GET
/List/{id}
Read the current state of the resource
readList 1 param → 200400401403404500429501
MedicationKnowledge 2
GET
/MedicationKnowledge
Search all resources of type MedicationKnowledge based on a set of criteria
searchMedicationKnowledge 6 params → 200400401403404500429501
GET
/MedicationKnowledge/{id}
Read the current state of the resource
readMedicationKnowledge 1 param → 200400401403404500429501
Medication 1
GET
/Medication/{id}
Read the current state of the resource
readMedication 1 param → 200400401403404500429501
Provenance 1
GET
/Provenance/{id}
Read the current state of the resource
readProvenance 1 param → 200400401403404500429501
QuestionnaireResponse 2
GET
/QuestionnaireResponse
Search all resources of type QuestionnaireResponse based on a set of criteria
searchQuestionnaireResponse 2 params → 200400401403404500429501
GET
/QuestionnaireResponse/{id}
Read the current state of the resource
readQuestionnaireResponse 1 param → 200400401403404500429501

Schemas 47

The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are ExplanationOfBenefit (21 properties), Coverage (18 properties), PractitionerRole (17 properties), MedicationRequest (13 properties). Each schema is shown below with its type and property counts.

OperationOutcome
object
QuestionnaireResponse
object
6 properties 6 required
QuestionnaireResponse-search
object
7 properties 7 required
CareTeam
object
8 properties 8 required
CareTeam-search
object
7 properties 7 required
AllergyIntolerance
object
11 properties 11 required
AllergyIntolerance-search
object
7 properties 7 required
Encounter
object
6 properties 6 required
Encounter-search
object
7 properties 7 required
Device
object
11 properties 11 required
Device-search
object
7 properties 7 required
Condition
object
10 properties 10 required
Condition-search
object
7 properties 7 required
DiagnosticReport
object
10 properties 10 required
DiagnosticReport-search
object
7 properties 7 required
Immunization
object
9 properties 9 required
Immunization-search
object
7 properties 7 required
CarePlan
object
8 properties 8 required
CarePlan-search
object
7 properties 7 required
Goal
object
8 properties 8 required
Goal-search
object
7 properties 7 required
MedicationRequest
object
13 properties 13 required
MedicationRequest-search
object
7 properties 7 required
PractitionerRole
object
17 properties 17 required
PractitionerRole-search
object
7 properties 7 required
Location
object
12 properties 12 required
Location-search
object
7 properties 7 required
Procedure
object
7 properties 7 required
Procedure-search
object
7 properties 7 required
Observation
object
11 properties 11 required
Observation-search
object
7 properties 7 required
Coverage
object
18 properties 18 required
Coverage-search
object
7 properties 7 required
Practitioner
object
7 properties 7 required
Practitioner-search
object
7 properties 7 required
Patient
object
13 properties 13 required
Patient-search
object
7 properties 7 required
ExplanationOfBenefit
object
21 properties 21 required
ExplanationOfBenefit-search
object
7 properties 7 required
Organization
object
8 properties 8 required
Organization-search
object
7 properties 7 required
List-read
object
9 properties 9 required
List-search
object
7 properties 7 required
MedicationKnowledge-read
object
5 properties 5 required
MedicationKnowledge-search
object
7 properties 7 required
Medication
object
5 properties 5 required
Provenance
object
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

centene-fhir-patient-access-openapi.json Raw ↑

Other APIs Centene publishes across the network.

Centene FHIR Provider Directory API
AE Profile APIs.io
Centene Provider RTR - FHIR PDEX Directory API
AE Profile APIs.io
Centene Provider RTR Demographics API
AE Profile APIs.io
Centene Provider Carrier Entity Search (PCES) API
AE Profile APIs.io
Centene Provider Carrier Entity Search (PCES) Extract API
AE Profile APIs.io
Centene Provider Search Suggest API
AE Profile APIs.io
Centene Product Mapping V2 API
AE Profile APIs.io
Centene LWC EDI CORE Real Time Service
AE Profile APIs.io
Centene CCM Communication API
AE Profile APIs.io
Centene CCM SMS User Response Webhook
AE Profile APIs.io
Centene Healow Health API
AE Profile APIs.io
#FHIR#Patient Access#CMS Interoperability
← Back to C APIs
API Details
ID
centene:centene-fhir-patient-access
Base URL
https://iopc-pa.api.centene.com/iopc/pa
Docs
https://partners.centene.com/apiDetail/2718669d-6e2e-42b5-8c90-0a82f13a30ba
Provider
Centene
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=centene-fhir-patient-access&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/centene-fhir-patient-access"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Centene FHIR Patient Access API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.