Skip to content
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

Various fixes and improvements, including XML support #136

Open
wants to merge 17 commits into
base: stu3_mar2017
Choose a base branch
from

Conversation

eug48
Copy link

@eug48 eug48 commented May 31, 2018

The XML support (largely thanks to https://github.com/lantanagroup/FHIR.js and https://github.com/dop251/goja) makes it possible to test using Crucible which should help improve the spec compliance of what is quite a good server (especially from a start-up time & performance point of view).

I've also added a workaround for the lack of transactions into my fork of fhir-server (eug48/fhir-server@bb06f) but with the upcoming support for transactions in MongoDB 4.0 it should be relatively easy to implement them properly.

If this is merged the previous PR (#134) can be closed.

eug48 and others added 17 commits March 8, 2018 19:19
The previous MIME type breaks the FHIR .NET API
to avoid URLs like Patient?identifier=urn:oid:0.1.2.3.4.5.6.7|urn:uuid:6002c2ab-9571-4db7-9a79-87163475b071
Chained searches with modifiers (e.g., `foo:Bar.baz`) were not properly parsed and resulted in errors.  Now they are properly parsed (e.g., param is `foo`, modifier is `Bar`, and chained query is `baz`).  Addresses intervention-engine#93.

(cherry picked from commit 3f6fef6)
Uses the FHIR.js library developed by the Lantana Consulting Group (https://github.com/lantanagroup/FHIR.js)
as well as the gaja Go-based JavaScript engine
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants