Written and maintained by CASRAI Editorial Board
Last updated
Greenway Health is a United States ambulatory healthcare information technology vendor that develops electronic health record (EHR vs. EMR), practice management, and revenue cycle management platforms for outpatient medical groups, specialty clinics, and Federally Qualified Health Centers (FQHCs). Formed through the consolidation of Greenway Medical Technologies, Vitera Healthcare Solutions, and SuccessEHS, Greenway Health supports two flagship ONC-certified ambulatory EHR platforms—Greenway Intergy and Greenway Prime Suite—connected through standardized HL7 FHIR R4 APIs, the Greenway Marketplace API (GAPI), and nationwide health information exchange networks.
What Is the Difference Between Greenway Intergy and Greenway Prime Suite?
Because Greenway Health evolved from merging distinct ambulatory EHR product lines, clinical informaticists, health IT integrators, and practice administrators must distinguish between Greenway Intergy and Greenway Prime Suite when scoping database extractions, clinical trial site integrations, or API connections:
| Architectural Dimension | Greenway Intergy | Greenway Prime Suite |
|---|---|---|
| Product Heritage | Originated from Medical Manager / Sage / Vitera Healthcare Solutions | Originated from Greenway Medical Technologies |
| Underlying Database & Stack | Relational Progress OpenEdge database architecture with integrated practice management | Microsoft .NET and Microsoft SQL Server relational database architecture |
| Primary Clinical & Organizational Fit | Multi-specialty group practices, enterprise ambulatory networks, and Federally Qualified Health Centers (FQHCs) | Independent single- and multi-specialty physician practices (primary care, OB/GYN, pediatrics, internal medicine) |
| Regulatory & Public Health Reporting | Includes native HRSA Uniform Data System (UDS) reporting, sliding-fee schedules, and encounter splitting for FQHCs and Community Health Centers | Integrated MIPS / Medicare Quality Payment Program (QPP) clinical quality measure (eCQM) tracking and specialty clinical templates |
| Deployment Options | Greenway cloud-hosted environment or customer-managed deployment | Greenway cloud-hosted environment or customer-managed deployment |
How Do Developers Integrate with Greenway Health APIs? (HL7 FHIR R4 vs. GAPI)
Third-party clinical applications, ambient AI scribes, patient intake platforms, and multi-site clinical research registries integrate with Greenway Intergy and Prime Suite through two complementary API layers:
1. ONC Cures Act Certified HL7 FHIR R4 APIs
To comply with the ONC 21st Century Cures Act certification criterion 45 CFR § 170.315(g)(10) (Standardized API for Patient and Population Services), both Greenway Intergy and Greenway Prime Suite expose standards-based HL7 FHIR Release 4 (R4.0.1) endpoints profiled to the US Core Implementation Guide and United States Core Data for Interoperability (USCDI):
- SMART on FHIR Authentication: Supports OAuth 2.0 and OpenID Connect authorization flows for both standalone patient-facing apps and clinician-facing EHR launch contexts.
- Standardized Clinical Resource Read Access: Exposes read/search operations across USCDI clinical resources including
Patient,AllergyIntolerance,CarePlan,CareTeam,Condition,Device,DiagnosticReport,DocumentReference,Encounter,Goal,Immunization,MedicationRequest,Observation(vital signs, laboratory results, smoking status),Procedure, andProvenance. - FHIR Bulk Data Access (
$export): Supports asynchronous system-to-system population queries using Backend Services OAuth 2.0 (client_credentialswith JSON Web Token assertion), returning Newline Delimited JSON (.ndjson) files for population health analytics, payer data exchange, and clinical registry cohort extraction.
2. Greenway API (GAPI) and Marketplace Partner Integration
Because the baseline ONC FHIR R4 specification primarily governs standardized clinical read and export operations, developers requiring bidirectional operational write-back—such as creating or updating appointment slots, posting patient demographic updates, submitting digital check-in forms, writing discrete clinical progress note sections, or posting financial charges—integrate through the proprietary Greenway API (GAPI) program. GAPI provides RESTful and web-service endpoints that abstract the underlying schema differences between Intergy’s Progress OpenEdge database and Prime Suite’s SQL Server tables.
How Greenway Health Connects Ambulatory Practices to Carequality and CommonWell
Outpatient clinics frequently care for patients whose acute hospital admissions, emergency department visits, and specialist consultations occur in external health systems running different EHRs. Greenway Health resolves cross-organization clinical data exchange through two interconnected national Health Information Exchange (HIE) frameworks:
- CommonWell Health Alliance (commonwellalliance.org): As a founding member of the CommonWell Health Alliance, Greenway embeds CommonWell services directly into Intergy and Prime Suite workflows. When a patient is registered, CommonWell’s cross-enterprise Master Patient Index (EMPI) and Record Locator Service (RLS) automatically identify matching patient records across participating outpatient clinics, acute-care hospitals, and post-acute facilities nationwide.
- The CommonWell–Carequality Interoperability Bridge: Through CommonWell’s nationwide connection to the Carequality Interoperability Framework, clinicians using Greenway Intergy or Prime Suite can execute federated query-based document exchange (IHE Cross-Community Access / XCA) with health systems on Epic, eClinicalWorks, athenahealth, and Oracle Health. Incoming Consolidated Clinical Document Architecture (C-CDA) continuity-of-care summaries are parsed inside the Greenway chart so clinicians can reconcile external medications, allergies, and problem lists directly into the local patient record.
Research Practice and Real-World Data (RWD) Considerations
When biomedical informaticists extract longitudinal ambulatory real-world data (RWD) from Greenway Health practices—particularly in community-based primary care networks and HRSA-funded Federally Qualified Health Centers—three data management practices improve cohort fidelity:
- Harmonizing Intergy and Prime Suite Schemas: Multi-site networks spanning both Intergy and Prime Suite practices should extract standardized FHIR R4
$exportNDJSON bundles or C-CDA documents before transforming records into common research schemas such as OMOP CDM or PCORnet CDM, rather than writing separate SQL queries against OpenEdge and SQL Server tables. - Leveraging FQHC Uniform Data System (UDS) Social Determinants: Intergy installations at FQHCs systematically capture structured social determinants of health (SDoH), housing status, federal poverty level (FPL) tiers, and primary language variables required for annual HRSA UDS reporting, providing high-completeness socioeconomic covariates for health equity research.
