The clinFHIR Chat

One of the things we’ve found at the various connectathons we’ve held is that communication between the attendees can be an issue – there are quite a number of different ‘streams’ of activity and it can be hard to connect people with questions or comments, to people with answers.

We’ve used skype in the past, which has been OK, but has a number of limitations – it can be quite a firehose, which means that stuff is missed, there’s no easy to maintain a ‘thread’ of conversation (though sometimes interesting when threads get mixed together!) and hard to review the history at the end of the event. Oh – and there’s a fixed limit of 300 people per conversation, which we recently discovered.

So for the ‘Clinicians on FHIR’ event that we’re holding at the HL7 Working Group Meeting in October, we’re going to try a different approach. We’re developing a basic ‘chat’ application that is hierarchically organized, and also integrated with the tooling – clinFHIR – that participants in the event use. If all goes well, it’s also going to help in running ‘virtual’ events in the future, where people are not in the same place.

This post describes how the chat application is structured.

Read more of this post

Canadian Connectathon

For those who don’t mind snow (though I’m told that by April 29 – the connectathon date – the snow has mostly gone).

Here’s the link to the registration site.

There doesn’t appear to be a website (yet) though there are details in a PDF that you can get from the organizers I’m sure. The tracks are listed as:

  1. Patient resource client
  2. SMART server or client
  3. Questionnaire
  4. Experimental


BTW – Lloyd did offer to arrange for snow if I came, but alas…

IHE MHD (Mobile Health Data) and FHIR

Just noticed John Moehrke’s post on the recent IHE MHD connectathon. I love the way that this shows how the different organizations involved in healthcare interoperability are working together rather than taking opposing views…

Clinician Connectathon

Well, we’ve just finished the second Clinician Connectathon. I wasn’t able to attend in person, but was able to dial in from home (New Zealand) to participate and it all worked out really well.

The tooling mostly behaved itself (we had a few server issues) – which was a relief!

We’ll do a more complete review later on, but for me the take away is that these events are really worth continuing (and the others seemed to agree with this), and that the tooling needs to continue to evolve – perhaps to move away from a strictly resource focussed perspective as it is now, to a more functional one. We also need to increase the range of resources, supported properties on those resources, save more stuff to FHIR servers & improve the way we support profiling. No pressure…

We’ll continue to work on this, and we’re encouraging people to try the tooling out between events so that bugs and be squashed, enhancements can be developed, deployed & tested prior to the actual event and we can maximize the value of getting clinical folk together to talk FHIR.

If you’re interested, the tool is available here, and I do encourage you to go have a look and give us feedback (you can do that in comments to this post for the moment- we’ll figure out a better way soon). We’ll also be working on the documentation…

So, on to Paris in May! (and I’m off for a sleep…)

FHIR Clinical Connectathon

I was going to write a post on the Clinical Connectathon that we held in Chicago at the Working Group Meeting the week before last (in fact, had just written the draft) but I see that Graham has just published a post covering the event, and a number of other FHIR related comments from the WGM, so I’ll just refer you there!

For myself, I think that the comment about the evolving FHIR community – moving from simply developing a standard to using that standard to solve ‘business’ problems is probably the most exciting for me – which is what the Clinical Connectathon was all about.

I also want to point out that there are (at least) 4 more FHIR related events in the next couple of months:

Plenty of opportunities to experience the hype for yourself!

SMART on FHIR – adding OAuth2

You may recall that a week back we had a look at one of the connectathon scenarios – the SMART scenario.

In this post we’re going to take the work that we had done in the last post, and make it secure using the SMART version of the OAuth2 standard. As always, a primary reason I’m writing it down is so that when I forget what I did to make it work – I’ll have this as a reference to remind me <s>. And a reminder – I’m using the Java based HAPI FHIR client, in a web based application running in a Tomcat servlet engine, with IntelliJ IDEA as my IDE.
Read more of this post


The following is a copy of an email sent to the FHIR list by Peter Bernhardt (and copied with permission). I’ve not read through it in detail, but it’s something that I’m grappling with myself as I prepare for the SMART track in the up-coming Connectathon.

I suspect that it’s something that a lot of folk are going to have ‘fun’ with, so I suggested to Peter that we copy it here so it can be found later!

(btw – all the servers that Peter refers to are described in the spec)

  Read more of this post