Which statement best describes FHIR's architectural approach?

• A. FHIR is designed around modular resources that can be accessed via RESTful APIs.
• B. FHIR replaces all existing standards with a single protocol.
• C. FHIR uses only batch processing for data exchange.
• D. FHIR is limited to imaging data.

Answer: (A)

FHIR’s architecture centers on modular resources that represent discrete healthcare data elements and can be combined in flexible ways. These resources are exposed through RESTful APIs, meaning you interact with them using standard HTTP methods (GET, POST, PUT, DELETE) and can address each resource via a stable, discoverable URL. This combination makes it easy to mix and match different data types—patients, observations, medications, encounters, and more—across systems in a scalable, interoperable way. The RESTful approach also supports powerful search capabilities and predictable, stateless interactions, which helps diverse systems integrate smoothly.

It’s important to note what FHIR is not. It doesn’t aim to replace every existing standard with a single protocol; instead, it emphasizes interoperability by using a common, modern web-based approach while still aligning with other standards where appropriate. It isn’t limited to batch processing; while bulk operations exist, the primary architecture supports real-time, on-demand data exchange. And it isn’t restricted to imaging data—the resource model covers a wide range of healthcare information, not just images.

So describing FHIR as modular resources accessed via RESTful APIs best captures how its architecture is designed to enable flexible, scalable, and interoperable data sharing across healthcare systems.