Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document FHIR server and repository while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
FHIR R4 4.0.1
FHIR R4 defines resources, RESTful interactions, data types, terminology bindings, conformance artifacts, security considerations, and exchange patterns. It includes the first normative FHIR content and remains the base for major U.S. implementation guides. Buyers must distinguish base R4 support from support for a named profile or implementation guide. FHIR R4 does not establish production connectivity, semantic quality, authorization design, or conformity for a particular product.
FHIR R5 5.0.0
FHIR R5 is HL7's current overall published release and adds substantial content beyond R4. HL7 labels the release trial use while individual artifacts can have their own standards status. The newest overall release and the dominant regulatory implementation baseline are not the same thing. Buyers need an explicit version-transition plan rather than treating current FHIR as one undifferentiated feature.
US Core 9.0.0
US Core defines U.S. FHIR profiles, interactions, search expectations, and guidance for exchanging common clinical data. Version 9.0.0 remains based on FHIR R4 and incorporates current USCDI-oriented development. US Core version support is more decision-useful than a generic FHIR statement. Current publication, regulatory adoption, and voluntary SVAP availability must be recorded separately.
HTI-5 Proposed Rule
HTI-5 proposes changes to the ONC Certification Program, information-blocking regulations, and standards-based API foundations. Its provisions remain proposals as of the seed date. The proposal can inform scenario planning, but vendors and buyers must not describe proposed removals or new API provisions as settled current requirements.
CMS-9115-F
CMS-9115-F requires specified payers to maintain FHIR-based Patient Access APIs for claims, encounter, cost, and maintained clinical data, and establishes other interoperability and provider-notification provisions. The rule created a durable payer API market while leaving data scope, patient authorization, app privacy, testing, operations, and implementation-guide choices as material implementation decisions.
Bulk Data Access 3.0.0
The Bulk Data Access guide defines asynchronous export patterns for large FHIR datasets, including system-, patient-, and group-level workflows and associated authorization considerations. Bulk export adds job orchestration, file security, filtering, deletion, monitoring, performance, and downstream stewardship requirements that are not answered by a synchronous FHIR API demo.
Operating domains
Standards version and conformance control
Risk that organizations treat a standard as a timeless feature, combine incompatible versions or profiles, misstate certification or conformance, and release interfaces without reproducible evidence for the exact artifacts in use.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should FHIR server and repository produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
HL7 publishes US Core 9.0.0 — FHIR platform and integration claims should identify both the base FHIR release and the exact US Core guide version, supported profiles, tests, and production status.