-
Notifications
You must be signed in to change notification settings - Fork 1
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
Filtering on Expand throws error #5
Comments
Personally I'd just use expand from Hermes. Why complicate by using FHIR as a transport? |
Plus it has more sophisticated management of historical associations so that you can expand and include now thought to be outdated inactive concepts. |
I'm mostly using FHIR terminology to use it alongside external applications like EHRBase. |
I have restarted work on hades as I now need a generic FHIR terminology server myself! The plan is to have a plug gable architecture with Hermes being but one provider. Others will include FHIR bundles, CodeSystems and data marked up in CSVW for example. |
Merge 'Decoupled architecture': Start of new architecture with pluggable modular backend. Still a work-in-progress, with additional modules needed for value sets and code systems including those built-in to HL7 FHIR but also other information standards/ value sets defined in a variety of formats (FHIR, JSON, EDN, CSVW) to create reproducible FHIR server images from source data. As a by product, fixes #5 in relation to URL decoding.
Sending the request:
Returns:
Also, I've noticed that switching the order of the query parameters:
Throws:
Moreover, sometimes, the query might be URL encoded by some client libraries:
The conversion of
would be
and this also throws:
Been learning some clojure in my free time. And I think the regex might be a reason for the Resource is not known error:
hades/src/com/eldrix/hades/convert.clj
Line 165 in 536c9ff
Not really sure regarding the null pointer. Seems like you are getting the filter parameter:
hades/src/com/eldrix/hades/core.clj
Line 116 in 536c9ff
But not sure how it's being used.
The text was updated successfully, but these errors were encountered: