‘Extending’ a ValueSet in a profile

In the last post we talked about ValueSets and CodeSystems – and in particular how the ValueSet can be thought of as the set of possible values from one or more CodeSystems for a particular element in a given context.

As you know, the spec provides ValueSets and bindings for all coded elements, and a common need when profiling is likely to be to ‘extend’ the set of possible values – take the contents already in the ValueSet and add others. What’s the best pattern to do that?

Read more of this post

‘Default’ namespaces in HL7 v2

So I had an interesting question this week about coded values when importing data from HL7 v2 messages into a data store, and then subsequently exporting them in FHIR interfaces.

The specific question was what should the ‘default’ namespace be when the namespace is not specified in the v2 message?

Read more of this post

EU Data Protection

Great post from Rene Spronk on the European Union GDPR (General Data Protection Regulation) standards in the context of healthcare interoperability…

clinFHIR profile viewer

Over the years I’ve made a number of attempts to build a profile viewer – to a mixed amount of success. The issue is becoming more urgent though, as profiles (as part of Implementation Guides) start to become published, and vendors such as Orion Health need to think about how we are to support them.

The issue is even more important for vendors in the international space, as our solutions are going to have to support different profiles in different countries, and we cannot assume that the profiles will be in alignment even for the same concept.

We’re not going to solve that issue right now (though it does highlight that the developers of profiles need to be aware of it and ideally working to avoid it as much as possible), but the ability to view profiles from different jurisdictions and analyse them in a common way is going to be important. Read more of this post

Changing a ValueSet in a profile

I learned something today.

Actually, most days I do learn something (and occasionally remember it later on) but this one is worth recording here.

Read more of this post

Viewing resource instances in clinFHIR

One thing you need to do quite frequently in the FHIR world is to look at resource instances (whether in XML or JSON), and this can be quite complex.

A little trick I use quite frequently is to use the clinFHIR scenario builder to create a hierarchical “tree view” of the resource, which I find easier to review than the raw format.

To do this, follow these steps.

Read more of this post

Connectathon report

A report on the recent FHIR connectathon hosted at the HL7 Site...