Jens Kristian Villadsen
Jens Kristian Villadsen
I saw that the homesharing feature is removed because it was incomplete. Could you explain what is needed for the feature to be completed?
…interceptors a better chance of figuring out what happened.
at https://github.com/hapifhir/hapi-fhir/blob/107de2cfba04691ec085453062ee98f7200d7a4e/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/packages/JpaPackageCache.java#L407 - the following bug occur with stacktrace (from HAPI FHIR JPA starter): ``` at java.base/java.util.concurrent.FutureTask.run(FutureTask.java) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:866) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:845) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1332) at...
Instatiating https://github.com/hapifhir/hapi-fhir/blob/4a726dd2d1d015ad03340d9c726a31c2b0ee831b/hapi-fhir-jpa/src/main/java/ca/uhn/fhir/jpa/sched/BaseHapiScheduler.java#L59 instead of having it autowired makes it hard to configure for downstream projects using e.g. regular Spring Boot AutoConfiguration features.
As seen on https://github.com/hapifhir/hapi-fhir-jpaserver-starter/issues/655#issuecomment-1980559256 it seems that there are duplicate bean definitions here https://github.com/hapifhir/hapi-fhir/blob/519f0cf69ea030427e684b99fd9dd3257765d69f/hapi-fhir-jpaserver-subscription/src/main/java/ca/uhn/fhir/jpa/topic/SubscriptionTopicConfig.java#L81 and here https://github.com/hapifhir/hapi-fhir/blob/519f0cf69ea030427e684b99fd9dd3257765d69f/hapi-fhir-jpaserver-subscription/src/main/java/ca/uhn/fhir/jpa/subscription/submit/config/SubscriptionSubmitterConfig.java#L57 which may cause non-deterministic behaviour.
Isn't https://github.com/smart-on-fhir/client-js/blob/8f64b770dbcd0abd30646e239cd446dfa4d831f6/src/Client.ts#L247 this a somewhat strong assumption. AFAIK the patientId is not required to be present in the access token.