Stream: committers
Topic: OperationDefinition invariant bug?
Brian Postlethwaite (Jul 01 2019 at 03:15):
The normative OperationDefinition has invariant opd-3 which prevents the use of the profile for specifying the profile of the resource type that is included, rather than referenced.
Or is that what the extension http://hl7.org/fhir/StructureDefinition/operationdefinition-profile is intended to provide?
(so StructureDefinition get's the 2 properties, however OperationDefinition uses the extension instead?)
Brian Postlethwaite (Jul 01 2019 at 03:15):
I take it the validator's should know about this one too when processing their rules.
Brian Postlethwaite (Jul 01 2019 at 03:16):
Discovered this when trying to define my internal profile for the Patient $match operation where we are explicitly defining the properties that we MUST have for the operation to work on our end.
Grahame Grieve (Jul 03 2019 at 23:23):
yes the extension. what do you think that the validator should know about ?
Brian Postlethwaite (Jul 04 2019 at 02:24):
It should validate the inline resource against the profile defined by that extension.
Brian Postlethwaite (Jul 04 2019 at 02:26):
Then again, that's the role of the operation processing not the validator, so ok. Nothing specific.
Grahame Grieve (Jul 04 2019 at 08:46):
well, we could extend the validator to be able to validate parameters against operation definitions. it can't do that right now
Last updated: Apr 12 2022 at 19:14 UTC
