Because it creates a common platform or foundation on which a variety of different solutions are implemented, the FHIR specification is what type of specification?

• A. A data exchange specification
• B. A platform specification
• C. An implementation guide
• D. A terminology binding specification

Answer: (B)

At the heart of this question is recognizing that FHIR is a platform specification. It creates a common foundation—including reusable resource definitions, a consistent RESTful API, and a flexible data model—on which a wide variety of healthcare solutions can be built and interoperate. This platform approach means developers don’t have to reinvent the wheel for every app; they can assemble and extend the same core capabilities to fit different use cases.

Seeing it as simply a data exchange specification would miss the broader structure FHIR provides—the underlying building blocks and architecture that enable many implementations to coexist and interoperate. It’s also not just an implementation guide, which would constrain how to use FHIR in a particular context, nor a terminology binding specification, which would only define mappings from vocabularies to data elements. The defining idea is that FHIR supplies a shared platform that supports diverse solutions on a common foundation.