Home / Technical research / OmniMD
Platform research
OmniMD 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.
Technical document · PDF
OmniMD EHR OpenAPI Version 1.1
Reviewed PDF
Public vendor 9-page API reference; methods, patient-data parameters, token examples and terms. Version 1.1 is the API document/interface version, not EHR/hotfix. Document itself undated; URL upload path 2025/10 is not treated as a release date.
View original source : OmniMD EHR OpenAPI Version 1.1 (opens in a new tab)Reviewed source file
06_OmniMD/Technical_Documents/OmniMD_EHR_OpenAPI_Version_1.1_b23957eb.pdf9 PDF pages. Citations use physical PDF pages.
Technical document · PDF
OmniMD Manual
Reviewed PDF
224-page OmniMD user/training manual. Title pages do not specify edition/version/date. This is not evidence of a current deployed build or hotfix.
View original source : OmniMD Manual (opens in a new tab)Reviewed source file
06_OmniMD/Technical_Documents/OmniMD_Manual_46eff770.pdf224 PDF pages. Citations use physical PDF pages.
White paper landing page · HTML
How a unified EHR and RCM System Solve Interoperability Challenges in Healthcare
Reviewed landing page; full paper not downloaded
Vendor explicitly labels this a whitepaper; public summary/landing page, full paper requires name/email/phone form. Full paper was not reviewed. Topic is interoperability and EHR/RCM integration, not a release/hotfix reference.
View original source : How a unified EHR and RCM System Solve Interoperability Challenges in Healthcare (opens in a new tab)Reviewed source file
06_OmniMD/Whitepapers/How_a_unified_EHR_and_RCM_System_Solve_Interoperability_Challenges_in_Healthcare_62564dfa_web_snapshot.htmlRelease / certification document · HTML
OmniMD ONC transparency and costs
Reviewed web snapshot
Disclosure separately lists v18.0 certified January 10, 2022. Certification date does not establish release/patch date or latest production deployment. Certification date October 24, 2023 Product Name: OmniMD V.20; Version: 20
View original source : OmniMD ONC transparency and costs (opens in a new tab)Reviewed source file
06_OmniMD/Release_and_Version_Documents/20_eed8d833_web_snapshot.htmlRelease / certification document · PDF
OmniMD ONC mandatory disclosures and costs
Reviewed PDF
Public file linked from https://omnimd.com/onc-transparency-and-costs/
View original source : OmniMD ONC mandatory disclosures and costs (opens in a new tab)Reviewed source file
06_OmniMD/Release_and_Version_Documents/20_-_ONC_Mandatory_Disclosures_Costs_7c8f8041.pdf16 PDF pages. Citations use physical PDF pages.
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.
Certified product version
18.0
OmniMD EHR
Certified product family version; no numeric build, release date, or patch applicability established.
Source citation
OmniMD ONC mandatory disclosures and costs — PDF p. 2; printed 2 (opens in a new tab)Section: 1. OVERVIEW AND PURPOSE
Date context: 2026 copyright disclosure
Source file:
Source document details06_OmniMD/Release_and_Version_Documents/20_-_ONC_Mandatory_Disclosures_Costs_7c8f8041.pdfCertified product version
20
OmniMD EHR
Certified product family version; no numeric build, release date, or patch applicability established.
Source citation
OmniMD ONC mandatory disclosures and costs — PDF p. 2; printed 2 (opens in a new tab)Section: 1. OVERVIEW AND PURPOSE
Date context: 2026 copyright disclosure
Source file:
Source document details06_OmniMD/Release_and_Version_Documents/20_-_ONC_Mandatory_Disclosures_Costs_7c8f8041.pdf
03 / Research limits
What the documents do not establish.
- No product build number verified in downloaded files.
- No hotfix identifier verified in downloaded files.
- Old manual labels 6.0 in its document Revision History; insufficient evidence to treat it as an OmniMD software version.
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.
Paid engagements. Scope and fees agreed before review.