Vladimir Ignatov

You are right. This was created for local development and such an option was simply not predicted. Now that I think about it, having it running on another machine in...

I am not familiar with portainer but I guess it lists the "global" volumes that you can create and then mount to any container... In this case, all the `dstu2-data*`...

Yes, i see this is introducing a lot of changes and merging it properly will be difficult. In fact, I did merge it but I am also making other changes...

I haven't been able to reproduce this so far. - Is it in the patient browser (the popup before launch) or in the built-in patient picker that is rendered after...

Got it, thank you! The reason for this was that the ":contains" operator wasn't enabled on our r4 server. I have enabled it now and should stop producing these errors....

It seems to work fine for me with http://launch.smarthealthit.org/v/r3/fhir. Can you provide an example or description of how you launch the medications app (including the patient that you select)?

Launching with that server is simple - just run `npm start` in the medications app and then open http://127.0.0.1:9090/launch.html?launch=eyJhIjoiMSJ9&iss=http%3A%2F%2Flaunch.smarthealthit.org%2Fv%2Fr3%2Ffhir. Which server are you launching with?

Got it. I was testing with 1.0.12. Unfortunately the change is in fhir.js and I can't revert it without loosing other stuff. I'll have to patch it somehow.

I think you are right. Patching the client or maintaining a fork of fhir.js should be avoided if possible. I could also "fix" the sample apps. That is not a...

It was not intentional but it is more complicated than that. The client depends on `fhir.js` in a weird way. 1. `fhir.js` does not come with pre-built JS. It is...