Stream: implementers
Topic: Nested Parameters
Sufyan Patel (Oct 11 2018 at 10:43):
Hi, I have a requirement to perform an operation with some parameters. One of the parameter needs to be a separate Parameters resource.
My question is how this can be done in the OperationDefinition. I believe I have two options:
1. Use the profile element to point to a parameters resource
<parameter>
<name value="SearchCriteria"/>
<use id="in"/>
<min value="1"/>
<max value="1"/>
<profile> <reference value="[base URL]/Parameters"/></profile>
</parameter>
2.
Use the <part> element which references the Parameters resource and its elements.
Is there a preference?
Thanks in advance.
Yunwei Wang (Oct 11 2018 at 14:18):
I use <part>. "The parts of a nested Parameter."
BTW, I don't see <profile> element in OperationDefinition.
Lloyd McKenzie (Oct 11 2018 at 14:47):
Parameters isn't intended to be persistable - so there shouldn't ever be an external reference to point at. The expectation is to use 'part'.
Last updated: Apr 12 2022 at 19:14 UTC