Health Intersections

SEPTEMBER 4, 2018

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.

FHIR 79

FHIR EHR Interoperability Health IT 79

HAY on FHIR

MAY 8, 2019

At the recent Working Group Meeting in Montreal, I participated in the ‘v2 to FHIR’ stream – focused on how can the HL7 community give advice to implementers about converting v2 messages into FHIR bundles. To actually process (convert to FHIR) a message, click the ‘Convert’ button to the upper right.

FHIR 69

FHIR 69

Health Intersections

MAY 20, 2019

It’s a common thing for implementers to want to do with FHIR: connect to a FHIR server, and make a local copy of the information provided by the server, and then check back occasionally with the server for updates – that is, new resources, or changes to existing resources. (In “I never took X”).

FHIR 99

FHIR EHR 99

Health Intersections

APRIL 13, 2018

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. Specific vs General.

FHIR 51

FHIR 51

Healthcare Exchange Standards

MAY 18, 2018

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.

FHIR 56

FHIR 56

HAY on FHIR

SEPTEMBER 24, 2017

As you probably know, there are a number of ‘conformance’ resources in FHIR that have a unique ‘canonical’ Url that identifies them globally. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this structure definition is (or will be) published. So back to FHIR versions. For ValueSet.

FHIR 49

FHIR 49

Healthcare Exchange Standards

APRIL 10, 2018

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. If you are in the USA, sign up for the tutorial at FHIR Dev Days.

FHIR 67

FHIR EHR 67

HAY on FHIR

AUGUST 31, 2017

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].

FHIR 45

FHIR 45

HAY on FHIR

MARCH 29, 2021

Looking at the proposal for the next version of FHIR (R5) it is multiple, but we can’t use that yet. The ‘plan definition’ extension specifies the url and value explicitly, while the ‘disease covered’ uses a named extension. These were: planDefinitionUrl. diseaseCovered.

FHIR 105

FHIR 105

HAY on FHIR

FEBRUARY 9, 2020

I was trying to remember how to represent family relationships in FHIR – to record that one person is related to another, maybe a mother / daughter relationship, assuming that each person is already represented by a Patient resource. The following are the overall steps I followed. Install sushi. See the online instructions.

FHIR 75

FHIR 75

HAY on FHIR

MAY 31, 2019

So a little while back I wrote about an app I developed during the WGM Connectathon to send an HL7 v2 message to a converter app, and display the response (a FHIR Bundle ) in a number of visualizations after validating it using the community supplied validation tool (actually, exposed by the reference servers via the $validate operation).

FHIR 66

FHIR Primary Care 66

Healthcare Exchange Standards

AUGUST 29, 2017

Integrating the Healthcare Enterprise (IHE) has been busy creating Profiles that leverage the new and exciting FHIR specification. IHE publishes their profiles on [link] IHE subset of Profile on FHIR can be found on the IHE wiki FHIR list An IHE Profile is equivalent to a FHIR Implementation Guide.

FHIR 66

FHIR Interoperability Public Health EHR 66

HAY on FHIR

MAY 25, 2021

We spent a bit of time in the last post describing why we want to have data coded, how FHIR supports coded data – especially the external terminologies where the concepts are defined – and described some of the RESTful API calls that we could make to retrieve specific Observations and DiagnosticReports from the repository.

FHIR 68

FHIR 68

Healthcare Exchange Standards

JUNE 22, 2022

I got a Question: Can you address a specific example of the intersection of FHIR standards and OWASP guidance? The FHIR spec allows for sensitive ids such as patient identifier to be used on the query string when searching for a patient. OWASP is fantastic resource. Everyone should use it.

FHIR 40

FHIR 40

HAY on FHIR

NOVEMBER 6, 2017

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). Finally the actual FHIR Conformance artifacts can be generated.

FHIR 45

FHIR Interoperability 45

Healthcare Exchange Standards

MAY 1, 2017

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. This methodology is not specified.

FHIR 40

FHIR 40

Healthcare Exchange Standards

MAY 4, 2023

This conversion enabled better and more comprehensive definition of the Provenance linkage between the derived FHIR clinical Resources and the source documents from the HIE. This Provenance definition is now in mXDE along with examples and requirements CapabilityStatement.

FHIR 119

FHIR HIE Interoperability Health Data 119

Health Intersections

JULY 17, 2018

FHIR defines a Questionnaire resource that specifies a set of questions for a user, along with a QuestionnaireResponse resource to capture their response. This extension says that the form filler takes a parameter which is a FHIR Patient resource. A variable has a name, and a value which is a list of resources or FHIR types.

FHIR 46

FHIR Interoperability 46

HAY on FHIR

MAY 24, 2021

Before we start thinking of the specifics of coding in lab tests, a quick review of coded data in FHIR in general is probably a good idea. It can represent an external terminology such as LOINC or SNOMED, or can contain the actual definition of the concepts directly. This is a common pattern in the FHIR core spec.

FHIR 58

FHIR Interoperability 58

Healthcare Exchange Standards

MAY 9, 2019

This is an update of what is going on in Security and Privacy in, and around, the FHIR specification. This is an update of what is going on in Security and Privacy in, and around, the FHIR specification. GDPR driven activities: The Security WG has done an assessment of FHIR in the context of GDPR.

FHIR 40

FHIR HIE Health Information 40

Healthcare Exchange Standards

NOVEMBER 7, 2023

This winter quarter will be a lighter load, recognizing the holidays: Patient Scheduling, prospective look at FHIR R5/6, and evaluating impact of Gender Harmony. The Non-Patient File Sharing (NPFS) Profile defines how to share non-patient files such as clinical workflow definitions, domain policies, and stylesheets.

FHIR 72

FHIR HIE Health Information 72

Healthcare Exchange Standards

MAY 29, 2016

Much discussion around consent (Privacy) in HL7 FHIR. FHIR should focus on only what systems do today, not what we want them to do. FHIR should put into common extensions those things that we want them to do (e.g. If we can agree on this, then the role of FHIR in capturing consent would be immensely clearer.

FHIR 40

FHIR Interoperability Nursing 40

Healthcare Exchange Standards

JANUARY 10, 2017

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. There is also a workgroup creating transforms from/to CDA -- CDA on FHIR.

FHIR 40

FHIR HIE Health Information Interoperability 40

Health Intersections

MAY 31, 2018

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 ). btw, If we could go get the definition of [link] we could validate the code against that too.

FHIR 51

FHIR 51

Healthcare Exchange Standards

DECEMBER 18, 2017

I have been pushing IHE to add FHIR conformance resources to their publication mechanism. I now have published the full set of FHIR conformance resources for PDQm and MHD profiles. FHIR conformance resources are available to carry programatically the constraints that historically IHE has written narratively into an IHE Profile.

FHIR 40

FHIR Interoperability 40

Healthcare Exchange Standards

SEPTEMBER 27, 2017

Bulk Data Access The addition of a Bulk Data Access in #FHIR was a hot topic at the San Diego workgroup meeting. Which is not a definition of a use-case. I have addressed this topic in FHIR before, FHIR does not need a deidentify=true parameter. This effort would best be done as the FHIR resources approach maturity.

FHIR 40

FHIR Public Health 40

Healthcare Exchange Standards

JANUARY 24, 2017

This means that when I attended the FHIR Connectathon 14, prior to the HL7 Workgroup Meeting in San Antonio TX , I was shocked to experience the new FHIR Connectathon. The others from the FHIR core-team have seen the changes over-time, so the transition is not as shocking as it was for me. FHIR has matured, it is growing up.

FHIR 40

FHIR 40

HAY on FHIR

APRIL 5, 2021

So we’ve talked about how to represent an immunization program both in the abstract (the overall definition of a national plan) and the specific (the plan applied to an individual). In addition, we discussed how to submit the actual administrations to the registry.

FHIR 71

FHIR Nursing 71

Healthcare Exchange Standards

MAY 13, 2016

There is renewed discussion, much like back in January, around the need to go beyond testing just the FHIR Resource 'interoperability'. A 'system' in the broadest of definitions. This reference system needs to pick a minimum-useful set of FHIR resource centric workflows. This is more than just a selection of FHIR Resources.

FHIR 40

FHIR Interoperability HIE Leadership 40

Healthcare Exchange Standards

JANUARY 18, 2015

I have been asked quite often to explain how to secure FHIR. The basics of Security for FHIR are written up on the FHIR Specification. Don’t worry about security The first answer is the one I give to those in HL7 that are working on developing FHIR, or just getting their feet wet learning FHIR. Not too big.

FHIR 40

FHIR mHealth 40

Healthcare Exchange Standards

MARCH 4, 2016

Rene asked for an outline of Security topics for FHIR for an upcoming tutorial he is giving. The easy answer is go read all my blog articles under the #FHIR topic The second easy answer is to point at the FHIR security pages. There are efforts underway to create a Privacy Consent Directive modeled in FHIR.

FHIR 40

FHIR mHealth 40

HAY on FHIR

APRIL 11, 2021

This is actually part of a project I’ve been working on for a little while – learning FHIR with clinFHIR – so it’s a perfect time to be doing it. The idea for clinFHIR started shortly after FHIR started to gain prominence within HL7 – coming up to 10 years ago now.

FHIR 68

FHIR Primary Care 68

Healthcare Exchange Standards

APRIL 20, 2016

Updated: Vadim Peretokin advises on the FHIR chat : You're better off in the world if you know about this stuff though. Specifically, with regard to the java reference implementation, it has always ignored DTD definitions, so is immune. Any newly released versions will change to stop ignored DTD definitions, and report an error.

FHIR 40

FHIR Interoperability 40

Healthcare Exchange Standards

FEBRUARY 27, 2021

Something supported by IHE Document Sharing (XDS/XDR/XDM/XCA/MHD), something enabled and using #FHIR. I use "document", with a lower-case "d", when I am referring to an object that meets the Internet's definition of a document. Everything else in the Bundle is just FHIR Resources. When is a Document a Document?

FHIR 81

FHIR HIE 81

HAY on FHIR

DECEMBER 13, 2019

So I’ve just been at the FHIR devdays in Amsterdam which was really interesting (of course – attending a devdays is a ‘must do if possible’ for FHIR implementers). Note also that I’m using the term ’message’ to indicate the input and output – not a Message in the FHIR sense. The firely approach uses 2 operations.

FHIR 84

FHIR 84

HAY on FHIR

JANUARY 23, 2020

The 23 rd FHIR connectathon in Sydney is almost upon us, and despite the trials and tribulations that the weather has thrown at us, it’s going to be a great event with over 150 people currently scheduled to attend. For myself, I’m going to participate in the FHIR shorthand track. In keeping with the FHIR ethos, the Mitre corp.

FHIR 123

FHIR Primary Care 123

HAY on FHIR

DECEMBER 16, 2019

In the previous post , we described a simple application to help develop transformation maps conformant with the FHIR mapping language. Determine the output format and create any models needed (this is not required if we’re going to use the standard FHIR types – which we will do in this case). Creating the source definition.

FHIR 59

FHIR 59