HAY on FHIR

FEBRUARY 17, 2023

So I’ve written an earlier post describing how you can use the excellent HAPI FHIR engine to host your own FHIR server. This used the CLI (Command Line Interface) tool , and has worked well for me in the past – for example most of the clinFHIR modules have used this as the back end storage.

FHIR 68

FHIR 68

Health Intersections

APRIL 6, 2020

Question: Is there a URI form for specifying FHIR versions? For example, ‘ r4.fhir.hl7.org For example, an external system that may not only interact with FHIR servers would need to use that URI to determine that: a) the server to invoke is a FHIR one; and, b) the version is r4.

FHIR 55

FHIR 55

Health Intersections

MAY 22, 2019

I also added this to the ci-build at [link] , so it will be present for all future versions of FHIR. Example: These spreadsheets are to help people who want to do spreadsheet based mapping, as a starting point. . Alternatives: the FHIR Mapping Language MDMI (and see MDHT ) Writing your own code…

FHIR 84

FHIR 84

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

HAY on FHIR

JANUARY 6, 2019

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. Compare, for example the Argonaut data query Implementation Guide with the Argonaut scheduling guide currently in development.

FHIR 73

FHIR 73

HAY on FHIR

MAY 10, 2019

I had an email from a company which had a number of really good questions about exposing data through FHIR, so I thought I’d write a post about it rather than just replying directly as it may be of interest to others (and also gives others the opportunity to disagree with me ). One resource that is not in the diagram above is the Encounter.

FHIR 84

FHIR 84

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 And that’s a real problem.

FHIR 92

FHIR EHR 92

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 69

FHIR EHR Interoperability Health IT 69

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. Conclusion I have rallied against this security theatre against GET.

FHIR 40

FHIR 40

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. The strength of the binding is ‘example’, which means that, actually, any code from any codesystem is allowed. For example, a url value of [link] would indicate that this is a LOINC code.

FHIR 58

FHIR Interoperability 58

Health Intersections

MARCH 28, 2020

In a number of contexts, people are using FHIR in production to make or report on patient appointments. How to represent this in FHIR: Mark an appointment as a virtual appointment. Examples include telephone conference, email exchange, robotic surgery, and televideo conference. it) has co-morbidities that are known risk factors.

FHIR 90

FHIR Telehealth Interoperability 90

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

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

JUNE 17, 2022

This kind of double pointers is discouraged in REST and in FHIR. The main difference from the FHIR core Consent I outlined in my Consent article is that this might be a specific kind of Privacy Consent delegating authority , and the RelatedPerson instance would be indicated specifically in the.provision.agent.

FHIR 40

FHIR 40

Healthcare Exchange Standards

SEPTEMBER 8, 2017

I have been working with some of the teams wanting to do something with Privacy Consent and are coming to the FHIR Connectathon in San Diego. For example: Role Based Access Control (RBAC), or Attribute Based Access Control (ABAC). An example of this is -- SMART-on-FHIR. Another example has been shown as "Cascading OAuth".

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 117

FHIR HIE Interoperability Health Data 117

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

Health Intersections

MARCH 4, 2018

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.

FHIR 52

FHIR 52

Healthcare Exchange Standards

APRIL 27, 2017

IHE is creating many Profiles using FHIR. Given that FHIR is still "Standard for Trial Use" (STU), and thus there is a "Maturity" concern. This maturity concern is communicated in FHIR STU3 through a "FHIR Maturity Model" (FMM) evaluation number on each Resource and other parts. All of which are at FMM level 5.

FHIR 40

FHIR 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. I have addressed this topic in FHIR before, FHIR does not need a deidentify=true parameter. Back then the solution was to add a parameter to any FHIR query asking that the results be deidentified.

FHIR 40

FHIR Public Health 40

Healthcare Exchange Standards

MAY 10, 2017

In FHIR STU3 there are now some common query parameters. Propose using common "patient" query parameter for patient scope With the new FHIR STU3 common shared query parameters , we could identify the specific patient within the Scope. The example with a patient of '[link] patient="[link] or, we could add it to the end.

FHIR 40

FHIR 40

Healthcare Exchange Standards

SEPTEMBER 11, 2017

There were three brave soles willing to try IHE-MHD Profile here at the FHIR Connectathon. They had a specific goal: They wanted to test the IHE-MHD Profile against general purpose FHIR Servers. Specifically FHIR Servers that have not declared IHE-MHD Profile, but which do declare support for the fundamentals that IHE-MHD needs.

FHIR 40

FHIR 40

Healthcare Exchange Standards

JANUARY 30, 2024

For example, the technical standards for encoding a lab result are not fit for patient consumption, but they are key contributors to the human readable report that is given to the patient. Must I record using ATNA or FHIR AuditEvent? Yes: The following commonly used FHIR Servers have BALP implemented within them.

FHIR 44

FHIR EHR Interoperability 44

Healthcare Exchange Standards

AUGUST 16, 2018

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. permissioned chains, or encrypted, etc). So pointers are good, data are bad.

FHIR 51

FHIR 51

HAY on FHIR

OCTOBER 6, 2017

For example, “body position” is not useful when separated from a Blood Pressure measurement. Just because something was an OBX in v2, that doesn’t mean it should be an Observation or Observation.component in FHIR. This will not be an issue for systems designed for FHIR, but most healthcare systems will not be for many years, if ever.

FHIR 40

FHIR 40

Healthcare Exchange Standards

FEBRUARY 25, 2016

Two independent projects this week sent to the FHIR mailing list their diagrams of how they are using FHIR as an API to classic XDS environments. The power of using FHIR as a simplifying API to classic environments. Our project will use FHIR as an abstraction layer for the application. These are great examples.

FHIR 40

FHIR HIE EHR Interoperability 40

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

APRIL 5, 2021

For the example patient aged 2 months, you’re going to need a PRV1 and PCV10. Clicking on the + symbol adds that vaccine to the catchup list and updates the analysis. Basically, you are trying to make the analysis all green – at which point the catch up can be planned.

FHIR 71

FHIR Nursing 71

Healthcare Exchange Standards

NOVEMBER 10, 2021

This new publication is published in HTML form with a full set of conformance resources and examples. This new publication is published in HTML form with a full set of conformance resources and examples. This revision was created using the Implementation Guide publisher. link] Patient Demographics Query for Mobile (PDQm) - Rev.

FHIR 52

FHIR Interoperability Healthcare IT 52

Healthcare Exchange Standards

JANUARY 4, 2016

As FHIR matures, the security topic becomes more and more important. In fact the specification they have " FHIR OAuth 2 " is not open for review, yet. It is made up of a set of strings that represent a few FHIR resources. It is not a complete list of FHIR resource types.

FHIR 40

FHIR mHealth Healthcare IT Public Health 40

Lloyd Price

SEPTEMBER 30, 2023

The project has been successful in developing and implementing a number of standards, including the Argonaut FHIR Data Exchange Standard and the Argonaut FHIR API Standard. The Argonaut Project focuses on the development and implementation of FHIR, a standard for exchanging healthcare data.

Interoperability 64

Interoperability FHIR Leadership Health Data 64

Healthcare Exchange Standards

FEBRUARY 20, 2021

HIE-Whitepaper -- the whitepaper needed to be updated to include the FHIR based models that we have published in the MHD family. This also includes the use of QEDm and mXDE to make FHIR Resource level data available from the shared documents, making consumption more easy. StructureDefinition) and inclusion of examples.

FHIR 72

FHIR HIE 72

Redox

DECEMBER 21, 2023

Here are some specific reflections: FHIR adoption: We missed the mark on our HL7® Fast Healthcare Interoperability Resources (FHIR®) growth prediction. It certainly is growing, but FHIR has not picked up the steam we had hoped for in 2023. We reflected on that in our recap of 2023 FHIR DevDays. Sadly, he was wrong.

Interoperability 59

Interoperability FHIR Digital Health eHealth 59

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 ). Note that this advice strictly applies to FHIR. valueUri" : "[link]. }] }].

FHIR 48

FHIR 48

Healthcare Exchange Standards

JUNE 22, 2016

The Security workgroup is looking at the FHIR datatype for Signature, specifically the use-cases where the one signing is not the one that the agreement or contract is about. For example when a parent signs for an infant child, or a guardian signs for an individual, or where an individual signs for an organization.

FHIR 40

FHIR 40

Health Intersections

OCTOBER 10, 2018

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., Cancer Rears Its Ugly Head.

FHIR 54

FHIR EHR Interoperability 54

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. After that we updated the FHIR specification with a section on being robust to narrative sections. We likely need to update this section to be more on Input Validation with SQL injection and now XXE as examples.

FHIR 40

FHIR Interoperability 40