Stream: terminology
Topic: tx.fhir.org $expand
Matt Rouhana (Jan 24 2022 at 23:53):
The tx.fhir.org expansion for the ActEncounterCode ValueSet (http://terminology.hl7.org/ValueSet/v3-ActEncounterCode) doesn't include a contains element: https://tx.fhir.org/r4/ValueSet/v3-ActEncounterCode/$expand?_format=json
Is this intentional? Other publicly available terminology servers properly expand the ValueSet (see: https://r4.ontoserver.csiro.au/fhir/ValueSet/v3-ActEncounterCode/$expand?_format=json)
Matt Rouhana (Jan 25 2022 at 17:19):
Can anyone shed some light on the above?
Grahame Grieve (Jan 27 2022 at 05:54):
looks wrong to me
Rob Hausam (Jan 27 2022 at 15:53):
@Matt Rouhana Yes, agree this is not correct on tx.fhir.org. The HAPI server is able to expand it:
https://fhir.hausamconsulting.com/r4/ValueSet/$expand?url=http://terminology.hl7.org/ValueSet/v3-ActEncounterCode
There are two copies of the value set with different ids on tx.fhir.org:
http://tx.fhir.org/r4/ValueSet?url=http://terminology.hl7.org/ValueSet/v3-ActEncounterCode
But if I specify and try to expand either of them individually, the expansion still doesn't return a contains:
http://tx.fhir.org/r4/ValueSet/v3-ActEncounterCode/$expand
http://tx.fhir.org/r4/ValueSet/2126/$expand
@Grahame Grieve?
Grahame Grieve (Jan 27 2022 at 21:55):
I hadn't got around to coding support for http://hl7.org/fhir/concept-properties#parent on tx.fhir.org . Will be fixed next upgrade
Last updated: Apr 12 2022 at 19:14 UTC
