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

Provider registries in FHIR

So we’ve had some interest in New Zealand concerning Provider registries – locations where the details of providers and the services they provide can be maintained and discovered. There are a lot of potential uses for such a registry, but the two that we’ve been discussing are locating targets for referrals, and locating providers by specialty as part of Care Pathways.

Typical query use cases could include:

  • Find a Provider by name (or other personal detail)
  • Find a Provider by specialty – eg a physiotherapist
  • Locate a Service provided by a facility like a hospital

There are lots more of course, but these will get us started.

Read more of this post

Building a profile in the new clinFHIR

So I had a question from someone who was wanting to develop some profiles using clinFHIR and not sure of the best way to approach this. I’ll write in more detail later on, but as there has been a substantial change in process and User Interface from the previous version, I thought I’d just do a quick post about how the new process is intended to work.

Read more of this post

clinFHIR and the CodeSystem resource (STU-3)

As you’ll probably be aware, a lot of my focus in recent months has been in updating clinFHIR to help non-technical folk like clinicians understand what FHIR is, and how they can get involved in FHIR related projects. Here’s a White Paper I did for Orion Health on the subject…

There are a couple of core components that have been developed to assist this.

Read more of this post