Stream: implementers
Topic: OperationDefinition and Parameters
Sufyan Patel (Aug 24 2017 at 14:55):
Hi, Just need some clarification on how the Parameters resource links with the OperationDefinition resource.
Am I correct in thinking that an operation can use the parameters defined within the OperationDefinition and also any from the Parameters resource?
Bryn Rhodes (Aug 24 2017 at 16:48):
An implementation would have to have access to the contents of the Parameters resource, so yes, but I don't know that it would be best practice to rely on something like that.
Lloyd McKenzie (Aug 24 2017 at 19:24):
The Parameters resource is used to send parameters when invoking an operation. OperationDefinition = definition; Parameters = instance
Haseeb (Aug 28 2017 at 13:31):
Hi all, I am trying to use $everything on Patient resource like:
http://localhost:4080/Patient/1/$everything
I am getting error codes "not supported" "not handled" when I run it on my local vonk instance. But when I try to execute same operation in smarthealth sandbox, its working: https://sb-fhir-stu3.smarthealthit.org/smartstu3/open/Patient/1/$everything
My understanding is that $everything is a resource operation and should either work in both or not work in either. Or operations are allowed explicitly by FHIR server instance?
Lloyd McKenzie (Aug 28 2017 at 15:18):
Each server decides what it will support vs. not. That includes what resources, compartments, search parameters, operations, messages and documents. Not all of the reference servers support everything and production servers will often support even less as they will be focused on particular business cases and the capabilities of legacy persistence and communications layers.
Ewout Kramer (Sep 26 2017 at 11:25):
Better late than never ;-) Vonk does not support $everything yet. But @Christiaan Knaap might be able to tell you about the Vonk roadmap and where $everything lives on it....
Christiaan Knaap (Sep 26 2017 at 13:19):
$everything is not high on the list, since we have not had many requests for implementing it. Anyone requiring a feature before considering Vonk is very welcome to report that here or via email.
That being said, we will include the CompartmentDefinitions somewhere in the next months, and that brings $everything a lot closer.
Christiaan Knaap (Sep 26 2017 at 13:21):
As for supported operations @Haseeb : You may want to check the CapabilityStatement. Every server can give you one on the /metadata endpoint and it contains everything the server supports.
Andrew A Zander (Jun 17 2019 at 03:57):
I have an R4 profile of the Parameters "resource" that i wish to use to express a constraint on the input parameters to an extended operation. (see https://www.hl7.org/fhir/operationdefinition-definitions.html#OperationDefinition.inputProfile)
In order to test my Parameters profile i create an example Parameters instance and use the java validator.
Validation works as expected for Parameters instances except when i create one with a parameter of type Bundle. In these cases I get the validation error:
Error @ Parameters.parameter.resource (line 8, col19) : entry.request mandatory for batch/transaction/history, otherwise prohibited [entry.all(request.exists() = ((.type = 'batch') or (.type = 'transaction') or (.type = 'history')))]
Error @ Parameters.parameter.resource (line 8, col19) : entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited [entry.all(response.exists() = ((.type = 'batch-response') or (.type = 'transaction-response') or (.type = 'history')))]
My example Parameters has a parameter of type Bundle - the Bundle has a type "collection" (so this invariant should not even be checked).
Is this a known like a bug in the validator?
Grahame Grieve (Jun 17 2019 at 04:06):
it's known now - can you submit a bug report https://github.com/hapifhir/org.hl7.fhir.core/issues with an attachment that demonstrates the problem
Last updated: Apr 12 2022 at 19:14 UTC
