Stream: conformance
Topic: ValueSet Expansion example
Simone Heckmann (Jun 24 2016 at 15:36):
Is this correct?
Expanding a value set that is specififed by the client (using JSON): POST [base]/ValueSet/23/$expand [other headers] { "resourceType" : "Parameters", "parameter" : [ { "name" : "valueSet", "resource" : { "resourceType" : "ValueSet", [value set details] } } ] }
I'd expect this query to go against POST [base]/ValueSet/$expand not POST [base]/ValueSet/23/$expand
http://hl7-fhir.github.io/terminology-service.html#2.5.1.3
Simone Heckmann (Jun 24 2016 at 15:37):
...I mean "correct" besides the obvious typo in "specififed" ? :D
Grahame Grieve (Jun 24 2016 at 19:57):
I think so
Simone Heckmann (Jun 24 2016 at 21:00):
But then: which ValueSet would be expanded? The one with the id 23 or the one provided in the body of the request?
Peter Jordan (Jun 25 2016 at 01:38):
That's an interesting question, @Simone Heckmann. If the ValueSet id is provided in the URL of a POST request, my server will use that as the identifier of the ValueSet, rather than any value in the _id, identifier or URL parameters supplied in the request body. It would be informative to know how other Terminology Servers handle this use case.
Grahame Grieve (Jun 25 2016 at 22:25):
oh no, i missed that bit. its not valid
Simone Heckmann (Jun 27 2016 at 08:58):
Added GF#10244
Last updated: Apr 12 2022 at 19:14 UTC