Local Feasilbility with Direct Broker + CQL + Basic Auth

[FloSeidel]

Hi,

I tried to setup the Feasibility portal for local Feasibility.

I used the direct broker with cql and needed to add basic auth funktionality. So I updated the images for the backend and the gui to (feasibility-backend:4.3.0 and feasibility-gui:2.3.4 respectivly).

Basic Auth seems to work, since the CQL Query is handed to blaze (0.26.1) and interpreted:

blaze_1          | 2024-05-29T09:33:00.673Z fed1a3fb8454 qtp1511733443-148880 DEBUG [blaze.rest-api.middleware.log:17] - GET [base]/fhir/metadata
proxy-nginx      | 10.32.42.200 - hdp-fhir-user [29/May/2024:09:33:01 +0000] "GET /fhir/metadata HTTP/1.1" 200 1861176 "-" "HAPI-FHIR/6.6.2 (FHIR Client; FHIR 4.0.1/R4; apache)"
blaze_1          | 2024-05-29T09:33:01.566Z fed1a3fb8454 qtp1511733443-168026 DEBUG [blaze.rest-api.middleware.log:17] - POST [base]/fhir
proxy-nginx      | 10.32.42.200 - hdp-fhir-user [29/May/2024:09:33:01 +0000] "POST /fhir HTTP/1.1" 200 475 "-" "HAPI-FHIR/6.6.2 (FHIR Client; FHIR 4.0.1/R4; apache)"
blaze_1          | 2024-05-29T09:33:01.796Z fed1a3fb8454 qtp1511733443-168024 DEBUG [blaze.rest-api.middleware.log:17] - GET [base]/fhir/Measure/$evaluate-measure?measure=urn%3Auuidf2159d93-a205-46e8-b4a5-c4dd3b50ae93&periodStart=1900&periodEnd=2100
blaze_1          | 2024-05-29T09:33:01.921Z fed1a3fb8454 ForkJoinPool.commonPool-worker-119 DEBUG [blaze.fhir.operation.evaluate-measure.measure:94] - Start compiling Library with ID `DD6DWIPVSAGOP2VT`...
blaze_1          | 2024-05-29T09:33:03.646Z fed1a3fb8454 ForkJoinPool.commonPool-worker-119 DEBUG [blaze.fhir.operation.evaluate-measure.measure:100] - Compiled Library with ID `DD6DWIPVSAGOP2VT` in 1725 ms.
blaze_1          | 2024-05-29T09:33:03.654Z fed1a3fb8454 ForkJoinPool.commonPool-worker-119 DEBUG [blaze.fhir.operation.evaluate-measure.measure:233] - Start evaluating Measure with ID `DD6DWIPVSAGOP2VU`...
proxy-nginx      | 10.32.42.200 - hdp-fhir-user [29/May/2024:09:33:11 +0000] "GET /fhir/Measure/$evaluate-measure?measure=urn%3Auuidf2159d93-a205-46e8-b4a5-c4dd3b50ae93&periodStart=1900&periodEnd=2100 HTTP/1.1" 499 0 "-" "HAPI-FHIR/6.6.2 (FHIR Client; FHIR 4.0.1/R4; apache)"

The backend seems to have an issue waiting for the result, since it fails with the following issue:

09:32:59.039 [XNIO-1 task-2] DEBUG o.s.w.s.m.m.a.RequestResponseBodyMethodProcessor - Read "application/json;charset=UTF-8" to [StructuredQuery[version=http://to_be_decided.com/draft-1/schema#, inclusionCriteria=[[Criterion[cont (truncated)...]
09:32:59.145 [XNIO-1 task-2] INFO  d.n.f.query.dispatch.QueryDispatcher - try to enqueue new query
09:32:59.191 [XNIO-1 task-2] INFO  d.n.f.query.dispatch.QueryDispatcher - enqueued query '9'                                                                                                                                                                                        
09:32:59.312 [XNIO-1 task-2] DEBUG d.n.f.q.t.QueryTranslationComponent - library Retrieve version '1.0.0'    
using FHIR version '4.0.0'                                                                                                                                                                                                                                                              
include FHIRHelpers version '4.0.0'
context Patient
 
define Criterion:
    Patient.gender = 'female'
define InInitialPopulation:
    Criterion
 
09:32:59.313 [XNIO-1 task-2] DEBUG d.n.f.q.t.QueryTranslationComponent - {"inclusionCriteria":[[{"context":{"code":"Patient","system":"fdpg.mii.cds","version":"1.0.0","display":"Patient"},"termCodes":[{"code":"263495000","system":"[http://snomed.info/sct"](http://snomed.info/sct%22),"display":"Geschlecht"}],"valueFilter":{"type":"concept","selectedConcepts":[{"code":"female","system":"[http://hl7.org/fhir/administrative-gender"](http://hl7.org/fhir/administrative-gender%22),"display":"Female"}]}}]],"version":"[http://to_be_decided.com/draft-1/schema#"}](http://to_be_decided.com/draft-1/schema#%22%7D)                                                                            
09:32:59.330 [XNIO-1 task-2] INFO  d.n.f.q.c.QueryStatusListenerImpl - query '4d6b27db-ae42-4967-b7de-3bf430fb4d7a' of broker client with type 'DIRECT' to site '1' changed its status to 'EXECUTING'                                                                              
09:33:01.801 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - GET "/actuator/health", parameters={}                                                                                                                                                                        
09:33:01.802 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.RequestResponseBodyMethodProcessor - Read "application/octet-stream" to []                                                                                                                                                        
09:33:01.805 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Using 'application/vnd.spring-boot.actuator.v3+json', given [*/*] and supported [application/vnd.spring-boot.actuator.v3+json, application/vnd.spring-boot.actuator.v2+json, application/json]
09:33:01.805 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Writing [org.springframework.boot.actuate.health.SystemHealth@31c53c52]                                                                                                                                
09:33:01.806 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - Completed 200 OK                                                                                                                                                                                            
09:33:06.893 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - GET "/actuator/health", parameters={}                                                                                                                                                                        
09:33:06.895 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.RequestResponseBodyMethodProcessor - Read "application/octet-stream" to []                                                                                                                                                        
09:33:06.897 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Using 'application/vnd.spring-boot.actuator.v3+json', given [*/*] and supported [application/vnd.spring-boot.actuator.v3+json, application/vnd.spring-boot.actuator.v2+json, application/json]
09:33:06.897 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Writing [org.springframework.boot.actuate.health.SystemHealth@3fc428f0]                                                                                                                                
09:33:06.898 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - Completed 200 OK                                                                                                                                                                                            
09:33:11.805 [XNIO-1 task-2] INFO  d.n.f.q.c.QueryStatusListenerImpl - query '4d6b27db-ae42-4967-b7de-3bf430fb4d7a' of broker client with type 'DIRECT' to site '1' changed its status to 'FAILED'
09:33:11.811 [XNIO-1 task-2] ERROR d.n.f.query.dispatch.QueryDispatcher - failed to dispatch query '9' with broker type 'DIRECT'                                                                                                                                                    
09:33:11.817 [XNIO-1 task-2] ERROR d.n.f.q.v.QueryHandlerRestController - running a query for '2c0f37c9-0a36-484c-a7fe-410a810285b2' failed
de.numcodex.feasibility_gui_backend.query.dispatch.QueryDispatchException: cannot dispatch query with id '9'. Dispatch failed for all brokers  
at de.numcodex.feasibility_gui_backend.query.dispatch.QueryDispatcher.lambda$dispatchEnqueuedQuery$3(QueryDispatcher.java:110)  
    at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:132)
    stacktrace ongoing...
 
09:33:11.826 [XNIO-1 task-2] DEBUG o.s.w.c.r.async.WebAsyncManager - Started async request                                                                                                                                                                                          
09:33:11.827 [XNIO-1 task-2] DEBUG o.s.w.c.r.async.WebAsyncManager - Async result set, dispatch to /api/v3/query                                                                                                                                                                    
09:33:11.829 [XNIO-1 task-2] DEBUG o.s.web.servlet.DispatcherServlet - Exiting but response remains open for further handling                                                                                                                                                      
09:33:11.832 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - "ASYNC" dispatch for POST "/api/v3/query", parameters={}                                                                                                                                                    
09:33:11.835 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerAdapter - Resume with async result [<500 INTERNAL_SERVER_ERROR Internal Server Error,cannot dispatch query with id '9'. Dispatch failed  (truncated)...]                                                      
09:33:11.839 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Using 'application/json', given [application/json, text/plain, */*] and supported [text/plain, */*, application/json, application/*+json]                                                              
09:33:11.839 [XNIO-1 task-3] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Writing ["cannot dispatch query with id '9'. Dispatch failed for all brokers"]                                                                                                                        
09:33:11.842 [XNIO-1 task-3] DEBUG o.s.web.servlet.DispatcherServlet - Exiting from "ASYNC" dispatch, status 500

(I reduced the length of the stacktrace) if its necessary I can provide it no problem.

Thanks for helping in advance.

Furthermore: What I asked myself is wether I could use the DSF backend integration (FEASIBILITY_BACKEND_DSF_*) for local feasibility queries?

[EmteZogaf]

@FloSeidel Is this issue still existing?