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

More on FHIR Logical Models

So a couple of weeks ago I posted on a new component that has been added to clinFHIR – a tool that will generate Logical Models – models of something that uses the FHIR infrastructure but doesn’t generate ‘real’ resources. The idea is that it is used as a requirements gathering tool when when interacting with clinicians to describe what information and processes are needed to meet some interoperability related need.

Since then, we’ve added a few new capabilities to the tool, and also further refined how it can work with the other clinFHIR components to provide an ‘end to end’ solution that starts with an idea, and ends with the various FHIR resources (profiles, valueSets, extension definitions etc) that will be needed. This post starts a ‘mini series’ that describes how this could work (and do note that this is just my idea – there are lots of other ways that this could be done).

Read more of this post

More on server roles

A post I did for Orion Health about server roles in FHIR…