So you want to create a FHIR extension?

 

Most people familiar with FHIR will be aware of profiling resources – and in particular adding new elements to resources for a specific use case – adding an extension. It seems straightforward, but there are a number of things to think about when you do this so – or so we’ve found at Orion Health!

In this post we’ll talk about some of the factors involved – less about the technology and how they work in FHIR and more about some of the design time issues.

Read more of this post

FHIR Connectathon, May 2017, Madrid Spain

Notice about the next connectathon:
It’s again my pleasure to remind you of the 15th FHIR Connectathon that is coming up on the Saturday/Sunday 6/7 May just before the next HL7 Working Group Meeting in Madrid, Spain. Here’s the link to the WGM: http://www.hl7.org/events/working_group_meeting/2017/05/
Here’s the wiki page that describes the connectathon in more detail: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_15

Read more of this post

Adding extensions to a resource

So a colleague of mine asked me this morning if the clinFHIR scenario builder supported modifier extensions.

If you’re not familiar with these, they are extensions that actually change the meaning of the resource to which they are attached. For example, if you wanted to indicate that a patient did not have a particular condition, then you could attach a ‘negation’ extension to the Condition to indicate that you looked for – but did not find – that particular condition. Or, a statement that indicates that a patient is not taking a particular medication.

Read more of this post

A complex scenario…

Bob Milius has kindly allowed me to share an example of a more complex genetics based scenario that he has built (by hand!) – you can download it from here.

To load it into clinFHIR, follow the steps I described in this post and you can then view it as a graph. Here’s an image:

Read more of this post

Internet etiquette

Just a very short post to the author of the site that is copying my posts (and that of others). While I’m flattered you think my work worthy of duplication,  there are more polite ways to recognize this than just a complete copy – including asking me first!

There’s no obvious way to contact you on your site, so hopefully this post will come to your attention.

Please contact me directly – my email is david dot hay twenty five at gmail.com so we can work out how you can do this in a more polite fashion.

cheers…

Import resources into clinFHIR Scenario Builder

Just a short note to let you know that I’ve added the ability to import resources directly into the clinFHIR Scenario Builder (people have asked about this for a while). There are 3 formats currently supported:

  • A single Json resource
  • A Json bundle
  • An XML bundle

(Note that a single XML resource is not yet supported – just place it in a bundle if this is a problem right now)

Read more of this post

The FHIR EndPoint resource

In the previous post, we talked about how FHIR could support a provider registry – the resources that would be involved and the types of query that you could use to access data within the registry. I was talking with Brian Postlethwaite (who is one of the authors of these resources, being a co-chair of the Patient Administration committee within HL7) and he pointed out that I didn’t mention the Endpoint resource.

Let’s rectify that.

Read more of this post