Which statement about resource conformance to profiles is supported by the rules?

Which statement about resource conformance to profiles is supported by the rules?

• A. A resource can conform to a profile without ever being labeled that it conforms
• B. A resource cannot conform to a profile without being labeled
• C. A resource can only conform to a single profile at a time
• D. A resource can never claim to conform to a profile

Answer: (A)

In FHIR, whether a resource matches a profile is determined by validation against the profile’s constraints, not solely by a tag on the resource. A resource can satisfy the rules defined in a profile and be considered conformant even if it never includes a declaration in its metadata that it adheres to that profile. The meta.profile field is a helpful way to advertise which profiles a resource conforms to, but it isn’t the only way conformance is recognized. This matters because profiles define constraints on elements, cardinalities, value sets, and other rules. A validator can check a resource against those constraints and confirm conformity regardless of whether the resource explicitly labels itself as conformant. That said, including the profile URLs in metadata improves discoverability and interoperability, letting parsers and systems quickly know which profiles apply. Resources can also conform to multiple profiles if they declare multiple profile URLs, so the idea that a resource can only conform to a single profile isn’t accurate. Similarly, it’s not true that a resource can never claim to conform; labeling is common and recommended to signal conformance.

In FHIR, whether a resource matches a profile is determined by validation against the profile’s constraints, not solely by a tag on the resource. A resource can satisfy the rules defined in a profile and be considered conformant even if it never includes a declaration in its metadata that it adheres to that profile. The meta.profile field is a helpful way to advertise which profiles a resource conforms to, but it isn’t the only way conformance is recognized.

This matters because profiles define constraints on elements, cardinalities, value sets, and other rules. A validator can check a resource against those constraints and confirm conformity regardless of whether the resource explicitly labels itself as conformant. That said, including the profile URLs in metadata improves discoverability and interoperability, letting parsers and systems quickly know which profiles apply. Resources can also conform to multiple profiles if they declare multiple profile URLs, so the idea that a resource can only conform to a single profile isn’t accurate. Similarly, it’s not true that a resource can never claim to conform; labeling is common and recommended to signal conformance.