There are many videos available for free, that would let you learn about FHIR.
But where to start ?
After watching some videos about FHIR you may easily end up feeling even more confused, if you do not learn the basics or simply watch content that is too deep at first.
I'm giving brief explanations below with the intent of presenting this in a very simple language. If you can refer and learn from the FHIR specification itself that's the best source.
Due to the "gap" in knowledge levels of software and medical professionals, the way to start learning FHIR varies. Therefore, contents are targetted with this in mind.
(software engineer, developer, programmer, QA engineer, IT manager, IT consultant, business analyst etc)
Since FHIR involves technical details that can be easily related and used in the software profession (eg: REST APIs, JSON/XML), most of the software professionals find it quite easy to grab.
At the same time, when it comes to real-life application they find it difficult to map entities as they lack the medical domain background on what happens in different clinical scenarios. So learning hand-on
could be a quick way to get started, followed by an understanding on how FHIR mapping is done to solve problems in real-life situations.
(doctor, nurse, consultant etc)
I suggest you first look at how FHIR solves practical problems in the medical domain you are already familiar with (eg: How mobile health apps use FHIR to share health data across hospitals),
before getting hand-on with too many technical details. The contents are ordered with this in mind, where it presents some IT concepts before learning FHIR.
There are many Electronic Health Record(EHR) software out there, which stores data in their own formats. So when a patient moves from one hospital to another, how can we see patient history data ? Simply put, a standard method is needed to communicate across software and exchange medical data seamlessly. That's where FHIR comes in, together with many other terminilogy standards like ICD, SNOMED, LOINC etc.
source: www.medicalbillersandcoders.com : The Evolution of Interoperability in Healthcare
HL7 v2 is a format based on values seperated by delimiters and collection of values grouped into sections.
Here is an example HL7 v2 message:
source: www.sciencedirect.com/
This shows both HL7 v2, v3 with FHIR. Since HL7 v2 has been the only widely used standard for some time (before FHIR was introduced), we see the term "HL7" being used to mean "HL7 v2". For eg, there are job opportunities mentioning "you need to know about HL7 and FHIR", where HL7 is actually an organization. What it means here is HL7 v2 in most cases.
source: lyniate.com : Versions of the HL7 Standard
This is a good article on summarizing all these standards.
How HL7 standards were improved over time with additional features:
http://sil-asia.org : Exploring HL7 Standards
Here is a sample HL7 v2, CDA and FHIR messages contianing the same data:
Clinical Document Architecture(CDA) is an XML based standard.
According to this article:
The HL7 Version 3 Clinical Document Architecture (CDA) is part of the HL7 V3 with a focus on the actual clinical documents. CDA is a document markup standard that specifies the structure and semantics of “clinical documents” for the purpose of exchange between healthcare providers and patients. It defines a clinical document as having the following six characteristics:
1) Persistence
2) Stewardship
3) Potential for authentication
4) Context
5) Wholeness and
6) Human readability
By the time this article was written (January 15, 2020), these are the current usage of HL7 technologies around the world.
In terms of usage, currently, HL7 CDA is still the leading data exchange standard in the world. It has already surpassed HL7 V2 during the early 2010’s. HL7 FHIR is the leading draft standard, and upon its adoption by countries and corporations, it is projected that FHIR will exceed CDA before 2020. This is accepted since HL7 FHIR has been very useful (most useful) for digital health implementers and developers, as they are the once who first accepted this technology. Rose Ann Zuniga says in her article
2.1. ePreop Cerner FHIR Enabled App (video embedding disabled)
2.2. Apple Is Going After The Healthcare Industry, Starting With Personal Health Data
2.3. InterSystems: iOS, FHIR and IRIS for Health : How they communicate
Going through these videos will give you a good foundation before you start hearing about many technical words and feel confused. Having a good understading of these is a must to proceed and practically use the FHIR specification.
This huge list of content in Confluence has a comprehensive list of FHIR servers that are publicly available for testing. As of now, there are 30+ public servers, which you can start using.
https://confluence.hl7.org/display/FHIR/Public+Test+Servers