#FHIR R5 Roadmap

Health Intersections

I’ve posted the Roadmap for FHIR R5 over on my FHIR Product Director’s blog

FHIR 57

Health Level Seven International Publishes FHIR Release 4

Electronic Health Reporter

Health Level Seven International (HL7), the global authority for interoperability in healthcare information technology with affiliates in 35 countries, announced that it has published release 4 of the HL7 Fast Healthcare Interoperability Resources (FHIR) standard.

FHIR 60

Understanding #FHIR Patterns

Health Intersections

The FHIR R4 ballot is out (see announcement), and I’d like to draw attention to one part of FHIR that we’ve been working hard on during the preparation of R4: Patterns. In FHIR, we made a specific decision to be as specific as we can get away with. FHIR Patterns.

FHIR 65

#FHIR and the Gartner Hype Cycle

Health Intersections

On a forum for FHIR Foundation members, I raised the subject of where FHIR is on the Gartner Hype Cycle (see Gartner write up , or Wikipedia ). FHIR Foundation member Wes Rishel ( @wrishel ), who’s a FHIR user, and also was a Gartner Analyst before he retired, graciously made this contribution that I could post here. In the last few years I created and positioned a spot for FHIR. FHIR could be at the top of the slope while V2 messages still flow.

FHIR 66

Fast Healthcare Interoperability Resources (FHIR) Explained

Perficient

What is FHIR? FHIR (Fast Healthcare Interoperability Resources) Specification is a standard for exchanging healthcare information electronically. FHIR aims to simplify implementation without sacrificing information integrity. FHIR is suitable for use in a wide variety of contexts – mobile phone apps, cloud communications, EHR-based data sharing, server communication in large institutional healthcare providers, and much more. Why is FHIR Important?

Question: #FHIR Terminology services

Health Intersections

Also, are there any plans to certify HL7 FHIR terminology services? Apelon DTS – open source, and a full blown terminology service that is filling out their FHIR API. Art-Decor – provides FHIR API to the content in art-decor. VSAC – provides some FHIR terminology services for the value sets already in VSAC. Of these, I believe that the most thoroughly tested (at least on the FHIR API side) are Ontoserver and my server. FHIR Question

FHIR 50

#FHIR JSON format questions

Health Intersections

There’s a thread running on chat.fhir.org about the FHIR JSON format. In FHIR, the base types are called ‘primitive types’ – things such as ‘string’, ‘integer’, ‘boolean’ etc. In FHIR, the primitive data types all specialize “Element” which means that they are actually objects with an ‘id’ and extensions. This thread needs some background, so here goes… Background.

FHIR 55

FHIR Prototyping with Node-RED – part 1

HAY on FHIR

As FHIR continues to mature, one of the things we’re seeing is a move away from ‘simple’ data representation Implementation Guides to more complex ones that describe a workflow of some sort. The first is an HTTP node that accepts a GET request to the endpoint ‘/fhir/’.

FHIR 67

Presenting IHE on FHIR at FHIR-DevDays

Healthcare Exchange Standards

I am getting excited to give two IHE on FHIR tutorials at FHIR DevDays in Boston. The FHIR DevDays event is focused on educating IT professionals in the newest standard in healthcare, FHIR – Fast Healthcare Interoperability Resources.

FHIR 56

Active Questionnaires in #FHIR

Health Intersections

FHIR defines a Questionnaire resource that specifies a set of questions for a user, along with a QuestionnaireResponse resource to capture their response. This enables interoperability between the record server and the form filler, but it is not necessary that they are separate, or even that they use FHIR to communicate between them – the form filler can process the FHIR based questionnaire content for whatever form is desired. FHIR Implementation Standards

FHIR 46

#FHIR Medication.Request message data structure analysis

Health Intersections

Here’s a contribution from a FHIR Implementer who says: I think this spreadsheet might be a useful HL7 training resource to understand this significant change from HL7v2 to HL7 FHIR timing.repeat message structure. FHIR ImplementationIndeed, I think it’s pretty useful – so I’m posting it here so implementers can found it by search engine. HL7-Medication-Request-Dose-Timing-Frequencies-with-table-structure-20180704.

FHIR 50

#FHIR and Cancer Patient Empowerment – Mike’s story

Health Intersections

I’m very honoured to make a guest today from Mike Morris, who I met at the HL7 FHIR Applications Round Table in Washington DC a couple of weeks ago. Mike is a cancer patient who is using FHIR improve his own treatment. With FHIR, we can now integrate multiple vendor systems (e.g.,

FHIR 76

#FHIR DevDays comes to Boston

Health Intersections

It’s less than 2 months to FHIR DevDays USA. FHIR DevDays USA 2018, Boston, MA, 19-21 June. When we – that is, the FHIR Community and the people from Firely – used to be Furore – started FHIR DevDays in Amsterdam back in 2014 it was the prime educational event for FHIR in the world. FHIR is a piece of technology that makes people’s job easier and actually more fun.

FHIR 46

#FHIR Baltimore Report

Health Intersections

See over on the official FHIR Product Director’s Blog

FHIR 40

#FHIR on the Hype curve: Follow up

Health Intersections

My recent blog post from Wes Rishel (thanks) got Steve Posnack thinking, and he’s responded with some statistics around adoption of FHIR in USA: Heat Wave: The U.S. is Poised to Catch FHIR in 2019. FHIR StandardsI don’t think that this makes any real difference to Wes’s analysis, but it’s actually pretty exciting – though we still have many problems to resolve.

FHIR 40

FHIR Prototyping with Node-RED – part 2

HAY on FHIR

In part one of this series, we looked at using node-RED to manage notifications using the FHIR Subscription resource for a Use Case where relatives (or other care givers) could be notified when a person is admitted to hospital. This is a FHIR search query, so in our case a value of Encounter?patient={patientId}

FHIR 60

Health Wizz pilots blockchain and FHIR mobile app for EHRs

Mobi Health News

Health Wizz has updated and is piloting its unusual blockchain- and FHIR-enabled EHR aggregator mobile app, which uses blockchain to tokenize data, enabling patients to securely aggregate, organize, share, donate and/or trade their medical records

FHIR 139

Determining the #FHIR version

Health Intersections

We’ve now published 3 FHIR milestone releases, and we’re working towards the 4th. We still haven’t clearly documented how you determine what version of FHIR is in use. Balloting the FHIR infrastructure as normative has forced us to finally come to resolution on this, after much long discussion. The semantics of the mime types, the RESTful URLs, the search parameters, and the overall interaction are bound to a particular FHIR version. FHIR R1 (DSTU 1).

FHIR 50

FHIR patient extensible data portability

Healthcare Exchange Standards

Discussions at FHIR DevDays raised this question of a basic way to leverage FHIR API capability to enable the Patient beyond the limited Apps their provider has approved. If a healthcare provider offers a FHIR API (e.g.

FHIR 60

Clinicians on FHIR

HAY on FHIR

Last week we held our first New Zealand ‘ Clinicians on FHIR ‘ seminar at the HINZ conference in Rotorua. This uses FHIR Logical Models – so an understanding of FHIR datatypes is desirable (though not mandatory).

FHIR 56

IHE on FHIR tutorial

Healthcare Exchange Standards

I will be giving a face-to-face tutorial on the topic of "IHE on FHIR" at both HL7 Workgroup meeting in Cologne, May 12-18 FHIR Dev Days in Boston, June 19-21 So, if you are in Europe, sign up for the tutorial at HL7 workgroup meeting. Here are the IHE profiles that leverage FHIR today.

FHIR 52

Should you use #FHIR resources as your storage format?

Health Intersections

In discussions with implementers, one question that has come up quite a lot recently is whether you should store FHIR resources natively in your database or not. In principle, FHIR resources (like all HL7 specifications) are designed for exchange between systems, rather than as a database storage format. One practical consequence of this is that FHIR resources are highly denormalised, so that granular exchanges are fairly stand alone. FHIR Implementation

FHIR 53

How FHIR is driving the new interoperability

Mobi Health News

Matthew Holt is co-chair of Health 2.0. At the Dev4Health conference in Cleveland on Monday andTuesday, he and Health 2.0 cofounder Indu Subaiya presented their assessment of the drivers of the new interoperability in healthcare.

Shutdown drags on

Morning eHealth

Re-light the FHIR — Research roundup

FHIR 109

FHIR really was positively different

Healthcare Exchange Standards

They had implemented a pilot project using FHIR. Their use-case was to instrument the DoD systems with a FHIR Server API, and similarly instrument a VA Vista system with a FHIR Client. They found that adding a FHIR Server API in the front of the DoD system to be quite achievable.

FHIR 52

GDPR on FHIR

Healthcare Exchange Standards

I just finished a very long week in Cologne at the HL7 workgroup meeting and FHIR Connectathon. I had the idea that I could host a discussion of how to use FHIR in a GDPR compliant organization. So I created a FHIR Connectathon track. This track was hopeful that we could do testing with various parts of the FHIR specification. We ended up talking more about generally how to use the various capabilities that exist in FHIR to meet the various Articles in GDPR.

FHIR 40

Healthcare use of Blockchain on FHIR

Healthcare Exchange Standards

It is better to put pointers (to FHIR Servers) onto the chain. Thus there will be many FHIR Servers that hold your data (might be others than FHIR, but why bother mentioning them). However probably best to presume many FHIR servers. I went to the ONC Interop Forum in DC.

FHIR 63

FHIR documents in XDS

Healthcare Exchange Standards

How does one put a FHIR Document into XDS? How does one find a FHIR Document in XDS? Both of these might still be needed for FHIR Documents. FHIR is more popularly known for the access model using http REST. FHIR has a Document model.

FHIR 52

IHE on FHIR. STU3

Healthcare Exchange Standards

Integrating the Healthcare Enterprise (IHE) has been busy creating Profiles that leverage the new and exciting FHIR specification. These constraints can be coded as a FHIR set of conformance resources.

FHIR 52

FHIR Security initiatives

Healthcare Exchange Standards

I am asked how someone can get engaged with developments in Privacy/Security around FHIR. I am especially encouraging to anyone that has either coding experience, or deployment experience; as I find that too many people engaged in Privacy/Security around FHIR are coming from the theoretical perspective. The drawback at this point is that this seems to be rather USA centric and FHIR centric, although I don't think that is the goal of the community. It is very FHIR centric.

FHIR 40

FHIR Core Extensions

HAY on FHIR

A really short post to record how to download the core extensions in the spec (This came up in a FHIR Chat today). This is particularly useful if you are setting up your own FHIR server and want to pre-load them with the code definitions in the spec. They can be found at: [link]. link]. Just download from the link above, remove the id from the bundle, change the bundle type to ‘batch’ and POST to the root of the server. Thanks Lloyd

FHIR 43

FHIR Walking: Day 2 of Interop Forum

Morning eHealth

More reports on VA turmoil — Lawmakers raise NIH harassment questions

FHIR 81

IHE ITI on FHIR

Healthcare Exchange Standards

IHE ITI has a set of profiles on FHIR existing in Trial Implementation today. These were written against FHIR DSTU2. This profile does rely on creative systems engineering to decompose the documents into the FHIR resources. This might leverage CDA-on-FHIR, or some other methodology. These have been updated to STU3, now in ballot for members of the ITI Technical Committee to comment and vote on.

FHIR 40

#FHIR: Extensible bindings and stating the value set for a code

Health Intersections

FHIR defines an extension to use to state the the value set a Coding was taken from: "coding": [{ "system": "[link] "code": "39065001", "display": "Burn of ear", "extension" : [{ "url" : "[link]. from the FHIR spec ). Note that this advice strictly applies to FHIR. ” is clearly defined in FHIR, and a matter of technical neccessity given how the terminology services and validator are defined and implemented. CDA FHIR v2

FHIR 50

#FHIR and Bulk De-Identification

Healthcare Exchange Standards

Bulk Data Access The addition of a Bulk Data Access in #FHIR was a hot topic at the San Diego workgroup meeting. I have addressed this topic in FHIR before, FHIR does not need a deidentify=true parameter. For #FHIR.

FHIR 52

InterSystems to debut FHIR interoperability sandbox at HIMSS18

Mobi Health News

This year at HIMSS18, InterSystems will be launching a new fast healthcare interoperability resource (FHIR) sandbox, which acts as a virtual testing environment.

IHE on FHIR

Healthcare Exchange Standards

IHE is still relevant in a FHIR world. But FHIR has changed the world, and IHE needs to adjust to this new world. Profiling is still needed The concept of profiling FHIR is still needed. The difference today is that FHIR is ready and instrumented to be Profiled. These mostly are basic profiles, where a basic profile is not a complex profile, one that simply points to a FHIR Resource as the solution for a defined problem.

FHIR 40

FHIR Versions and Conformance URLs

HAY on FHIR

As you probably know, there are a number of ‘conformance’ resources in FHIR that have a unique ‘canonical’ Url that identifies them globally. So how do you accomplish this across different versions of FHIR? This is intended to be a ‘business version’ – i.e. when the contents of the resource change substantially, and is not the same as the FHIR versioning that occurs as resources are updated on a server. So back to FHIR versions.

FHIR 46

Maturing FHIR Connectathon without confusing the marketplace

Healthcare Exchange Standards

Grahame, being the fantastic Product Manager for FHIR that he is, is asking the FHIR community for input on how FHIR Connectathon should evolve. I have also written about how nice it is to see FHIR Connectathon changing.

FHIR 52

Using a FHIR Observation

HAY on FHIR

Just because something was an OBX in v2, that doesn’t mean it should be an Observation or Observation.component in FHIR. In FHIR, Observation and Observation.component have specific purposes: Observation is about information that is being collected/observed. This will not be an issue for systems designed for FHIR, but most healthcare systems will not be for many years, if ever. These are some notes written by Lloyd , Grahame & Eric about using Observation in practice.

FHIR 40