Greenway Intergy is an ambulatory electronic health record and practice management platform developed by Greenway Health. The vendor describes it as a unified solution for modern healthcare practices, combining clinical documentation, financial operations, and specialty-focused workflows. Intergy is also positioned as the foundation for Greenway's newer Novare platform, which the company markets as an AI-enabled evolution of the Intergy EHR. For developers and interoperability teams, Greenway provides both a standards-based FHIR R4 API and a proprietary Greenway API for accessing clinical and financial data. [1][4][6]

Product Positioning and Intended Settings

Greenway Health markets Intergy Suite as a combined EHR and advanced practice management solution for ambulatory practices. The vendor's brochure states that Intergy is built with specialty-focused features, customizable workflows, and integration capabilities intended to support patient care, efficiency, and financial performance. A separate Intergy EHR brochure describes the product as clinician-friendly and patient-centric, with specialty-specific personalization that adapts to existing workflows. [4][7]

The Intergy product page positions the system as having long supported ambulatory practices with integrated clinical, financial, and operational workflows. Greenway Health also presents Novare as the next evolution of Intergy EHR, describing it as AI-powered and cloud-native. The vendor's marketing materials contrast structured workflows in Intergy with AI-driven automation in Novare, including ambient documentation, insurance verification, and coding assistance. [6]

Interoperability APIs and Developer Access

Greenway Health's Developer Platform supports two APIs for Intergy and Prime Suite. The FHIR API is standards-based and uses a REST model, while the Greenway API is proprietary with separate data structures for each EHR product. The FHIR API currently supports read operations only, according to the developer documentation. The Greenway API supports reads and writes across clinical and financial data elements. [1]

Authentication for the FHIR API uses the SMART-on-FHIR standard with OAuth2. Patients and EHR users authenticate to production endpoints using Greenway Identity credentials. The developer documentation notes that PKCE implementation is mandatory for all SMART on FHIR applications as part of HTI-1 regulatory updates. A public sandbox was described as coming soon in the getting started guide, but the FAQ states that no sandbox environment is currently available. [1][3][5]

Backend Service Access Workflow for Developers

For developers registering Backend Service SMART on FHIR applications, Greenway Health documents a multi-step access provisioning process. The developer must provide the Intergy License or GID, the relevant Practice IDs or names, whether confidential data access is required, and a site contact who can confirm access. Greenway Health then contacts the site contact to obtain written permission for the application. If the site does not reply or declines permission, Greenway Health cannot proceed. [5]

Once permission is granted, Greenway Health coordinates with internal teams using the provided information. After completion, both the site and the developer are notified that access has been provisioned. For applications already registered that need access to another client, developers can email FHIR support with the same information. The FAQ also notes that the FHIR ecosystem does not currently support writeback functionality. [5]

FHIR Resource Coverage and API Mechanics

The Greenway FHIR R4 API exposes a defined set of resource types through GET operations. Documented resources include AllergyIntolerance, CarePlan, CareTeam, Condition, Coverage, DiagnosticReport, DocumentReference, Encounter, Immunization, MedicationRequest, Observation, Patient, Practitioner, Procedure, and others. The reference documentation lists both collection-level and by-ID retrieval endpoints for these resources, along with a Generate CCD operation under DocumentReference. [3]

The developer documentation states that Greenway's FHIR API provides a subset of FHIR resources compliant with 21st Century Cures Act requirements, with additional resources planned over time. The API enforces payload size limits of 5 MB for individual resources, binary data, and bundle or batch requests. Pagination is supported through a next link in searchset bundles, and the _count query parameter limits records per page, with values above 100 returning a validation error. [1][5]

FHIR Services Onboarding and Client Requirements

Greenway clients must opt in to FHIR Services through a defined process. The practice administrator first checks Information Service Requests on MyGreenway to avoid duplicate submissions. If no active request exists, the practice submits an opt-in form through records.greenwayhealth.com using MyGreenway login credentials. For Intergy sites, the Site ID is the Intergy License number. [2]

Greenway Health states that Intergy or Prime Suite systems must be on a minimum version that changes annually to opt into FHIR Services. Practices below the minimum version must update their software before onboarding. After submission, activation takes up to 15 days on average, with large practices potentially taking longer. Status updates can be requested by adding a comment to the Information Service Request, with staff generally replying within 48 business hours. [2]

Certification and Regulatory Documentation

Greenway Health publishes ONC certification information for Intergy v22. The certification document lists a certification date of August 14, 2025, with an HTI-1 update completed November 13, 2025. The certification ID is 15.04.04.2913.Inte.22.06.0.250814. The document states that the Health IT Module is compliant with ONC Certification Criteria and was certified by an ONC-ACB, while noting that certification does not represent endorsement by the U.S. Department of Health and Human Services. [8]

The certification criteria listed for Intergy v22 include computerized provider order entry for medications, demographics, family health history, implantable device list, transitions of care, clinical information reconciliation, electronic prescribing, electronic health information export, decision support interventions, authentication and access controls, auditable events, audit reports, amendments, automatic access time-out, emergency access, end-user device encryption, integrity, trusted connection, encryption of authentication credentials, multi-factor authentication, patient health information capture, transmission to immunization registries, safety-enhanced design, quality management system, accessibility-centered design, consolidated CDA creation performance, application access for patient selection and all data requests, standardized API for patient and population services, and Direct Project. The document separately lists Updox under Prime Suite v22; that entry does not establish the same dependency for Intergy. [8]