How to integrate with Veradigm
This page lists what Veradigm publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.veradigm.com/.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| Allscripts ED | 8.1 | Retired | 2015-10-22 | CHP-028362 |
| Allscripts Enterprise EHR | 11.4.1 (CQM Phase 4) | Retired | 2014-03-20 | CHP-022208 |
| Allscripts Enterprise EHR (Complete) | 11.4.1 | Retired | 2013-05-02 | CHP-019380 |
| Allscripts Enterprise EHR (Modular) | 11.4.1 | Retired | 2013-05-02 | CHP-019379 |
| Allscripts ePrescribe | 2016.1 | Retired | 2016-06-16 | 14.04.04.2891.Alls.IN.01.0.160616 |
| AllScripts FollowMyHealth® | 22 | Withdrawn by Developer | 2022-09-19 | 15.04.04.2891.Alls.22.05.1.220919 |
| Allscripts MyWay EHR | v10.1 | Retired | 2012-05-24 | CHP-008738 |
| Allscripts MyWay EHR (Complete) | v12.0 | Retired | 2012-07-19 | CHP-009067 |
| Allscripts MyWay EHR (Modular) | v12.0 | Retired | 2012-07-19 | CHP-009068 |
| Allscripts PeakPractice | 5.5 | Retired | 2010-10-29 | CHP-007432 |
| Allscripts Professional EHR | 21.4 | Withdrawn by Developer | 2022-01-28 | 15.04.04.2891.Alls.PR.07.0.220128 |
| Allscripts Professional EHR (Modular) | 12.0 | Retired | 2013-07-11 | CHP-019643 |
| Allscripts TouchWorks EHR (Complete) | 11.5 | Retired | 2014-11-13 | CHP-024766 |
| Allscripts TouchWorks EHR (Modular) | 11.5 | Retired | 2014-11-13 | CHP-024765 |
| Avenel | 1.1 | Withdrawn by Developer | 2019-10-03 | 15.04.04.2891.Aven.01.01.1.191003 |
| Enterprise EHR Modular | 11.2.0.496 | Retired | 2011-07-14 | CHP-008026 |
| ePrescribe | 26 | Active | 2026-07-07 | 15.04.04.2891.ePre.26.03.1.260707 |
| FollowMyHealth Mobile Patient Experience | 4.3 | Withdrawn by Developer | 2020-07-08 | 15.04.04.2891.Foll.04.01.0.200708 |
| FollowMyHealth® Universal Health Record | 17 | Withdrawn by Developer | 2017-05-30 | 15.04.04.2891.Foll.17.00.1.170530 |
| FusionFx Patient Portal | 5.3.3 | Retired | 2018-05-09 | 14.07.04.2891.Fusi.53.01.1.180509 |
| Paragon® for Hospitals | 12.1 | Retired | 2018-10-10 | 14.04.04.2891.Para.12.01.0.181010 |
| Paragon® for Hospitals 2014 Certified EHR | 14.1 | Retired | 2018-10-10 | 14.04.04.2891.Para.14.01.0.181010 |
| Sunrise Acute Care Module Set | 5.5 FP1 | Retired | 2010-12-21 | CHP-006464 |
| Sunrise Ambulatory Care Module Set | 5.5 | Retired | 2010-12-21 | CHP-007987 |
| Sunrise Emergency Care | 5.5 FP1 | Retired | 2010-12-21 | CHP-006467 |
| Sunrise Emergency Care Module Set | 5.5 FP1 | Retired | 2010-12-21 | CHP-006466 |
| Sunrise Patient Portal and Sunrise Acute Care EHR | Sunrise Patient Portal Version 5.5 and Sunrise Acute Care EHR Version 5.5 | Retired | 2010-12-21 | CHP-007990 |
| Sunrise Patient Portal and Sunrise Ambulatory Care EHR | Sunrise Patient Portal Version 5.5 and Sunrise Ambulatory Care EHR Version 5.5 | Retired | 2010-12-21 | CHP-007985 |
| Veradigm EHR | 26 | Active | 2025-12-31 | 15.04.04.2891.Vera.26.14.1.251231 |
| Veradigm ePrescribe | 3.7 | Active | 2026-09-21 | 15.04.04.2891.ePre.37.04.1.260921 |
| Veradigm FollowMyHealth® | 2026 | Active | 2026-03-09 | 15.04.04.2891.VFMH.26.09.1.260309 |
| Veradigm View | 1 | Withdrawn by Developer | 2025-09-09 | 15.04.04.2891.View.01.02.1.250909 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://developer.veradigm.com/
- Application Access - Patient Selection (170.315 (g)(7)): https://developer.veradigm.com/
- Application Access - All Data Request (170.315 (g)(9)): https://developer.veradigm.com/
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://api.veradigmview.com/assets/static_files/ServiceBaseURLs.json, https://open.platform.veradigm.com/fhirendpoints, https://open.platform.veradigm.com/fhirendpoints/download/R4?endpointFilter=Patient.
ONC Lantern tracks 4018 FHIR endpoints for Veradigm. Reported FHIR versions: 4.0.1 (3660), 1.0.2 (96).
How to integrate
- Read the (g)(10) documentation above. ONC criterion 170.315(g)(10) requires a standardized FHIR API for patient and population services.
- Register your application with the vendor, as its documentation describes.
- Authorize with SMART App Launch, or with SMART Backend Services for system-to-system access.
- Find the practice's FHIR base URL in the service base URL list.
- Plan for the gaps. (g)(10) certifies read access to USCDI data. Scheduling, charges, claims and write-back need vendor-specific APIs or another route.