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

New UI for clinFHIR

If you’ve used clinFHIR in the last 24 hours then you’ll have noticed a new User Interface. This is a recognition that clinFHIR is now really a number of ‘co-operating’ modules rather than a single application, so the previous UI wasn’t really the best any more.

In this post I’ll describe the UI (Actually I call it a ‘Launcher’ as it’s really a start point for the various modules).

Read more of this post

Scenario Builder: Library and Documents

In the last post we talked about the new builder component that was developed to help people (especially clinicians) develop sets of resources to represent clinical scenarios. There are a couple of features we didn’t have time to discuss then – the Library and Documents – so let’s talk about them now.

Read more of this post

Building a set of resources in FHIR

One of the primary goals for clinFHIR is to help people who are new to the standard understand how it works – and increasingly these are clinicians whose interest is less in the technology and more about how FHIR can be used to represent the clinical information they wish to exchange.

While the current app does allow this, it has been aimed more at the people actually developing the resources than the casual user, and so can be time consuming to develop sets of resource instances that represent real world scenarios.

The component described by this post (called a simple builder – though a better name is needed!) is intended to allow someone completely new to FHIR to build sets of resources that represent clinical scenarios, to help them understand how the resources can be linked together – rather like Lego is used to build a complete model.

Read more of this post

Using workflow to track comments

So there’s a requirement that’s come out of the UK profiling work (among others) to be able to gather comments about logical models as part of getting feedback – particularly from Clinicians.

Read more of this post

Basic Pregnancy Logical Model

So there was an interesting conversation in the FHIR chat just recently about representing maternity information in FHIR. It was pointed out by Lloyd that some elements that seem simple – like the LMP (Last Menstrual Period date) – are actually more complex than that, they are more properly Observations made by someone, at some date, with a degree of certainty etc.

So what this means is that a single logical model – like a summary of pregnancy – is going to wind up being represented in FHIR by a number of different resources, presumably ‘bound together’ in some way (eg  a bundle of some sort Document/Message – or just a Composition with appropriate references) and described by an Implementation Guide.

Given that I’m working on a logical modeler in clinFHIR, this seemed like something to address. Here’s where I’ve got to so far.

Read more of this post

clinFHIR Profiling Walk Through

So I’m in the middle of getting ready for the Furore  devdays event – part of the preparation being a writing series of posts on the various stages we’ll be exploring as part of that event.

Quite co-incidentally, Mark Braunstein from Georgia Tech asked me to do a presentation for their FHIR class which is happening in a couple of days, so I thought it a good idea to write this walk through of the complete process from end to end – from a requirement to a profiled resource instance.

We’ll return to the more detailed consideration of the steps after this.

Read more of this post