Stream: implementers
Topic: parameters in domain resources
Emre Avsar (Sep 21 2017 at 06:20):
Hi guys, I'm having some very specific information which should be attached to a Domain Resource, so that they can be exchanged. There is no matching other Resource so that I thought about attaching a Parameters resource to my extended Domain Resource. Is this a good practice? Or should I create a whole new DomainResource for this purpose and attach this to my extended Resource?
Lloyd McKenzie (Sep 21 2017 at 06:27):
If you need a "custom" resource, look at Basic. It's intended to be used for this purpose. Parameters resource instances aren't persisted or queriable.
Emre Avsar (Sep 21 2017 at 06:30):
OK. We're using FHIR only for the API, inside we have our domain specific model. We don't have any necessity to query parameters, but I read this line in the doc, which made me think about using it or not:
This special resource type is used to represent the operation request and response.
(https://www.hl7.org/fhir/parameters.html)
Seem's like not related to Resources, but more into Operation Input-Output without any Resource. Am I correct with this assumption?
Lloyd McKenzie (Sep 21 2017 at 06:33):
Yes. That's what Parameters is for.
Emre Avsar (Sep 21 2017 at 06:44):
Alright. Thanks. I'll follow the Basic resource (didn't realized that it existed until now).
Last updated: Apr 12 2022 at 19:14 UTC
