-
Notifications
You must be signed in to change notification settings - Fork 59
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
[ServerSide] Move the Practitioner Details endpoint to plugins on the FHIR Gateway #2213
Comments
In order to add a new end-point on the Gateway, it would be necessary to conduct R&D to figure out the actual design implementation. Following that investigation, the appropriate LOE would be shared. |
Initial R&D results on Moving Practitioner Details end-point to the Plugin module on the FHIR Gateway: |
Found another finding during the R&D:
Here is the reference on the Hook documentation. I will look around for a solution for this and see if there is a way to skip certain end-points from intercepting the request. |
@rehammuzzamil I have reviewed the comments above and this is how I thought the workflow would look like
Pros
Cons
|
I don't think the above description will help with the infinite loop created when the request is returned from the JPA server. I will review this further and leave comments |
There is an issue encountered while returning the aggregated response on the custom end-points (Testing it with However, the same flow works fine on the FHIR end-points (For example: /Patient). I have observed, both custom and existing end-point of FHIR follows the same flow of logic and lands on the same if/else condition blocks. I have also added logs to monitor how many times the same method is being executed to ensure that stream is accessed only once for the reading, and observed the same that the method is triggered only once in both the cases. It fails with the following exception and stack trace:
Please let me know if you have any thoughts @dubdabasoduba |
@rehammuzzamil @dubdabasoduba identified the issue as being caused by invocation of this helper method: Internally in its implementation it closes the reader after it finishes processing I've stripped out the invocations on my PR here #39 , we can find some other alternative way to process the response |
Thanks @ndegwamartin |
Context
Implementation
Acceptance Crirteria
Linked issues
The text was updated successfully, but these errors were encountered: