NextGen Enterprise API
Section 170.404 Regulatory Information
Terms of Service
Partner Program fees vary according to the terms specific to each available API Partner Program; the available Partner Programs and their associated fees are detailed below:
Patient Access API Program: No Fees
Open Access Partner Program(solely for current NextGen Healthcare clients): No Fees
Open API Consumer & Premier Partner Programs:
Variable Fees are potentially based on any of the following criteria that are applicable given the intentions & needs of the developer’s application:
The scope of data access requested1.
Version of NextGen Healthcare Enterprise® EHR in use by a given NextGen Healthcare client and the corresponding ONC Health IT Certification (e.g. 2015 Edition Cures Update).
The volume of data required.
Application data transaction types, i.e. if the application will have “read-only” vs. “read and write” capabilities when integrated with NextGen Healthcare Client databases.
1Fees may or may not be charged based on the categorization of data elements needed, such as USCDIv1, EHI not included in USCDIv1, and non-EHI.
Available Value-Added Services:
Developer Assistance (beyond normal support infrastructure provided to all API Partners):
Rates vary according to time and depth of technical assistance required.
Participation in the Patient Access API Program is only available to developers whose applications will solely utilize NextGen Patient Access APIs.
Participation in the Open Access Partner Program is limited solely to current NextGen Healthcare clients who have licensed NextGen Enterprise® EHR v. 5.9.0 or higher and have established a mutually executed API Terms of Service Agreement (with Open Access Partner terms) with NextGen Healthcare. This can be initiated by completing the online API Onboarding form.
Participation in the Open API Consumer Partner Program or the Premier Partner Program is limited to 3rd Party Vendors and requires execution of an API Terms of Service Agreement specifying Open API Consumer Partner Program or Premier Partner Program terms. This can be initiated by completing the online API Onboarding form.
While a Global Service Account (“GSA”) is currently the only possible Enterprise API authentication model, User-level authentication will become available in Fall 2021.
GSA authentication enables use of most Enterprise USCDI API Routes, but some routes that require provider-level auditing are not available under GSA. The routes prohibited under GSA will become available via the User-level authentication capabilities coming in Fall 2021. Please refer to the “Enterprise GSA Routes” tab of the NGE API Data Details Grid(.xlsx) for specifics.
There are slight differences between supported NGE versions (v5.9.0+) in the API response data for certain USCDI data elements. Please refer to the “Enterprise API, C-CDA, HL7” tab of the NGE API Data Details Grid(.xlsx) for specifics.
Patient Access APIs
Specifics regarding Patient Access API support for USCDI Data Categories are available in the “Patient API” tab of the NGE API Data Details Grid(.xlsx).
Clients of NextGen Healthcare eligible to develop an API app via the Open Access Partner Program are expected to utilize their existing non-production NextGen Enterprise® EHR environment(s) for application QA testing & validation prior to production deployment.
Registration Process Requirements
Excepting developers who elect to participate in the Patient Access API Program, all other developers interested in becoming API Partners must initiate engagement with NextGen Healthcare by completing the online API Onboarding form.
Developers who complete the API Onboarding form will receive an email with details & next steps, including instructions on how to self-register at the NextGen API Developer Portal.
Note: Developer Portal registration is a required step needed for optional Sandbox Testing and for apps to establish production integrations with NextGen Healthcare client systems.
Developer Portal registration is not needed to access regulatorily required API technical & business documentation.
The NextGen API Developer Portal includes extensive guidance information in the API Hub section, including a structured Getting Started guide, Wiki/FAQ content, and sandbox testing capabilities for both NextGen Patient Access APIs & NextGen Enterprise APIs.
Requirements for Patient Access API Application Deployment:
Developers creating an application powered by NextGen Patient Access APIs may proceed to production deployment to NextGen clients at their own discretion once they have completed development and have thoroughly tested their application using the test patient credentials provided in both the API Developer Portal and in the NextGen Patient Access API Authentication Guide.
Prior to going to production, NextGen requests each Patient Access API developer:
Notify NextGen (via APIpartners@nextgen.com) of their intention to begin support of production integrations of their application;
Provide NextGen (via APIpartners@nextgen.com) with detailed requirements that individual NextGen Healthcare client practices must satisfy before their patients are able to utilize the Patient Access API application.
Requirements for Enterprise API Application Deployment:
Developers creating an application powered by NextGen Enterprise APIs may only proceed to Beta Testing with NextGen Healthcare clients when each of the following requirements have been satisfied:
The developer has requested and correctly configured their application entry in the NextGen Developer Portal according to the guidance information provided in the Developer Portal;
NextGen has approved the application entry request (which results in activation of the application credentials necessary for OAuth2 authentication);
The developer has become a NextGen API Partner (via a mutually executed API Terms of Service Agreement between their organization and NextGen Healthcare);
The API Partner has completed initial application development using the sandbox testing capabilities provided via the API Developer Portal;
The API Partner has completed all applicable Pre-Beta requirements, including submission of a detailed route list for their application (needed for Non-USCDI data access only), verification of creation of a Beta Test Plan (optional) and any requisite client-facing documentation (optional);
NextGen has received confirmation from a minimum of one (1) Beta Clients via communication directly from the client providing the following:
The Beta Client’s confirmation that they have entered into an agreement with the Enterprise API application developer allowing the developer’s app to access their NextGen Test database.
The Beta client’s consent and readiness to participate as a Beta Site for the API Partner’s application.
The above client confirmation will result in NextGen providing the developer (via encrypted email) with the unique Test Environment client identifier(s) needed for the developer’s app to securely integrate with the client test database.
In order for a developer to proceed to integrate their Enterprise API application with the Beta Client’s Production database, the Client must communicate directly to NextGen (via APIpartners@nextgen.com) their approval for the app to integrate with their Production Environment.
The above client confirmation will result in NextGen providing the developer (via encrypted email) with the unique Production Environment client identifier(s) needed for the developer’s app to securely integrate with the client production database.
Developers creating an application powered by NextGen Enterprise APIs may declare their application to be Generally Available (optional) and proceed to engage NextGen Healthcare clients at large when each of the following requirements have been satisfied (optional but recommended):
NextGen has received (via email sent directly from the Beta Client to firstname.lastname@example.org) sign-off approval that the app is working as designed to their satisfaction.
NextGen approves the API Partner application’s release from Beta and declares the API Partner’s application to be Generally Available (optional).
Open Access Partner Program (NextGen Healthcare Clients Only)
Our Open Access Partner Program is designed especially for clients that want to develop their API application for their own use. There is no fee to participate in the development phase or the deployment phase. If an API application developed by a NextGen Healthcare client is deemed beneficial to other NextGen Healthcare clients, members are offered the option to move toward the Premier Partner Program to release the application to the NextGen Healthcare community.
Open API Consumer Partner Program
The Open API Consumer Partner program allows vendors to develop & distribute their application to NextGen Healthcare clients. There is a fee for app distribution as detailed in the preceding Fees section of this page. Open API Consumer Partners can develop on our platform and license their app to NextGen Healthcare clients, but their app will not be featured on the API Marketplace or demonstrated at User Group Meetings.
Premier Partner Program
The NextGen Healthcare Premier Partner program is a full-service development platform that provides all the tools and documentation you need to develop and launch an API app for the NextGen Healthcare community. There is no charge to develop your API application or use our platform. There is a fee for app distribution as detailed in the preceding Fees section of this page. Premier Partners have the option to feature their app in the API Marketplace and may have the opportunity to demonstrate their app at NextGen Healthcare User Group Meetings. Our goal remains to bring innovative applications to our client base that will reduce workflow burdens while improving practice efficiency, patient care, and outcomes.
Clients & 3rd Party Vendors interested in becoming a NextGen API Partner should browse the available API Partner Programs. Select the “Learn More” link beneath the most applicable program description on the Partner Program page to proceed to the API Onboarding Form and apply for Partner Program participation.
Developers will receive an email with further information and guidance following submission of the API Onboarding Form.
Terms of Service
There are multiple versions of the API Terms of Service; the terms applicable to a developer will depend upon multiple factors, including scope of data needs, partner program type, etc.