CMS-0057-F looked like a build candidate when the rule first dropped in 2024. The reference implementations were public, the IGs were stable, and the FHIR engineering market was hot. By 2026 the calculus has shifted. The vendor market matured, deployment patterns formalized, and the cost of building in-house turned out to be higher than most teams budgeted. Mid-size payers running the build-versus-buy analysis in 2026 land more often on buy than on build, but the decision is not automatic. This comparison lays out the trade-offs honestly for payer compliance reading on this site.
What Buying Actually Includes in 2026
A typical buy decision for CMS-0057-F bundles four things. The platform itself (FHIR data layer, the four APIs, the ePA stack, security, audit). Pre-built IG conformance for US Core, CARIN BB, PDex, Da Vinci. Ongoing IG maintenance as IGs evolve. Vendor-owned conformance certification for Inferno and similar suites.
The flat-fee vendors (Smile Digital Health is the canonical example with documented $97k annual pricing across dev/staging/prod with maintenance and support) make the total clear up front. PMPM vendors (1upHealth) tie cost to member count, which fits smaller plans cleanly. Per-transaction vendors require careful volume modeling.
What Building Actually Costs in 2026
A from-scratch build of CMS-0057-F by an in-house engineering team typically requires 8 to 15 engineers over 12 to 18 months. Specialized FHIR engineering talent is expensive (fully loaded $250k-$400k per engineer per year in US markets). The build alone is $3 to $6 million in engineering cost before infrastructure, conformance certification, ongoing maintenance, and the cost of slipping the deadline.
The WEDI February 2026 survey estimates broadly: 28 percent of payers expect compliance to cost $1 to $5 million, 25 percent expect more than $5 million. The high-end numbers correlate with payers building substantial portions in-house.
Where Buy Wins
Buy wins on three dimensions. First, deadline reliability: the 3 to 6 month vendor go-live paths actually exist and have reference customers. A from-scratch build that has to hit January 1, 2027 starting in mid-2026 is a tight timeline. Second, total cost: even enterprise-tier vendor contracts are cheaper than the loaded cost of an in-house engineering team building the same scope. Third, IG maintenance: vendors that own ongoing IG conformance handle the recurring work that often surprises in-house teams.
For most mid-size payers without an existing FHIR engineering team, buy is the obvious choice.
Where Build Wins
Build wins in narrow circumstances. Payers with an existing FHIR engineering team (often unicorn payers with a software-engineering-led culture) can extend in-house work cleanly. Payers with highly unusual data models that resist standard FHIR profile mappings sometimes find vendor implementations too rigid. Payers with strategic reasons to control the entire stack (rare but real) accept the cost.
Build also wins for payers that are building beyond CMS-0057-F into broader FHIR-driven products. If the FHIR platform becomes a product line, the build cost amortizes across more than just compliance.
The Hybrid Path Most Mid-Market Payers Actually Take
A common pattern in practice is to buy the core FHIR platform (Smile, 1upHealth, InterSystems, Edifecs) and build only the layers that genuinely need customization. The vendor handles the four APIs, ePA stack, security, and IG conformance. The payer builds the integration to their specific claims platform, the member-facing experience inside their portal, and any unique attribution or consent logic.
This pattern keeps the cost predictable, the deadline achievable, and the customization where it actually adds value.
How to Frame the Decision
The honest framing for a mid-size payer in 2026 is that buying the CMS-0057-F platform is the default, and building is justified only when the payer can articulate a specific reason the vendor market does not serve. Vague preferences for in-house control are usually not strong enough reasons. Specific architectural requirements (unusual data models, strategic platform extension, existing engineering capacity) sometimes are.
For the specific vendors that offer 3 to 6 month go-live commitments under a buy decision, the Top 5 vendors with 3-6 month CMS-0057-F go-live timelines covers the leaders. For the cost drivers that determine whether buy is actually cheaper than build, the 5 hidden costs of CMS-0057-F compliance covers the budget detail.