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…)

DevDays slides

This link (which came up during the Connectathon) is to the presentations given at the recent Dev Days in Amsterdam. The actual video recordings of the event are also on line.

FHIR Videos from Amsterdam Developer days

I came across this site just this morning – it’s got a whole lot of videos from the recent Developer Days in Amsterdam last November.

I’ve not had a chance to review they presentations (this was a 3 day event), but given that all the FHIR experts were present they are bound to be excellent, and a tremendous source of information.


Extension Viewer Update

I’ve posted an update to the Extension Viewer that I’ve been working on over the holidays.

Read more of this post

Profiling resources in DSTU2 – part 2.

Actually, on reviewing the previous post about profiling in DSTU-2, I realize that there is a simpler way of applying extensions to a profile (in addition to the Conformance package). If you look at the Profile resource, it contains 2 main parts:

  • Metadata about the Resource/Datatype being profiled (name, identifier publisher etc) plus the name of the resource and a link to the base profile that is being modified (eg the profile that describes the core resource in the spec).
  • A collection of elements (of type ElementDefinition) each of which describes one of the elements/properties within the resource.

(To be precise, there are 2 collections of elements in the profile:

  • The differential – which describes the difference between the base profile
  • The snapshot – which describes the profiled resource completely

the reason for the two is to support tooling – we’ll focus on the snapshot for now).

Read more of this post