Katya Samardina

Why is it important for Clinicians to become actively involved in FHIR®?

February 10, 2017

WHAT IS HL7 2 - stockfresh 9674474 modern-medical-technology-system-and-devices sizeXS-min

The HL7® FHIR® standard is evolving to the point where it is feasible – if not necessary – for clinicians to become actively involved in FHIR®.

HealH® has educational resources – there is aFHIR® fundamentals course for example.

  1. Engaging with the FHIR® community (which is extremely vibrant!).
    • Joining your local HL7® Affiliate is always a good start. These are the folk with a good understanding of all HL7® standards, including FHIR®.
    • The HL7® Patient Care committee is the group responsible for the clinical resources.
    • There is a FHIR® chat where you can get questions answered in near real-time, and all previous conversations are available for searching.
  2. Doing is using tools like clinFHIR and forge to actually build FHIR® artifacts. clinFHIR in particular is aimed at the clinical user and has a distinctly educational focus, whereas forge is intended as a functionally complete profiling tool for production use.

It is very important for clinicians to become actively involved in FHIR® and health IT projects will benefit from having end users involved earlier in the process.

Related Blogs

InteropNOW Podcast Michelle Blackmer Q&A

Michelle Blackmer

Q&A: Data interoperability and the future of health IT

Read more

Stephan Rubin

Do doctors really care about interoperability? … and other insights from Day 2 of ViVE2022

A session from ViVE Day 2, The Complicated Convergence of Clinical and Claims Data, evolved into a conversation about how challenges in interoperability are secondary to challenges in care delivery,

Read more
Lyniate_Rapid_illustration_api_gateway_manager (1)

Lyniate Team

Lyniate introduces Rapid, a healthcare API gateway

Rapid is a healthcare API gateway and manager designed to help health teams create and safeguard APIs, including Fast Healthcare Interoperability Resources (FHIR)-based APIs like those required by the CMS Interoperability and Patient Access Rule.

Read more