Stream: hapi
Topic: Encounter INCLUDE
Hannes Ulrich (Nov 18 2016 at 14:33):
Hey! I'm working with the include feature on the Encounter resource and discovered some inconsistencies. Running the following snippet does not return any resources besides the original resource:
bundle = client.search().forResource(Encounter.class)
.where(Encounter.RES_ID.matches().value(new IdDt(url).getIdPart()))
.include(Encounter.INCLUDE_ALL)
.execute();
Additionally there is the possibility of adding Encounter.INCLUDE_CONDITION, but looking at the Encounter spec, I'm not sure which one that should be! Any thoughts on that?
PS: And how can I can format code snippets in here?
Hannes Ulrich (Nov 22 2016 at 11:47):
I ran into a "ca.uhn.fhir.rest.server.exceptions.InternalErrorException: HTTP 500 Server Error" using the resource.INCLUDE, if the referenced instances aren't stored on the same server. E.g. an encounter is stored on server A and contains a reference to a patient which is stored on server B. Is there a way to call the external reference asynchronously?
James Agnew (Nov 30 2016 at 02:52):
Hi @Hannes Ulrich , is this issue happening against our public server, or a local server? If local, is it HAPI JPA or a plain HAPI server?
If you want to format a snippet, just wrap it in three backticks before and after the snippet (backtick is the key to the left of the 1 on a US English keyboard.. not sure on others)
Hannes Ulrich (Nov 30 2016 at 14:54):
Hi @James Agnew , it is a local HAPI JPA server, version 2.1. The other server is a Spark.
James Agnew (Dec 01 2016 at 17:44):
Hi Hannes,
This turned out to be a bug in HAPI. I've checked in a fix :)
Hannes Ulrich (Dec 02 2016 at 11:09):
Hi James, thanks for the quick fix!
Last updated: Apr 12 2022 at 19:14 UTC
