Change record: HL7 publishes US Core 9.0.0

What changed

US Core 9.0.0 becomes the current published U.S. FHIR profile guide while remaining based on FHIR R4.

This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.

Operating consequence

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.

Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.

Capabilities to revisit

FHIR Server And Repository

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for FHIR server and repository.

FHIR Profile And Implementation-Guide Support

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for FHIR profile and implementation-guide support.

FHIR API Gateway And Orchestration

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for FHIR API gateway and orchestration.

Conformance Testing And Validation

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for conformance testing and validation.

Questions for operating teams

• Which exact population and effective date does the source establish?
• Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
• What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
• What test case would show whether the operational consequence has reached production?
• What record will close, defer, or supersede this review?

Evidence boundary

The source class is Standards development organization publication. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.