Which resource types are supported by the Terminology Service's READ and SEARCH interactions?

Which resource types are supported by the Terminology Service's READ and SEARCH interactions?

• A. CodeSystem, ValueSet, ConceptMap
• B. ConformanceResource, ValueSet, ConceptMap
• C. CodeSystem, CodeSystemVersion, ConceptMap
• D. ValueSet, CodeSystem, StructureDefinition

Answer: (A)

The important idea here is that the Terminology Service's READ and SEARCH operations are designed for the core terminology content resources: CodeSystem, ValueSet, and ConceptMap. You can read a specific CodeSystem, ValueSet, or ConceptMap by its identity or URL, and you can search for these resources using standard parameters (like URL, status, date, etc.) to locate the terminology data you need. ConformanceResource (a descriptor of server capabilities) isn’t a terminology content resource, and CodeSystemVersion isn’t a separate resource in modern FHIR (version is a property of CodeSystem). StructureDefinition is about defining data structures or profiles, not terminology content. So the resources that MAKE SENSE for terminology read/search are CodeSystem, ValueSet, and ConceptMap.

The important idea here is that the Terminology Service's READ and SEARCH operations are designed for the core terminology content resources: CodeSystem, ValueSet, and ConceptMap. You can read a specific CodeSystem, ValueSet, or ConceptMap by its identity or URL, and you can search for these resources using standard parameters (like URL, status, date, etc.) to locate the terminology data you need.

ConformanceResource (a descriptor of server capabilities) isn’t a terminology content resource, and CodeSystemVersion isn’t a separate resource in modern FHIR (version is a property of CodeSystem). StructureDefinition is about defining data structures or profiles, not terminology content. So the resources that MAKE SENSE for terminology read/search are CodeSystem, ValueSet, and ConceptMap.