Hospital EHR & Clinical Information Systems buyer guide
Review the wider capability model, products, evaluation criteria and procurement questions for this category.
Support SMART on FHIR or comparable app-launch patterns for embedded third-party clinical applications.
Recorded product facts are shown separately from buyer-specific recommendation scores. “Not yet verified” means evidence is incomplete; it does not mean the product lacks the capability.
| Product | Status | Confidence | Implementation | Evidence | Limitations / notes | Last verified |
|---|---|---|---|---|---|---|
AS Altera Sunrise Altera Digital Health | Supported | 100% | Not recorded | 1 source | Sunrise 25.1 documentation explicitly references SMART App Launch Implementation Guide v2 and modern interoperability support. | Sep 21, 2026 |
E Epic Epic Systems | Supported | 100% | Not recorded | 1 source | Epic supports SMART on FHIR EHR launch, standalone launch and backend services using OAuth 2.0 profiles. | Sep 21, 2026 |
IT InterSystems TrakCare InterSystems | Supported | 100% | Not recorded | 1 source | TrakCare explicitly supports HL7 FHIR and SMART on FHIR and exposes TrakCare data through APIs. | Sep 21, 2026 |
OH Oracle Health EHR Oracle | Supported | 100% | Not recorded | 1 source | Oracle Health Millennium Platform supports SMART applications, SMART App Launch and OAuth2 authorization with FHIR APIs. | Sep 21, 2026 |
ME MEDITECH Expanse MEDITECH | Partially Supported | 97% | Not recorded | 1 source | MEDITECH Greenfield Workspace provides FHIR APIs and app testing, but this source set does not establish universal SMART-on-FHIR launch support for every Expanse deployment. | Sep 21, 2026 |
Use this capability as one requirement inside the wider category evidence model. The links below are research and comparison paths, not a product recommendation.
Review the wider capability model, products, evaluation criteria and procurement questions for this category.
Understand TechSelectAI coverage, source verification and research gaps before interpreting individual capability records.
See how support status, confidence, freshness and Unknown ≠ Unsupported are handled.
Supported, conditional, unknown and not-supported states are kept distinct so missing evidence is not treated as a negative fact.
Confidence reflects the strength of the recorded evidence for this capability, not overall product quality.
A product can strongly support this capability and still be a poor overall fit due to deployment, integrations, security, region, budget or other must-haves.
TechSelectAI can evaluate this capability together with your other must-haves, integrations, deployment constraints, security requirements, region and budget.
Evaluate software for my company