Selecting clinical software in 2026 involves specific priorities that shift compared to previous years. FHIR-first has changed the calculus.
Priority 1: FHIR API completeness. Does the vendor expose the FHIR API surface your integrations need? Verify with Inferno conformance testing, not marketing claims.
**Priority 2: SMART on FHIR support.** SMART launch is universal expected in 2026. Custom auth is a red flag.
Priority 3: US Core conformance. US Core profiles conformance is baseline. Verify version alignment.
Priority 4: Bulk data export. Bulk Data IG $export is required for CMS-0057.
Priority 5: Terminology binding depth. SNOMED CT, LOINC, RxNorm coverage. Terminology drift is where compliance fails.
Priority 6: Vendor roadmap alignment. Ability to keep pace with regulatory changes (CMS updates, ONC certifications).
Priority 7: Third-party ecosystem access. Growing SMART app marketplace.
Evaluation framework
| Priority | Weight | Verification |
|---|---|---|
| FHIR completeness | High | Inferno tests |
| SMART support | High | Live launch demo |
| US Core conformance | High | Inferno tests |
| Bulk data | Medium | Load test |
| Terminology | Medium | Version + update cadence |
| Roadmap | Medium | Reference customers |
| Ecosystem | Low | Marketplace size |
Red flags
1. Custom auth instead of SMART. 2. Unversioned US Core conformance. 3. Sync-only bulk export. 4. Manual terminology updates. 5. Custom profile requirements for third-party integration.
Reference-check questions
1. How long did it take to reach production? 2. What CMS-0057 compliance level? 3. Any Inferno test failures? 4. How does vendor handle profile version updates? 5. What ongoing support quality?
Purchasing timeline
1. RFP: 2-4 weeks. 2. Demo phase: 4-8 weeks. 3. Reference checks: 2-4 weeks. 4. Contract negotiation: 4-8 weeks. 5. Implementation: 6-24 months.
Clinical software selection in 2026 is FHIR-centric. The seven priorities above cover most decision factors.
