FHIR Chat · CMS Connectathon Notes

Howdy all, I'm back from the CMS Connectathon and thought I'd start a thread with notes/questions/comments/info/etc. from it. Please feel free to jump in if I missed anything, or for discussion on anything below in general.

1) hapi.fhir.org is having issues, so if you are using the test server at subscriptions.argo.run, it will be having issues (it proxies calls to the public hapi server). I am trying to find out ETA or will look into alternatives.

2) CORS issues can and will happen in development/testing/prod. If you work on a server, please make sure it returns the necessary headers (Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers minimum). CORS errors will show up in the JavaScript console in most browsers, so it's a good place to check if connections are failing that you expect to work.

3) Need a big push on consolidating functionality/definitions with DaVinci Notifications so that we don't end up with two workflows doing (mostly) the same thing. Will likely be arranging a small focus group first to sort through it, then present for broader feedback.

4) I am lagging a bit on documentation and resource definitions. Sorry, but in my defense - editing the core specs is painful. I hope to have everything up to date (whatever that means) before Sydney. In the mean time, please note that I push into the argonaut-subscriptions branch on the build server, so it has the most current. Once I'm fully caught it, I'll be submitting Jira issues for FHIR-I before merging into master.

5) I will be looking at clarifying the matchType fields on Subscriptions and SubscriptionTopics. Current feedback is that if we are using a search modifier, the name of the field should indicate that.

n-1) A BIG THANKS to everyone!

Keith Boone (Jan 09 2020 at 22:10):

Other notes: Gino has added some new features to his tool to make life easier. Download it from github and do npm install and run it locally for easier debugging, especially with something like wire shark to get a better idea of what’s going on ( I found it especially helpful dealing with CORS stuff).

Keith

On Jan 9, 2020, at 2:04 PM, Zulip missed messages <noreply@zulipchat.com> wrote:

Gino Canessa:
Howdy all, I'm back from the CMS Connectathon and thought I'd start a thread with notes/questions/comments/info/etc. from it. Please feel free to jump in if I missed anything, or for discussion on anything below in general.

2) CORS issues can and will happen in development/testing/prod. If you work on a server, please make sure it returns the necessary headers (Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers minimum). CORS errors will show up in the JavaScript console in most browsers, so it's a good place to check if connections are failing that you expect to work.

5) I will be looking at clarifying the matchType fields on Subscriptions and SubscriptionTopics. Current feedback is that if we are using a search modifier, the name of the field should indicated that.

n-1) A BIG THANKS to everyone!

—
You are receiving this because you have email notifications enabled for this stream.
Reply to this email directly, view it in Zulip, or manage email preferences.

Keith Boone (Jan 10 2020 at 16:39):

Connecting today to: https://client.subscriptions.argo.run/api/Clients/ I'm getting:

Your connection is not private
Attackers might be trying to steal your information from client.subscriptions.argo.run (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID

Gino Canessa (Jan 10 2020 at 16:50):

Thanks Keith, I'll ask @Josh Mandel to renew the certs (expired today).

Gino Canessa (Jan 10 2020 at 17:25):

Fixed, wasn't auto-renewing for some reason. Thanks for the heads up!

Keith Boone (Jan 10 2020 at 19:51):

This client.subscriptions.argo.run page can’t be found
No webpage was found for the web address: https://client.subscriptions.argo.run/
HTTP ERROR 404

I'm assuming the server is offline perhaps for certificate maintenance.

Gino Canessa (Jan 10 2020 at 19:55):

I think you want subscriptions.argo.run, the service at client hosts the dynamic endpoints and proxys notifications to the UI via websockets.

Keith Boone (Jan 10 2020 at 19:59):

I'm building a subscription server, so I need to connect with a client. I'd been using https://client.subscriptions.argo.run since Connectathon.
But since I'm running locally, I suspect there might be a local URL for the client as well, as the image suggests.

Gino Canessa (Jan 10 2020 at 20:11):

There are three projects running:
1) server.subscriptions.argo.run - the FHIR server proxy which you would be replacing with your own
2) client.subscriptions.argo.run - a .Net core service which hosts endpoints and forwards notifications to the UI via websockets
3) subscriptions.argo.run - a React UI to interact with everything

Gino Canessa (Jan 10 2020 at 20:12):

If you are using the UI, it needs to use the Client Host to work with REST notifications, otherwise the client isn't actually used (e.g., in websocket or email workflows)