Which artifacts can include the fhirVersion element?

Which artifacts can include the fhirVersion element?

• A. CapabilityStatement
• B. StructureDefinition
• C. ImplementationGuide
• D. All of the above

Answer: (D)

The fhirVersion element is used to indicate which versions of FHIR an artifact is compatible with. This kind of version compatibility information is relevant across multiple artifact types, not just one. In a CapabilityStatement, listing fhirVersion shows the FHIR versions that the server supports for its capabilities, helping clients choose the correct interaction and validation path. In a StructureDefinition, fhirVersion communicates which FHIR versions the profile (structure, constraints, or extension) is designed for, guiding validators and tooling about version-specific semantics. In an ImplementationGuide, fhirVersion indicates which FHIR versions the guide applies to, so implementers know which versioned content the guide is intended to support. Because each of these artifacts can carry version compatibility information, all of the above can include the fhirVersion element.

The fhirVersion element is used to indicate which versions of FHIR an artifact is compatible with. This kind of version compatibility information is relevant across multiple artifact types, not just one.

In a CapabilityStatement, listing fhirVersion shows the FHIR versions that the server supports for its capabilities, helping clients choose the correct interaction and validation path.

In a StructureDefinition, fhirVersion communicates which FHIR versions the profile (structure, constraints, or extension) is designed for, guiding validators and tooling about version-specific semantics.

In an ImplementationGuide, fhirVersion indicates which FHIR versions the guide applies to, so implementers know which versioned content the guide is intended to support.

Because each of these artifacts can carry version compatibility information, all of the above can include the fhirVersion element.