NextGen
Access
Section titled “Access”- Register through NextGen’s developer portal (“add an app”). One client id serves every practice; each practice supplies a site id, which goes into the token request and onto queries.
- SMART Backend Services with a JWT. The token request uses the parameter name
scopes, notscope.
Known behaviour
Section titled “Known behaviour”Backend tokens cannot search patients
Section titled “Backend tokens cannot search patients”FHIR Patient search works only with a user token from a SMART launch. With a backend token,
match patients through NextGen’s native Enterprise API person lookup (first name, last name, date of
birth), then switch back to FHIR for clinical data.
Name plus date of birth returns every match, so use the 5-digit home ZIP as a tie-breaker, and reject matches you cannot verify.
Data calls need extra headers
Section titled “Data calls need extra headers”Clinical data calls need practice, enterprise and person identifier headers (x-practice-id,
x-enterprise-id, x-person-id). The person id comes from the matched patient and must be carried
onto every next page. Send these headers to NextGen only — not from shared code that talks to
other vendors.
Bulk export requires a patient Group built by the customer.
Extraction approach
Section titled “Extraction approach”Per-patient search, starting from a patient list, with _count=100 and link.next paging.