Stream: IG creation
Topic: Capability Statement and Profiling
Saul Kravitz (Jan 05 2022 at 19:00):
I have a naive question about the Capabilities required in a Capability statement and how/whether they are inherited when profiling. I think I've asked this before, but my search couldn't find the Q&A.
The USCore Organization (for example) requires as a SHALL that the name and address search parameters be implemented.
1) Do all use cases that incorporate the US Core Organization implicitly require that these search parameters be supported? What if it is a use case where there are no search parameters (exchange of bundles that incorporate Organizations)?
2) If these search parameters do make sense in the use case for the profile, is the IG expected to state the requirement in its capability statement? Or is the requirement implicit?
John Moehrke (Jan 05 2022 at 19:04):
in theory, theory and practice are the same... in practice they are not.....
Note that there are different kinds of CapabilityStatement. The one found in an IG is defining requirements of that IG, hence it is a 'requirements' kind. A specific product or instance would publish what they actually implement, which should be inclusive of the requirements, likely more than required, but might be different.
Lloyd McKenzie (Jan 05 2022 at 19:11):
USCore Organization (StructureDefinition) doesn't require any search parameters. It's the CapabilityStatement that sets the requirement. If a derived IG doesn't make use of the US Core CapabilityStatement, then none of the CapabilityStatement rules apply.
Eric Haas (Jan 05 2022 at 20:24):
US Core documents this topics in the latest published version (4.0.0): http://build.fhir.org/ig/HL7/US-Core/conformance-expectations.html
Last updated: Apr 12 2022 at 19:14 UTC
