Stream: committers
Topic: Specify Operation parameters at Resource and Instance levels
Gino Canessa (Jun 02 2020 at 17:18):
I'm working on the $status operation for Subscription, and am wondering if it is possible to restrict the parameters by usage type. Specifically, at the Resource level, there is a parameter for ids, while that parameter is invalid at the Instance level.
Other spreadsheets I found just include text saying it isn't valid at one/the other level - is there anything more, or just add the note and move on?
Lloyd McKenzie (Jun 02 2020 at 17:39):
Nothing more computable available at the moment
Lloyd McKenzie (Jun 02 2020 at 17:40):
I guess you could define distinct OperationDefinition instances - one for each mode
Gino Canessa (Jun 02 2020 at 17:46):
Thanks Lloyd. I thought about it, but they need to have different names (the tooling doesn't allow two operations with the same name), and I don't think I want to establish a pattern for that (e.g., status-r and status-i or some such).
I've added the text for now, and will be happy to revisit later if a better option comes along.
Lloyd McKenzie (Jun 02 2020 at 17:48):
The tooling theoretically should allow the same name if the endpoints are different, but I accept that's the way things work now. You might submit a change request?
Gino Canessa (Jun 02 2020 at 17:49):
Sure, I can file that.
Gino Canessa (Jun 02 2020 at 17:57):
Created FHIR#27761
Last updated: Apr 12 2022 at 19:14 UTC
