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

Follow-up questions from FHIR & Ice

At our recent ‘FHIR & Ice‘ seminar, we tried to answer as many question as we could, but we did ask people who attended if there were outstanding ones that we could have covered. Here is our attempt to answer them, I did the FHIR ones and my colleague Alastair Kenworthy the SNOMED ones.

Read more of this post

Creating Lists in clinFHIR

As we’ve just discussed, clinFHIR allows you to quite easily create resources based on profiles (whether the ‘core’ resource profiles or simple ones created by clinFHIR) but what about more complex structures like Lists?

Read more of this post

Building resources from FHIR profiles.

This post finishes off our ‘mini-series’ on creating a simple profile using clinFHIR – now we’ll create a resource based on the profile that we created earlier.

Read more of this post