FHIR Chat · lookup, $expansion: results looks different on each server · terminology

Stream: terminology

Topic: lookup, $expansion: results looks different on each server

Marcelo Cabello (Sep 12 2019 at 11:27):

Hi. I can see the result of operations $lookup and $expand looks different on my local server than on other servers (for example fhirtest.uhn.ca) .
My local server doesn't show the properties for the concepts that I added to CS, and $expand shows the right expansion only for intensional declaration of codes, but it doesn't show it when I build filters in VS.
Do I have to do another configuration in the server or the resources? (maybe CapabilityStatement is the right way...)
A hint would be very welcome!

Rob Hausam (Sep 12 2019 at 12:14):

What is your local server? Many specific details of the output content and formatting are at the discretion of the particular server implementation.

Marcelo Cabello (Sep 12 2019 at 13:24):

Hi @Rob Hausam . I know the output details are particular on different servers( vonk, hapi, whatever). In this case my local server is a Hapi Fhir jpa-starter 3.8. So, the comparison between both results (local and fhirtest.uhn.ca) are under the same kind of server.
So, I guess the details of the implementation of terminology services should be configured in the server or the ad-hoc resource(s). I'm looking for what say the spec about it. But, it seems this aspect belongs to server instead the spec

Marcelo Cabello (Sep 13 2019 at 11:52):

Hi @James Agnew , could you give me a suggestion about this trend?

James Agnew (Sep 13 2019 at 13:03):

If you could provide sample links on public servers that shows what you're talking about that would be helpful to understand your issue.

Marcelo Cabello (Sep 13 2019 at 13:37):

this request looks well GET http://hapi.fhir.org/baseDstu3/CodeSystem/$lookup?system=http://terminology.cens.cl/CodeSystem/semana&code=_lun
It brings not only the concepts but also its property.
However, on my local server only retrieves:

{
    "resourceType": "Parameters",
    "parameter": [
        {
            "name": "name",
            "valueString": "Unknown"
        },
        {
            "name": "display",
            "valueString": "Lunes"
        },
        {
            "name": "abstract",
            "valueBoolean": false
        }
    ]
}

Grahame Grieve (Sep 13 2019 at 13:48):

is your local server a HAPI server?

Marcelo Cabello (Sep 13 2019 at 13:48):

yeap!

Grahame Grieve (Sep 13 2019 at 13:48):

how is http://terminology.cens.cl/CodeSystem/semana defined?

Marcelo Cabello (Sep 13 2019 at 13:57):

it's the same definition in hapi fhir test server (http://hapi.fhir.org/baseDstu3/CodeSystem/cs-semana)

Grahame Grieve (Sep 13 2019 at 14:58):

ok. so I agree that there is more information that could be returned that is not being returned

Grahame Grieve (Sep 13 2019 at 14:58):

have you tried it on test.fhir.org?

James Agnew (Sep 13 2019 at 15:16):

If you're only seeing this issue on your local HAPI server, it's probably worth upgrading to the 4.0.0 release (or even the 4.1.0-SNAPSHOT release). Lots of active work is happening right now on the term service, which explains why you're seeing different results on your local server from on the public server.

Marcelo Cabello (Sep 23 2019 at 21:13):

It works well after try with 4.0.0 release of jpa-starter. I didn't try yet on test.fhir.org but it will be done
Thanks @Rob Hausam , @Grahame Grieve , @James Agnew

James Agnew (Sep 23 2019 at 21:16):

woohoo!

Last updated: Apr 12 2022 at 19:14 UTC