When an implementer needs a resource concept not yet defined by HL7 concepts, or needs to convey a narrative-only construct, which FHIR resource should be used?

When an implementer needs a resource concept not yet defined by HL7 concepts, or needs to convey a narrative-only construct, which FHIR resource should be used?

• A. StructureDefinition
• B. Basic
• C. ValueSet
• D. CodeSystem

Answer: (B)

When a piece of information doesn’t map to an existing FHIR resource type, Basic serves as a flexible container for unmodeled concepts or narrative-only data. It’s designed for situations where you need to store something that HL7/FHIR doesn’t define as a standard resource—whether that’s a locally defined concept or a free-text note about a subject. You can attach a subject or author, include an identifier to label the concept, and capture narrative text or use extensions for any needed structure. This makes Basic the best fit for conveying information that isn’t yet formalized in the standard resources. StructureDefinition is about defining or constraining how resources are structured; it’s metadata for how data must be shaped, not a place to store data itself. ValueSet and CodeSystem are for coded concepts: ValueSet is a set of codes chosen for use, and CodeSystem is the repository of those codes. They’re not intended to hold arbitrary, narrative, or unstandardized data.

When a piece of information doesn’t map to an existing FHIR resource type, Basic serves as a flexible container for unmodeled concepts or narrative-only data. It’s designed for situations where you need to store something that HL7/FHIR doesn’t define as a standard resource—whether that’s a locally defined concept or a free-text note about a subject. You can attach a subject or author, include an identifier to label the concept, and capture narrative text or use extensions for any needed structure. This makes Basic the best fit for conveying information that isn’t yet formalized in the standard resources.

StructureDefinition is about defining or constraining how resources are structured; it’s metadata for how data must be shaped, not a place to store data itself. ValueSet and CodeSystem are for coded concepts: ValueSet is a set of codes chosen for use, and CodeSystem is the repository of those codes. They’re not intended to hold arbitrary, narrative, or unstandardized data.