FUME, a data transformation API factory with native FHIR support, provides mechanisms to convert various source data into FHIR resources and other structured formats. It enables flexible data processing using a mapping language that combines JSONata-based expressions and FLASH via the RESTful API.
This article details the specification for the 'MedicinalProductPharmaceutical' resource in FHIR R4. This resource provides a structured information model for pharmaceutical products, comprehensively defining elements such as identifiers, ingredients, dosage forms, and usage restrictions.
A FHIR Capability Statement is a machine-readable document published by a FHIR server or client that declares which resource types, operations, and profiles it supports. This allows users to programmatically confirm the API contract beforehand.
HRSA has published the 'UDS Plus Insurance Codes' code system for patient-level submission data, released as an FHIR IG v1.0.1. This serves as a starter set to identify various types of insurance, such as Medicaid and Medicare.
ASSYST offers 'FHIR®Break,' a zero-trust API solution enabling secure health information data exchange for enterprise users and subscribers. Built on an open API framework, it provides access to available FHIR resources and aggregate datasets.
A European data standardization project has published the specification for a logical model defining 'Health Professional' within electronic health records. This FHIR-based standard contributes to improving international healthcare data interoperability.
HL7 v2 is a messaging standard that has facilitated data exchange between hospital systems since the late 1980s. It uses a pipe-delimited text format to transmit clinical data—such as admissions or lab results—in near real-time, forming a foundational technology used alongside modern standards like FHIR.
This study developed a standardized questionnaire based on HL7 FHIR to address the challenge of heterogeneous data collection for long-term follow-up of childhood cancer survivors. This provides a reusable foundation that supports not only primary clinical use but also secondary use within the European Health Data Space.
Bricks offers capabilities to build and maintain comprehensive source-to-target schema map registries for B2B data exchange between healthcare systems. It further supports advanced data linkage by utilizing AI/ML for mapping predictions and handling legacy schema elements.
A mobile app was developed to guide patients through medication choices based on symptoms or conditions, performing contraindication and interaction checks. By utilizing a FHIR backend, the app links clinical signals directly to the patient's medical record, aiming to improve adherence.
The open-source JetBrains plugin, "FHIR Toolkit," significantly improves the FHIR R4 development workflow. It aims to eliminate the manual effort of validation and reference resolution that typically occurs when editing JSON in separate tools, allowing all processes to be completed within the IDE.
mock.health has provided a synthetic sandbox environment matching the Epic FHIR structure used by Stanford Health Care. This allows developers to conduct integration testing in an environment closely resembling production.
This article introduces expertise in developing complex healthcare integration systems for highly regulated areas like FHIR R4 and TEFCA QHIN connectivity. The focus is on building robust audit trails, ensuring reproducibility of HEDIS measurement pipelines, and maintaining HIPAA compliance.
Aamako Maya Apps Pvt. Ltd. is transforming Nepal's healthcare system with standards-based digital solutions, aiming to improve public health through data connectivity and decision support. They are building a comprehensive infrastructure that integrates national electronic records and disease surveillance systems.
An EHR partner built a robust FHIR R4 platform to address data exchange challenges across multiple healthcare networks. This achieved comprehensive resource coverage and implemented strict security measures, meeting complex industry requirements.
By utilizing the European Health Data Space (EHDS) and FHIR, it is possible to break down traditional information silos and achieve comprehensive, continuous patient care. This transition is expected to improve diagnosis and treatment planning, while also enabling a shift toward a model where patients actively participate in their healthcare decisions.
EHR development often prioritizes administrative functions and billing requirements over the practical usability and efficiency needed by clinical staff. This structural gap in design is cited as a major contributor to healthcare worker burnout.
The FHIR-native backend, Fire Arrow, supports compliance with Germany’s Digital Healthcare Act (DiGA). It excels by meeting strict security and interoperability requirements demanded by the BfArM, particularly regarding authentication, authorization, and adherence to domestic profiles like ISiK/KBV.