Home / Integrations / ModMed
Integration guide · United States
Point-of-care results, filed in ModMed.
Run the test in the exam room and the result lands in ModMed as a structured value against the right patient. Nothing read off a screen, nothing typed twice, no printout walked to the front desk.
ModMed provides cloud-based, specialty-specific electronic health record (EHR) and practice management software: EMA for specialties including dermatology, ophthalmology, orthopedics, ENT, urology, plastic surgery, podiatry, pain management, allergy and OB/GYN, and gGastro for gastroenterology. Its public API portal describes a Certified FHIR API on FHIR R4 with SMART on FHIR, a proprietary API for EMA and ModMed Practice Management, and HL7 options. The analyzer in the office is what usually stays unconnected. That is the manual step in between.
Two things push a specialty practice on ModMed to connect its analyzers. The first is volume: an allergy, urology, dermatology or gastroenterology practice running waived tests in the office produces results that belong in the visit note before the physician finishes it, and typing them in afterwards is where errors and delays creep in. The second is the record: recordkeeping obligations under the Clinical Laboratory Improvement Amendments (CLIA, 42 CFR Part 493) depend on test complexity, the manufacturer's instructions, state rules and any accreditation, and a result that arrives in the chart with the operator, device and quality-control status attached is the simplest way to meet whichever apply.
Catenix sits between your analyzers and ModMed. A gateway at each office, or a staff phone running Pocket Gateway, captures each result electronically the moment it is produced, over HL7, POCT1-A2, ASTM or the device's own format. The result is matched to the right patient and operator, kept separate from quality-control runs, and forwarded to ModMed through an HL7 v2 results interface, one of the HL7 options ModMed lists alongside its Certified FHIR API and proprietary API, or a supported ModMed API where the practice has enabled it. ModMed's API portal sets the terms on the ModMed side.
How it works
From bench to filed result.
More than the pipe
Connectivity is the start, not the whole product.
QC captured as it happens, Westgard rules on failures, Levey-Jennings charts drawn for you, competency against the operator who ran the test. Every analyser, one system
Chemistry, immunoassay, blood gas, haematology, molecular and urinalysis on one platform instead of one middleware per manufacturer. Pocket Gateway
A phone becomes the gateway, so testing connects even in settings without fixed network infrastructure. Built for networks
One coordinator can oversee devices, QC and operators across every site from a single screen.
Modules switch on per clinic, so you take the connectivity and governance you need now and add the rest if it earns its place. There are no per-test fees.
Questions, answered
Before you ask.
How do point-of-care results reach ModMed?
A result captured at the bench is turned into a structured message and delivered to ModMed through an HL7 v2 results interface or, where the practice has enabled it, a supported ModMed API. ModMed's API portal describes a Certified FHIR API with SMART on FHIR, a proprietary API and more traditional HL7 options for connectivity. Catenix is designed to connect over those open standards, so the value that was measured is the value filed against the right patient, with the operator and device attached.
Is Catenix integrated with ModMed?
Catenix is designed and ready to connect to ModMed over the standards it accepts. That describes connectivity built to open standards, not an affiliation with or endorsement by ModMed. Exactly what flows, and how, is confirmed with your practice during implementation.
Does this cover both EMA and gGastro?
ModMed's API portal states that its Certified FHIR API supports EMA, ModMed Practice Management, ModMed GI and gGastro, while the proprietary API is for EMA and ModMed Practice Management only, and HL7 options sit alongside both. Which route carries results into your chart depends on the product you run and what ModMed enables for your practice, and that is confirmed with you and ModMed during implementation. Catenix presents a standard result message either way and keeps its own tamper-evident record of every result.
Catenix is designed and ready to connect to the systems named on this page over open standards. That wording is deliberate: it describes connectivity built to published interfaces, not a claim of affiliation with, endorsement by, or certification from any named vendor. Product and company names are the trademarks of their respective owners and are used for identification only. What connects in your setting is confirmed during implementation. This page describes connectivity and data handling only and is not clinical advice.
See a result land in ModMed.
Bring your analyser list. We'll show the journey from bench to record, live, and start with a 15-minute call if you prefer.