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

NextGen Healthcare Coverage API

https://hl7.org/fhir/R4/coverage.html

NextGen Healthcare Coverage API is one of 35 APIs that NextGen Healthcare publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Coverage. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://fhir.meditouchehr.com/api/.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://fhir.nextgen.com/nge/prod/fhir-api-r4/fhir/r4/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

NextGen Healthcare Coverage API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OauthSecurity) using the authorizationCode flow, exposing 4 scopes. By default, every request must be authenticated.

  • OauthSecurity — Access code based oauth authentication

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Coverage 2

https://hl7.org/fhir/R4/coverage.html

GET
/fhir/r4/Coverage/{id}
Fetches a Coverage by id. FHIR Resource: Coverage Coverage resource represents insurance coverage details for a patient
1 param → 200404401
GET
/fhir/r4/Coverage
Fetches a bundled resource containing Coverage data based on the provided parameters. - If patient is provided, a bundle containing the coverages is returned. FHIR Resource: Coverage Coverage resourc…
1 param → 200404401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Coverage (12 properties), CoverageBundled (7 properties). Each schema is shown below with its type and property counts.

Coverage
object
12 properties 5 required
CoverageBundled
object
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nextgen-healthcare-coverage-api-openapi.yml Raw ↑

Other APIs NextGen Healthcare publishes across the network.

NextGen Enterprise Patient Access FHIR API
NextGen Enterprise API
NextGen Office FHIR R3 API
NextGen Office Patient FHIR API
NextGen Office SMART App Launch FHIR API
NextGen Office Bulk FHIR API
NextGen Mirth Connect Integration Engine API
NextGen Healthcare Allergy Intolerance API
NextGen Healthcare Care Plan API
NextGen Healthcare Care Team API
NextGen Healthcare CCDA API
NextGen Healthcare Condition API
Where this information came from

This is an independent, third-party profile of NextGen Healthcare Coverage 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.