Lab and referral results without the fax
Where results still come in on paper, n-frames builds the NextGen Connect interface that brings the HL7 messages straight in, so staff stop keying them.
A lab faxes results, someone scans them into the chart, and the practice's IT lead has heard NextGen has an API. It has several. What you can use depends on whether you run NextGen Enterprise or NextGen Office, which version, and whether the app is for your own organization or for other NextGen clients.
Building something that changes practice data means Enterprise. Office projects start from what FHIR can read.
Enterprise APIs need NextGen Enterprise 5.9.0 or later. Office APIs need NextGen Office 5.0 or later. An older version means an upgrade conversation first.
Internal apps fit the Open Access Developer Program. Apps for the wider NextGen community go through the API Distributor Program, where fees may apply depending on data scope.
The FHIR APIs read. Writing appointments, demographics or billing data back means the Enterprise APIs.
Message traffic between systems is often an interface engine job for NextGen Connect, not an API call.
Vendor apps are authorized in the NextGen API Client Portal, and a Main Client Community user has to grant that access. Find that person early.
NextGen Connect is the name many practices use for NextGen's interface engine, which NextGen's own site now calls Mirth Connect by NextGen Healthcare. It's the usual place to build an HL7 interface: lab results in, orders out, or ADT messages exchanged with a hospital. It sits beside the APIs rather than replacing them.
Claims EDI, the X12 files that go to payers and come back as remittances, normally runs through the practice management side and its clearinghouse setup. Connect can read and reshape X12 when a practice needs a custom route, such as remittance data pulled into a reporting tool.
Before any of this, it's worth looking at the NextGen API Marketplace. If a listed app already does the job, a custom build only makes sense where it stops short.
Where results still come in on paper, n-frames builds the NextGen Connect interface that brings the HL7 messages straight in, so staff stop keying them.
Billing staff exporting NextGen payment data to reconcile against QuickBooks or another accounting tool get a sync that keeps the totals current, where the Enterprise API allows.
Where an intake form sits outside NextGen's own check-in tools, it can fill in the appointment and demographic fields through the Enterprise API, where the API allows, for the front desk to confirm.
Product, version, program track and Client Portal approval come first. n-frames works through that with your NextGen contacts, then builds.
More than one. NextGen Enterprise has proprietary REST APIs with read and write access plus FHIR APIs for patient access, and NextGen Office has FHIR R4 APIs for Patient Access, SMART App Launch and Bulk FHIR. Which one fits depends on the product and version you run.
NextGen's interface engine, listed on NextGen's site today as Mirth Connect by NextGen Healthcare. Practices and health systems use it to build HL7 interfaces between NextGen and labs, hospitals or other EHRs, and it can also transform files such as X12 when a custom route is needed.
Yes, in different places. HL7 interfaces are usually built in NextGen Connect. Claims EDI normally runs through the practice management side and its clearinghouse, with Connect available for custom handling of X12 files.
Both. The NextGen API Developer Program has three tracks: Patient Access, Open Access Developer for clients' internal apps, and API Distributor for apps offered to other NextGen clients. The API Marketplace is where distributed apps are promoted.
NextGen says there's no charge to develop a Patient Access app, no fee to develop or deploy under Open Access, and no charge for development or sandboxes under the Distributor program, though fees may apply there depending on data scope. Your NextGen license itself is a separate matter.