Why Hospitals Still Can't Exchange Data, and What HL7 FHIR Has to Do with It
Imagine: a patient gets tests at one clinic, undergoes examination at another, and a doctor at a third sees neither the results nor the medical history. It would seem we're in the 21st century, with digital technology everywhere, but interoperability in healthcare remains one of the most complex challenges. According to the ONC (Office of the National Coordinator for Health IT) report published in 2021–2023, most U.S. hospitals use EHRs (electronic health records), but full-fledged data exchange between different systems is still limited. And the reason is not only regulation but also the diversity of standards: HL7 v2, HL7 FHIR, DICOM, IHE profiles — each solves its own problem, and without a systematic understanding, it's easy to get lost in this labyrinth.
That's why the course "Medical Informatics and HL7 FHIR" on the asibiont.com platform is not just a theoretical primer but a practical guide to modern healthcare data exchange standards. It's designed for those who want to understand how integrations in healthcare are structured, why FHIR R4/R5 is gaining momentum while HL7 v2 and DICOM remain in demand, and how regulatory requirements (ONC, CMS, EHDS) influence development.
In this article, I'll talk about what the course teaches, how learning on asibiont.com is structured, who it will benefit, and why the format with AI-generated lessons is not hype but a real way to master a complex topic.
What Is HL7 FHIR and Why It's Been Talked About for Ten Years
HL7 FHIR (Fast Healthcare Interoperability Resources) is a healthcare data exchange standard developed by HL7 International. The first version (DSTU 1) appeared in 2014, and starting with R4 (2019), the standard became stable and gained widespread recognition. FHIR uses modern web technologies: REST API, JSON, XML, OAuth 2.0. FHIR resources (Patient, Observation, Condition, MedicationRequest, and others) describe clinical entities and allow data exchange between systems via simple HTTP requests.
For comparison, HL7 v2 (the second version of HL7) is an older standard that appeared in the late 1980s. It is still widely used in hospitals, especially for transmitting messages between laboratory systems, radiology information systems (RIS), and EHRs. However, v2 has drawbacks: lack of a strict data model, variability in implementation, and parsing complexity. DICOM (Digital Imaging and Communications in Medicine) is a standard for exchanging medical images, used in PACS (Picture Archiving and Communication System) and modalities (MRI, CT, ultrasound).
The course "Medical Informatics and HL7 FHIR" covers all these standards, but with an emphasis on FHIR and its role in modern interoperability. You will learn to work with FHIR resources, understand how to build REST API requests, master SMART on FHIR for application authorization and CDS Hooks for clinical decisions. The program also includes IHE profiles (XDS, PIX, PDQ), medical terminologies (SNOMED CT, LOINC, ICD-10, RxNorm), and regulatory frameworks (US Core IG, ONC, CMS, EHDS).
What Exactly the Course Teaches: Skills and Knowledge
The course program is designed so that the student gains not scattered facts but a holistic picture. Here are the key topics:
- HL7 v2: message structure (ADT, ORM, ORU), segments, fields, encodings. You will analyze real message examples and learn to read them.
- HL7 FHIR R4/R5: resources Patient, Observation, Condition, MedicationRequest, Encounter, and others. You will study REST API, search, operations, extensions, profiling.
- DICOM: tags, services C-STORE, C-FIND, C-MOVE, working with PACS. You will understand how images are transmitted and how to link them to EHR via FHIR ImagingStudy.
- IHE profiles: XDS (Cross-Enterprise Document Sharing), PIX (Patient Identifier Cross-Referencing), PDQ (Patient Demographics Query). These are standards for document exchange and patient identification.
- Medical terminologies: SNOMED CT (clinical terms), LOINC (laboratory and clinical observations), ICD-10 (diagnoses), RxNorm (medications). You will learn to use them in FHIR resources.
- SMART on FHIR and CDS Hooks: how to create applications that securely connect to EHR, and how to embed clinical guidelines into a doctor's workflow.
- US Core IG and regulatory frameworks: requirements of ONC (21st Century Cures Act), CMS (Interoperability and Patient Access Rule), EHDS (European Health Data Space). You will learn how to comply with regulations.
Each topic is reinforced with practical assignments: for example, forming a FHIR request to a server, parsing an HL7 v2 message, setting up a DICOM C-FIND request. This is not abstract theory but skills that can be immediately applied in projects.
How Learning on asibiont.com Is Structured
The asibiont.com platform uses AI generation of personalized lessons. This means that a neural network creates educational material for a specific student, taking into account their level, goals, and previous experience. You don't go through a fixed program with the same lessons for everyone — instead, AI builds an individual trajectory. If you are already familiar with HL7 v2 but know nothing about FHIR, the course will start with FHIR. If you are a developer but haven't encountered medicine, AI will add more context about clinical processes.
Learning is entirely text-based: no video lessons, webinars, or podcasts. This is done so that you can learn at a convenient pace, return to difficult parts, copy code examples, and immediately try them in practice. Access to materials is 24/7; you choose the time and duration of classes.
AI doesn't just output text but also explains complex concepts in simple language. For example, if you don't understand how Observation differs from Condition, AI will provide analogies and examples. If you need to understand SMART on FHIR, AI will generate a step-by-step guide with real scenarios. However, AI does not respond in chat in real time — it generates lessons and assignments that you complete independently. It's important to understand this: the format does not involve interactive dialogue with the neural network, but the material is adapted to you.
Why AI Learning Is Modern and Effective
Traditional courses in medical informatics often suffer from two extremes: either too academic and detached from practice, or superficial and lacking depth. AI generation of lessons solves this problem. The neural network analyzes your progress and adjusts the program: if you quickly master the FHIR REST API, it will move on to more complex topics (e.g., profiling and validation). If something causes difficulties, AI will offer additional explanations and examples.
Moreover, AI can explain complex topics in simple language. For example, the concept of interoperability is often described abstractly, but AI will generate a specific case: how hospital A transmits test results to hospital B via FHIR API, which resources are used, how errors are handled. This helps not just memorize but understand the logic.
Another advantage is personalization for the goal. If you are preparing for an interview for an integration engineer position, AI will focus on practical tasks and typical questions. If you are a doctor who wants to understand how EHRs work, AI will add more clinical examples. This approach saves time and makes learning meaningful.
Comparison of HL7 v2, FHIR, and DICOM: What and When to Use
To understand the value of the course, it's useful to see the difference between the standards. Here's a brief table:
| Standard | Year of Appearance | Main Purpose | Format | Where Used |
|---|---|---|---|---|
| HL7 v2 | late 1980s | Message exchange (ADT, ORU, ORM) | ER7 (pipe-delimited), XML | Hospitals, laboratories, RIS |
| HL7 FHIR | 2014 (DSTU 1), R4 — 2019 | Resource exchange via REST API | JSON, XML, Turtle | Modern EHRs, mobile apps, APIs |
| DICOM | 1985 (ACR-NEMA), 1993 — DICOM | Medical image exchange | Binary, with tags | Radiology, PACS, modalities |
HL7 v2 remains dominant in hospitals for internal data transmission, especially in the U.S. According to the ONC "Hospital Interoperability" report (2021), most hospitals use HL7 v2 for message exchange. However, FHIR is being actively implemented due to CMS and ONC requirements: since 2021, CMS requires health plans to provide access to data via FHIR API (Interoperability and Patient Access Rule). This incentivizes EHR vendors such as Epic, Cerner, Allscripts to add FHIR endpoints.
DICOM remains indispensable for images. But integrating DICOM with FHIR (via the ImagingStudy resource) is a new area that allows linking radiological studies with clinical data. The course teaches exactly how to do this.
As for the cost of integrations, according to expert estimates, developing interfaces on HL7 v2 can be expensive and labor-intensive due to variability in implementations. FHIR lowers the entry barrier through standardized REST APIs and ready-made libraries. However, the transition does not happen instantly: many systems will support both standards for a long time.
Regulatory Frameworks and Their Impact on Developers
The course pays great attention to regulatory requirements because they directly influence which technologies are in demand. In the U.S., these are:
- ONC (Office of the National Coordinator for Health IT): develops rules for EHR certification, including requirements for FHIR API (US Core IG).
- CMS (Centers for Medicare & Medicaid Services): Interoperability and Patient Access rules (2020) and Interoperability and Prior Authorization (proposed in 2022). They obligate health plans and hospitals to provide data via FHIR.
- EHDS (European Health Data Space): a European initiative that also relies on FHIR for data exchange between countries.
These regulations create demand for specialists who can work with FHIR, SMART on FHIR, and US Core IG. The course helps understand how to comply with these requirements: which resources are mandatory, how to pass certification, which profiles to use.
Who Will Benefit from the Course
The course "Medical Informatics and HL7 FHIR" on asibiont.com is suitable for:
- Developers who want to enter the medical field or already work with EHRs and need a systematic understanding of standards.
- IT specialists in clinics responsible for integrations, data migration, and interface setup.
- Analysts and product managers in HealthTech who need to understand technical limitations and capabilities.
- Doctors and healthcare professionals interested in how digital systems are structured and how data travels between institutions.
- Students of medical and IT specialties planning a career in medical informatics.
If you want not just to hear the terms "FHIR" and "interoperability" but to be able to apply them, this course will provide the necessary foundation.
Forecast to 2030: What Will Happen with HL7 v2, FHIR, and DICOM
Judging by current trends, by 2030 FHIR will become the main standard for new integrations. However, HL7 v2 and DICOM will not disappear: they will continue to be used in legacy systems. The share of FHIR is expected to grow due to regulatory requirements and the development of SMART on FHIR. DICOM will remain the standard for images, but integration with FHIR via ImagingStudy will become more widespread.
Developers and IT teams in clinics should already invest in learning FHIR to be ready for the transition. The course on asibiont.com helps do this systematically and without unnecessary theory.
Practical Takeaways
- FHIR is not a replacement for HL7 v2 but a complement. In the coming years, many systems will support both standards.
- SMART on FHIR and CDS Hooks are key technologies for creating applications embedded in EHRs.
- Regulatory frameworks (ONC, CMS, EHDS) stimulate FHIR adoption, so knowledge of US Core IG is essential for working in the U.S. market.
- DICOM remains important for working with images, but integration with FHIR opens new possibilities.
- Practice is more important than theory: the course provides assignments that help reinforce skills.
If you want to master these topics, start learning on asibiont.com. The course "Medical Informatics and HL7 FHIR" will help you understand the standards, grasp regulatory requirements, and gain practical skills that employers value. Follow the link Medical Informatics and HL7 FHIR and start learning today.
Sources:
- HL7 FHIR Specification: https://hl7.org/fhir/
- ONC Health IT: https://www.healthit.gov/
- CMS Interoperability: https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability
- DICOM Standard: https://www.dicomstandard.org/
- IHE International: https://www.ihe.net/
Comments