Thoughts and comments on the emerging HL7 FHIR standard, from a FHIR Evangelist
May 17, 2018 Leave a comment
In June this year, there will be the first FHIR DevDays in the United States – in Boston.
For those unfamiliar with DevDays (Developer Days), this is a 3 day event simply crammed with FHIR activities – from educational presentations to ‘Connectathon’ type testing to just enjoying the community (and maybe a beer or two…) .
April 29, 2018 Leave a comment
This is the third post in a mini series on using the Logical modeler. In the first post we talked in generalities of models (admitting that this is very much a work in progress), and then we discussed the Information Model – a model that is used to capture clinical requirements for information exchange. Now, it’s time to think about how we can design real FHIR artifacts from the work so far.
April 29, 2018 1 Comment
As described in the previous post, an Information model is used to capture the data requirements for a use case in a structured way, using the FHIR datatypes, but not aligned with the core FHIR resource types. This means that you can’t create an instance of this model – it’s just for analysis – but it will inform the development of the real FHIR artifacts.
April 29, 2018 2 Comments
It’s been a while since we talked about the clinFHIR Logical Modeler, and I’ve had a few questions about it, so I thought an update might be in order.
The term ‘Logical Model’ can be used in different ways (much like ‘Profile’) so let’s first define just what we are talking about. Basically, it’s just a hierarchical model of data – much like you see in any of the core FHIR resource types – with the exception that the model does not have to align with any of the core types. Other than the requirement that you must use the FHIR datatypes, there are no limits on the complexity of the model you create (though overly complex models can be hard to understand – or use).
In this post we’ll talk about the general aspects of using the modeler – subsequent posts will go into more detail about how to build them.
November 7, 2017 1 Comment
Last week we held our first New Zealand ‘Clinicians on FHIR‘ seminar at the HINZ conference in Rotorua. This was really important for me, as it was the first ‘public outing’ of a seminar format that I’d like to see could be repeated wherever Clinicians are getting their first taste of FHIR, and showing how they can participate more fully in FHIR based Interoperability projects.
We had around 30 attendees and excellent participation – especially as the event was a combination of presentations and practical exercises. Thanks to John Fountain for presenting the clinical perspective. Talking to participants after the event was also very positive, with some good suggestions for improvement of the seminar.
October 7, 2017 3 Comments
These are some notes written by Lloyd, Grahame & Eric about using Observation in practice. I’ve copied this directly, here so I always know where to find it. You should refer to the source for the most recent version.
September 25, 2017 9 Comments
As you probably know, there are a number of ‘conformance’ resources in FHIR that have a unique ‘canonical’ Url that identifies them globally. Other resources that need to refer to them can do so by addressing them by that URL – for example when a profile (Core or Derived) binds a coded element to a ValueSet, it does so via that URL – as does a Profile referencing an Extension Definition (both Profile and Extension Definition are StructureDefinition resources).
Looking at the definition of the Url in the spec:
For StructureDefinition:
An absolute URI that is used to identify this structure definition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this structure definition is (or will be) published. The URL SHOULD include the major version of the structure definition.
For ValueSet
An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this value set is (or will be) published. The URL SHOULD include the major version of the value set.
So how do you accomplish this across different versions of FHIR?
Recent Comments