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-OnlyRESTful API endpoints that providepatient datausing the FHIR data standard (DSTU & R4).

RESTful APIs (500+ routes) enablingReadandWritetransactions acrossan expansive array of EHR datausing 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 byindividual patientsof NextGen Practices.

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

Functional Scope

Patient Access API Apps let patients of a NextGen Practiceaccess their own personal health data在实践的次世代企业系统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 ofclinical, administrative, and other functions.

Developer Program Info

Program details for Patient Access API Developers are provided in thePatient Access APIs and Regulatory Compliancesection ofwww.www.orderpulsa.com/partner-program.

Program options for Clients or 3rdParty Vendors developing Enterprise or FHIR API Apps intended for NGE Users include theOpen Access DeveloperandAPI Distributorprograms described atwww.www.orderpulsa.com/developer-program.

Technical Documentation

FHIR API Documentation for Patient Access is publicly available viawww.www.orderpulsa.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 availablehere.

APIs for NextGen®Office 5.0+:

YourHealthFile®Patient APIs

  • FHIR-based (R3、R4)NextGen Office YourHealthFile®Patient Access APIsare for developers creating Apps intended to empower patients with access to their own personal health data in a NextGen Office practice.
  • The NextGen Office® section of theOnline Patient Access API Documentation for App Developerspage contains technical information, a link to route-level API documentation, and a link to the Developer Guide forNextGen Office YourHealthFile® Patient Access APIs.

NextGen Office FHIR APIs

  • The FHIR-based (R4)NextGen Office FHIR APIsis 21st Century Cures compliant and enables interoperability for providers by allowing vendors of their choice to obtain USCDIv1 data.
  • Navigate to theNextGen Office Regulatory Information pagefor 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.
  • NextGen® Population Health Solution
    • NextGen®Population Health Solution 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.