Public API Documentation for NextGen Healthcare Certified Health IT Solutions

Available API Categories

APIs for NextGen® Enterprise EHR (v5.9.0+):

Patient Access APIs

Available in both the FHIR DSTU2 and R4 standards, Patient Access APIs are for developers creating Apps that are intended to empower patients with access to their own personal health data in a NextGen Enterprise practice via API.

Enterprise APIs

Comprised of an extensive collection of JSON-based RESTful APIs (400+ routes), Enterprise APIs power the category of apps that are used by provider organizations and integrate with NextGen® Enterprise EHR. These apps use Enterprise APIs to add value and functionality across a variety of clinical, administrative, and other functions.

 

NextGen Patient Access APIs

(Apps for Patients)

 NextGen Enterprise & FHIR APIs

(Apps for Provider Organizations)

Technical Info & Data Standards

Read-Only RESTful API endpoints that provide patient data using the FHIR data standard (DSTU & R4).

RESTful APIs (500+ routes) enabling Read and Write transactions across an expansive array of EHR data using a proprietary NextGen JSON data standard. FHIR APIs may also be used for NGE Client-Facing applications.

User Audience

Apps powered by Patient Access APIs are used by individual patients of NextGen Practices.

Apps powered by Enterprise APIs (and FHIR -powered apps that are not for the Patient Access use case) are intended for NextGen Enterprise Users.

Functional Scope

Patient Access API Apps let patients of a NextGen Practice access their own personal health data within that Practice's NextGen Enterprise system via API using a web-based or native mobile application.

NGE user-facing apps (powered by Enterprise and/or FHIR APIs) integrate with NextGen Enterprise (5.9.0+) to add value & expand functionality for NextGen Clients across an extensive variety of clinical, administrative, and other functions.

Developer Program Info

Program details for Patient Access API Developers are provided in the Patient Access APIs and Regulatory Compliance section of www.nextgen.com/developer-program.

Program options for Clients or 3rd Party Vendors developing Enterprise or FHIR API Apps intended for NGE Users include the Open Access Developer and API Distributor programs described at www.nextgen.com/developer-program.

Technical Documentation

FHIR API Documentation for Patient Access is publicly available via www.nextgen.com/patient-access-api.

Access to full technical documentation for Enterprise APIs (and FHIR APIs for NGE user-facing apps) is provided following submission of developer details to NextGen – links on the Developer Program page lead to the appropriate API Onboarding Form. Enterprise API documentation for USCDIv1 data is available here.

APIs for NextGen® Office 5.0+:

Introduction to FHIR

  • NextGen® Office implements the R4 Version of the HL7® FHIR® standard. It is advisable to familiarize yourself with this standard by referring to the ample information provided by the HL7 organization. You can start exploring it here.
  • The NextGen Office FHIR API supports the NextGen Office EHR, and its primary purpose is to facilitate the exchange of health information included in the U.S. Core Data for Interoperability.

NextGen® Office FHIR APIs

  • The NextGen Office section of the Online FHIR API Documentation for App Developers page contains technical information, a link to routes-level API documentation, and links to the Developer Guide for NextGen Office FHIR APIs.
  • The FHIR-based (R3/R4) NextGen Office Patient Access APIs are for developers creating Apps intended to empower patients with access to their own personal health data in a NextGen Office practice.
  • The FHIR-based (R3/R4) NextGen Office Smart App Launch API is 21st Century Cures compliant and enables interoperability for providers by allowing vendors of their choice to obtain USCDIv1 data of a single patient.
  • The FHIR-based (R3/R4) NextGen Office Bulk FHIR API is 21st Century Cures compliant and enables interoperability for providers by allowing vendors of their choice to obtain USCDIv1 data for multiple patients in a group using FHIR Bulk Data Access.
  • Navigate to the NextGen Office Regulatory Information page for technical and process details.

Regulatory Information

  • NextGen® Enterprise EHR
  • NextGen® Office
  • NextGen® Direct Messaging (formerly, Mirth Mail)
    • NextGen® Direct Messaging is not certified for the certified HIT criteria relevant to patient API access (170.315 (g)(7), (g)(8), (g)(10). Accordingly, there are no API specifications to disclose.