-
Notifications
You must be signed in to change notification settings - Fork 345
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
Our terminology client does not work with ontoserver anymore #2854
Comments
BTW, switching to tx.fhir.org gives a null reference exception ;-( |
Apparently we send requests like this:
The error mentions we must send one of the following: |
Hmmm in the FHIR Spec it says:
So in this case, we must send the context too. I'll just ask the CSIRO people.. |
This tickets requires multiple changes: SDK:
Validator:
|
While using our Validator Demo, I tuned the settings so I forced it to use the suggested ontoserver terminology service. (Change..., select ontoserver, unmark try built-in terminology service first). I then got an error:
It seems we're providing too many parameters to the $validate-code call (while our internal terminology service accepts it). We should make sure we send legal calls to ontoserver (since I believe they have a great implementation) that is also sufficient for our built-in TS.
The text was updated successfully, but these errors were encountered: