A server can support multiple FHIR versions on the same endpoint if...

Study for the Fast Healthcare Interoperability Resources (FHIR) Proficiency Test. Dive into flashcards and multiple-choice questions with hints and explanations. Prepare effectively for your exam!

Multiple Choice

A server can support multiple FHIR versions on the same endpoint if...

Explanation:
Version negotiation via the fhirVersion mime type parameter lets a single endpoint serve multiple FHIR versions. The client indicates which version it wants by including fhirVersion in the content negotiation header (for example, Accept: application/fhir+json; fhirVersion=4.0.1 or fhirVersion=5.0.0). The server can then respond with data encoded in that specific version while using the same URL, as long as it supports that version. This is why the option that uses the mime type parameter to specify the version is the correct approach. Using a single static version would prevent serving multiple versions from the same endpoint. Requiring separate endpoints per version goes against the idea of a single URL handling multiple versions. And saying it’s not possible ignores the established mechanism for version negotiation via the fhirVersion parameter.

Version negotiation via the fhirVersion mime type parameter lets a single endpoint serve multiple FHIR versions. The client indicates which version it wants by including fhirVersion in the content negotiation header (for example, Accept: application/fhir+json; fhirVersion=4.0.1 or fhirVersion=5.0.0). The server can then respond with data encoded in that specific version while using the same URL, as long as it supports that version. This is why the option that uses the mime type parameter to specify the version is the correct approach.

Using a single static version would prevent serving multiple versions from the same endpoint. Requiring separate endpoints per version goes against the idea of a single URL handling multiple versions. And saying it’s not possible ignores the established mechanism for version negotiation via the fhirVersion parameter.

More practice questions