Stream: hapi
Topic: Expansion in 5.3.0 is missing the ValueSet URL
Patrick Werner (Mar 24 2021 at 11:40):
We are using VS expansions in hapi like this:
[serverBase]/ValueSet/$expand?url=http://molit.eu/fhir/ValueSet/uicc-stage
Patrick Werner (Mar 24 2021 at 11:42):
with hapi 5.2.0 these expansions looked like this:
{
"resourceType": "ValueSet",
"status": "active",
"compose": {
"include": [ {
"valueSet": [ "http://molit.eu/fhir/ValueSet/uicc-stage" ]
} ]
},
"expansion": {
Patrick Werner (Mar 24 2021 at 11:43):
hapi 5.2.0 used compose.include.valueSet to transport the VS canonical url (which seemed a little bit funky)
Patrick Werner (Mar 24 2021 at 11:44):
now with hapi 5.3.0 this element isnt't populated anymore. I would propose to use ValueSet.url to transport the canonical of the VS which was expanded.
Patrick Werner (Mar 24 2021 at 11:46):
Knowing which expansion belongs to which VS is very important in the use-case of doing expansions in transaction bundles.
Patrick Werner (Mar 25 2021 at 11:09):
https://github.com/hapifhir/hapi-fhir/issues/2502
Patrick Werner (Dec 12 2021 at 21:46):
just created a PR to address this issue: https://github.com/hapifhir/hapi-fhir/pull/3241
Patrick Werner (Jan 12 2022 at 11:20):
could this please be reviewed/approved?
Patrick Werner (Jan 21 2022 at 21:08):
push. Could this be approved please?
Michael Lawley (Jan 24 2022 at 09:43):
ValueSet.expansion.parameter would be the normal place to include this information (with name = the ValueSet URI
Patrick Werner (Jan 24 2022 at 10:00):
@Michael Lawley i don't think that is correct. Looking at: http://hl7.org/fhir/r4/valueset.html "The canonical URL for the expansion is the same as the value set it was expanded from".
And also have a look at the example in the spec: http://hl7.org/fhir/r4/valueset-example-expansion.json.html
Michael Lawley (Jan 24 2022 at 10:46):
@Patrick Werner you are correct -- I was confused by the strange approach shown for hapi 5.2.0 (!) :-)
Last updated: Apr 12 2022 at 19:14 UTC
