-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with the FHIR search queries when using the blaze FHIR server #5
Comments
@alexanderkiel just to be sure: The above query doesn't seem work with the blaze. Is that because this kind of Search Parameter is not implemented or is something going wrong with the references in the server? |
Exactly, it is because this kind of search parameter is not supported by Blaze. The references in the dataset used are correct. I've verified that the Query does work when using the IBM FHIR server using exactly the same dataset. |
Okay, because I think we had a case somewhere where a reference query didn't work because there references weren't correctly resolved internally. Does the query work if you remove the |
@RaffaelBild You are right. The reason is that Blaze doesn't support chained search parameters jet. So |
Okay, that's good to know, thanks. @RaffaelBild is there any chance you could use another type of server? It seems like you have an IBM available? |
Thank you all for the information. I do have an IBM available and will use this server for the analysis then. |
Great, thank you both! |
Thank you @palmjulia for your quick response! @RaffaelBild Yes it would be great if you can use the similar type of server (IBM). Thank you! |
Hi, we are currently using Blaze as well. Unfortunately we are not having another server on hand :/ |
@FloSeidel Is the FHIR search query also gives you 0 encounters? |
Hi, thank you all @palmjulia , @RaffaelBild , @alexanderkiel, @FloSeidel and @NandhiniS08 for you inputs. @FloSeidel did you have the opportunity to try out @palmjulia's suggestion regarding the query? |
As @alexanderkiel wrote the Blaze currently doesn't support chaining at all, so neither |
The initial query Your adaption |
Careful, the second result is !=0 but still not correct, I think it just gives back the same number as |
Yep. I can confirm, it's the same. |
I updated the code as per @palmjulia suggestion to download the resources without chaining and pushed them into a different branch blaze_update @FloSeidel Is it possible for you to pull this branch and execute it? Thank you! |
Will do. I get back to you when it finishes. |
@FloSeidel I've released the v0.17.0 of Blaze which supports chaining and is a drop-in replacement for the v0.16.x versions. So you can just try it on your existing data. |
Hello,
unfortunately it seems that the Blaze FHIR server does not support FHIR search reference parameters.
As a consequence, the first FHIR search query
Encounter?date=ge2015-01-01&diagnosis:Condition.code=I60.0,I60.1,I60.2,I60.3,I60.4,I60.5,I60.6,I60.7,I60.8,I60.9,I61.0,I61.1,I61.2,I61.3,I61.4,I61.5,I61.6,I61.8,I61.9,I63.0,I63.1,I63.2,I63.3,I63.4,I63.5,I63.6,I63.8,I63.9,I67.80!&_include=Encounter:patient&_include=Encounter:diagnosis
does not work as expected when using Blaze, because it cannot select Encounters based on ICD codes of Conditions they reference. More precisely, the query returns 0, even though the data definitely containes Encounters that meet the specified search criteria.
Is there any way to still do this analysis when using the Blaze server?
The text was updated successfully, but these errors were encountered: