Building resources from FHIR profiles.
August 3, 2015 1 Comment
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.
Thoughts and comments on the HL7 FHIR standard, from a FHIR Evangelist
August 3, 2015 1 Comment
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.
July 26, 2015 12 Comments
In the previous post, we outlined our plans for creating a profile against the Patient resource, and manually created and saved some of the supporting resources (ValueSet and our NamingSystem) that we’re going to need.
Next up is the extension definition and the actual profile against Patient. Once we’ve done that (which is the topic of this post) we can actually create conformant resources.
Fortunately, we can use clinFHIR to create these artifacts, so start up that application and select the ‘profile builder’ from the front page. (And a reminder that this is very much ‘beta’ software designed for training! Let me know of any issues)
July 26, 2015 5 Comments
One of the things we discussed at the recent seminar in New Zealand was profiling FHIR resources. This is where we take the base resources and then adapt them for specific use cases. While quite simple in concept, there are some complexities ‘under the hood’, so part of the talk was to describe some of the ‘infrastructure’ that makes all this work.
Once we had the set up some of the supporting resources, we used the clinFHIR tool to actually assemble the profile, as this makes it easier for ‘non-technical’ people – especially clinicians – to build these artifacts, and then build a resource that is conformant to that profile.
July 11, 2015 1 Comment
So I got an interesting email yesterday.
Someone asked me how to fulfill the following User Story: As a clinician, I want to search for a list of patients being seen by certain consultants today.
There were some Acceptance Criteria given:
Now, we’d want to dig a bit into the specifics of how some of the searches should work – eg what does it mean when you specify a consultant and a ward – that the consultant saw the patient on the specified ward on that date? And what happens when both a consultant and a specialty are in the query parameters?
But lets start with a simple case – getting a list of patients seen by a consultant on a specified date. This is not quite as simple as it sounds!
May 24, 2015 3 Comments
One of the things that is happening to FHIR is that as it grows in maturity, it is starting to attract more Clinicians and Business Analysts who are less interested in the technology, and more interested in how it can be used to represent the clinical information they want to share – both inside and between organizations.
Indeed, the chair of HL7 – Stan Huff – referred to this explicitly at the last Working Group Meeting when he referred to the importance of the clinical community getting together to develop the profiles of use that take the core FHIR specification, and make it work for the clinical community. There is a very real risk of developing multiple different profiles that actually mean the same thing and thus harming interoperability. FHIR offers mechanisms to avoid this, but it does mean that people – especially clinical and analysts –need to have a good idea of how FHIR in general – and these mechanisms in particular – work.
Recent Comments