Home / Technical research / ModMed

Platform research

ModMed technical research.

Available source documents and verified published identifiers, with source-file and page citations. Product versions, components, release labels, and compatibility requirements retain their original context.

Sources reviewed

01 / Source documents

The materials behind the research.

Links open the publisher’s source. The document type and review status distinguish full files from web pages or landing pages.

  1. Technical document · HTML

    ModMed synapSYS and API Portal

    Reviewed web snapshot

    Public Certified FHIR and proprietary API documentation. Certified FHIR covers EMA and gGastro; proprietary API is for EMA and ModMed Practice Management, and does not support gGastro.

    View original source : ModMed synapSYS and API Portal (opens in a new tab)
    Reviewed source file03_ModMed/Technical_Documents/ModMed_synapSYS_and_API_Portal_e660adc5_web_snapshot.html
  2. Technical document · PDF

    ModMed EMA EHI Export Data Dictionary for Single Patient Export

    Reviewed PDF

    96-page data dictionary for interpreting EMA single-patient EHI exports; also see vendor ONC page for bulk export dictionary.

    View original source : ModMed EMA EHI Export Data Dictionary for Single Patient Export (opens in a new tab)
    Reviewed source file03_ModMed/Technical_Documents/ModMed_EMA_EHI_Export_Data_Dictionary_for_Single_Patient_Export_62d1662c.pdf

    96 PDF pages. Citations use physical PDF pages.

  3. Technical document · HTML

    gGastro Hardware Compatibility and Technical Documents

    Reviewed web snapshot

    gGastro-specific compatibility requirements and links to desktop client release notes; separate from EMA.

    View original source : gGastro Hardware Compatibility and Technical Documents (opens in a new tab)
    Reviewed source file03_ModMed/Technical_Documents/gGastro_Hardware_Compatibility_and_Technical_Documents_5b85beee_web_snapshot.html
  4. White paper landing page · HTML

    White Paper: EMA Security

    Reviewed landing page; full paper listed separately

    Vendor whitepaper, published 2022-06-01, explains EMA information security. Landing page contains downloadable four-page PDF. Applies to EMA, not automatically to gGastro.

    View original source : White Paper: EMA Security (opens in a new tab)
    Reviewed source file03_ModMed/Whitepapers/White_Paper_EMA_Security_9a2beab1_web_snapshot.html
  5. White paper · PDF

    White Paper: EMA Security - Download PDF

    Reviewed PDF

    Public file linked from https://www.modmed.com/resources/educational-guides/ehr-security-whitepaper

    View original source : White Paper: EMA Security - Download PDF (opens in a new tab)
    Reviewed source file03_ModMed/Whitepapers/White_Paper_EMA_Security_-_Download_PDF_ed21bf63.pdf

    4 PDF pages. Citations use physical PDF pages.

  6. Release / certification document · PDF

    EMA 7 certificate of Health IT compliance

    Reviewed PDF

    2022-11-29 (certificate date; PDF posted under 2026/01) Certificate identifies 'EMA 7' and 'Date Certified: 11/29/2022'.

    View original source : EMA 7 certificate of Health IT compliance (opens in a new tab)
    Reviewed source file03_ModMed/Release_and_Version_Documents/EMA_7_e7f5f455.pdf

    1 PDF pages. Citations use physical PDF pages.

  7. Release / certification document · HTML

    gGastro v6.2 and Desktop Client v1.2.0.9 - Historical Release Notice

    Reviewed web snapshot

    2023-12-26 notice; scheduled cloud update 2024-01-07 Official archived notice announces gGastro v.6.2 and says release notes are available on ModMed Communities for gGastro. Same notice names Desktop Client v1.2.0.9, an ancillary client version distinct from the gGastro EHR version. Vendor marks this historical notice EXPIRED.

    View original source : gGastro v6.2 and Desktop Client v1.2.0.9 - Historical Release Notice (opens in a new tab)
    Reviewed source file03_ModMed/Release_and_Version_Documents/gGastro_v.6.2_51fa1429_web_snapshot.html
  8. Technical document · HTML

    ModMed API Getting Started Guide

    Reviewed web snapshot

    Public integration guide describes EMA Proprietary API, Certified FHIR API, scope and supported systems.

    View original source : ModMed API Getting Started Guide (opens in a new tab)
    Reviewed source file03_ModMed/Technical_Documents/ModMed_API_Getting_Started_Guide_c52af0d1_web_snapshot.html
  9. Technical document · HTML

    ModMed Certified FHIR API App Types and Scopes Guide

    Reviewed web snapshot

    Public guide to app types, OAuth scopes and resource permissions.

    View original source : ModMed Certified FHIR API App Types and Scopes Guide (opens in a new tab)
    Reviewed source file03_ModMed/Technical_Documents/ModMed_Certified_FHIR_API_App_Types_and_Scopes_Guide_9c6638d2_web_snapshot.html

02 / Verified identifiers

Published labels, with their source context.

These findings establish what appears in the reviewed documents. They do not establish the latest release or any organization’s installed version, build, or applicable hotfix.

  1. Certified product version

    7

    ModMed EMA

    Certificate explicitly names EMA 7. URL posting date and certificate-template revision are not release dates.

    Source citation

    EMA 7 certificate of Health IT compliance — PDF p. 1; printed Unnumbered certificate (opens in a new tab)

    Section: Certificate of Health IT Compliance - This is to certify that

    Date context: Date Certified 11/29/2022; PDF posted at a 2026/01 vendor URL

    Source file: 03_ModMed/Release_and_Version_Documents/EMA_7_e7f5f455.pdf

    Source document details
  2. Historical product release version

    6.2

    ModMed gGastro

    gGastro EHR release version, separate from EMA. This historical notice is not evidence of the current version.

    Source citation

    gGastro v6.2 and Desktop Client v1.2.0.9 - Historical Release Notice — Unpaginated (opens in a new tab)

    Section: Practice Action May Be Required

    Date context: Historical expired notice dated December 26, 2023; scheduled cloud upgrade January 7, 2024

    Source file: 03_ModMed/Release_and_Version_Documents/gGastro_v.6.2_51fa1429_web_snapshot.html

    Source document details
  3. Ancillary client version

    1.2.0.9

    gGastro Desktop Client

    Four-part software component version explicitly labeled Desktop Client. Not a gGastro EHR build or hotfix.

    Source citation

    gGastro v6.2 and Desktop Client v1.2.0.9 - Historical Release Notice — Unpaginated (opens in a new tab)

    Section: Desktop Client

    Date context: Historical expired notice dated December 26, 2023; scheduled cloud upgrade January 7, 2024

    Source file: 03_ModMed/Release_and_Version_Documents/gGastro_v.6.2_51fa1429_web_snapshot.html

    Source document details
  4. Product compatibility threshold

    6.1 or higher

    gGastro (Desktop Client compatibility)

    Compatibility threshold for Desktop Client 1.2.0.9; not a claim that gGastro 6.1 is current.

    Source citation

    gGastro v6.2 and Desktop Client v1.2.0.9 - Historical Release Notice — Unpaginated (opens in a new tab)

    Section: Desktop Client

    Date context: Historical notice dated December 26, 2023

    Source file: 03_ModMed/Release_and_Version_Documents/gGastro_v.6.2_51fa1429_web_snapshot.html

    Source document details

03 / Research limits

What the documents do not establish.

  • No EMA or gGastro EHR build number or hotfix number verified from the downloaded files.
  • Desktop Client 1.2.0.9 is a related client version and was not substituted as an EHR build/hotfix.
  • gGastro release notes referenced in the historical notice require ModMed Communities access; the notice itself is retained.

Page numbers refer to the physical pages in the reviewed PDF; printed page labels are shown where available. Web and JSON sources are unpaginated and cited by section. Publisher files and web pages may change after the review date. Research coverage reflects the available documents and does not imply vendor endorsement.

Assess the records in context.

Tell us the platform and the records available so we can discuss an assessment scope.

Request an assessment proposal

Paid engagements. Scope and fees agreed before review.