Stream: fhir/infrastructure-wg
Topic: GF#14299
Grahame Grieve (Jul 02 2018 at 09:44):
GF#14299 - I do not understand the disposition of this task. What does it mean to have 'characteristics that will be part of this CapabilityStatement'? @Lloyd McKenzie @Richard Ettema ?
Lloyd McKenzie (Jul 02 2018 at 10:52):
If the imported statement declares support for operations, resources, documents, etc., those declarations are treated as if they appeared on the importing statement
Grahame Grieve (Jul 05 2018 at 06:47):
so how is that different to instantiates?
Lloyd McKenzie (Jul 05 2018 at 13:30):
Instantiates is a declaration "I am conformant with x". Imports is a mechanism for distributed maintenance where you borrow some of your characteristics from another CapabilityStatement.
Grahame Grieve (Jul 05 2018 at 19:01):
no, I'm not actually seeing the difference
Grahame Grieve (Jul 19 2018 at 12:22):
ping on this... @Lloyd McKenzie @Richard Ettema @Ewout Kramer @John Moehrke
John Moehrke (Jul 19 2018 at 12:32):
The need that I expressed in the CR is that when one is writing an Implementation Guide, it is not uncommon to use within that Implementation Guide previously written Actors (CapabilityStatement -- requirements kind) or content (StructureDefinition). I can today say that my new StructueDefinition is based on some previously published StructueDefinition. When I do this, I don't re-state all those constraints, I get them by importing. I simply want the same thing for CapabilityStatement. As IG get bigger, it will be very important to build on previous IG as building blocks. I don't understand the disposition of my CR either.
Lloyd McKenzie (Jul 19 2018 at 14:09):
"Instantiates" is a declaration of conformance. It doesn't impact the content of the CapabilityStatement. The capabilities (REST, messaging and otherwise) are only those directly declared in the instance. "Imports" means that you read the capability statement as if it includes all of the capabilities in the current instance as well as all of those in the imported instance.
Lloyd McKenzie (Jul 19 2018 at 14:11):
If you instantiate, that doesn't mean that you do everything in the instantiated profile. Only that what you do is a valid constraint on the instantiated profile. So you'd have to do all of the SHALL resources, operations, messages, etc. But you might only do some of the SHOULD and MAY resources, operations, messages. If you "import", you're grabbing everything in the base CapabilityStatement.
Lloyd McKenzie (Jul 19 2018 at 14:11):
Is that clearer?
Grahame Grieve (Jul 19 2018 at 20:12):
yes
Grahame Grieve (Jul 19 2018 at 20:13):
in what way does 'import' not imply 'instantiate'?
Lloyd McKenzie (Jul 19 2018 at 20:54):
Import implies instantiate. Instantiate does not imply import.
Lloyd McKenzie (Jul 19 2018 at 20:55):
And if you're importing, it's generally in a use-case where "declaring conformance with" isn't really relevant. You're just trying to re-use stuff.
Grahame Grieve (Jul 20 2018 at 21:22):
ok thanks. applied
Last updated: Apr 12 2022 at 19:14 UTC
