When applications access a patient's health record, granular control is required, not just a simple access grant. This article explains the technical steps to implement scope control in a FHIR API, based on the SMART on FHIR authorization model, combining resource type, access level, and patient context.
The FHIR Foundation announced that registering FHIR implementations is optional and currently not possible. However, all public implementation guides must be placed in the Implementation Guide Registry.
Governments worldwide are shifting AI healthcare from unregulated technology use to formal institutional governance. The EU classifies clinical diagnosis as "high-risk" under its AI Act, the US mandates safety data sharing, and Taiwan's Ministry of Health and Welfare is standardizing FHIR and establishing a center for "Responsible AI" to ensure legal accountability and traceability.
The article guides developers on building a FHIR-ready API using ASP.NET Core and C#. It explains that FHIR standardizes the exchange of diverse healthcare resources, such as patient demographics and clinical observations, ensuring interoperability between various clinical systems.
Imperva Threat Research identified new remote Denial-of-Service (DoS) vulnerabilities in GraphQL Java, a widely used library. This vulnerability occurs in the early stages of the processing pipeline, independent of the schema, potentially affecting healthcare systems using HL7 FHIR.
This article defines the standardized CodeSystem `reason-medication-given`, which is used to categorize the reason for medication administration. The system standardizes the documentation of whether the medication was given due to an ordered protocol, an emergency, or if the reason was unknown.
Apple provides detailed procedures for healthcare organizations to maintain and update their registration details and technical integrations (FHIR APIs) within its Health Records and data sharing platforms. This covers updating contact details, brand information, and managing FHIR endpoints.
This article details the architecture of secure, compliant data platforms built on Google Cloud for healthcare providers in regions like Australia and Singapore. It outlines advanced technical approaches to maintain patient data sovereignty while ensuring FHIR interoperability and managing complex multi-jurisdictional compliance.
Naveen Raj developed a FHIR-based healthcare backend. This platform provides structured relational models and REST APIs for core clinical resources, ensuring clinical data remains queryable.
The MedLog protocol defines the information that should be recorded at each invocation of a medical AI model. By leveraging existing open standards such as W3C PROV, FHIR, and OpenTelemetry, it achieves scalable and vendor-agnostic data exchange.
WaslMed provides the Cura Platform's Integration Hub, a standards-based solution designed to overcome data silos. It utilizes major standards like HL7 and FHIR to connect diverse systems, including government portals, banks, and messaging channels, achieving comprehensive ecosystem integration.
ApexSutra outlines a reference architecture for telehealth platforms. The design emphasizes separating the audit trail into an append-only log, ensuring clinical notes persist independently of video calls, and utilizing a translation layer to map FHIR R4 resources into an internal domain model.
The OCL Terminology Service offers a REST API-based solution for standardizing and exchanging health data, enabling the management of code systems, value sets, and mappings using FHIR standards.
This article introduces an online viewer capable of displaying complex medical dataβincluding XML, ZIP, FHIR, and CDAβin an easily readable format directly within the browser. This capability helps overcome the barriers of specialized data formats, making information accessible to patients and clinicians alike.
FHIR introduces Topic-Based Subscriptions to solve the inefficiency of constant data polling. This pattern allows systems to receive real-time notifications when specific medical resources or events change, significantly improving interoperability efficiency.
This comprehensive guide helps hospital buyers evaluate integration partners. It presents specific questions across six critical areas, including message exchange (HL7 v2, FHIR), API definition, integration layer ownership, clinical safety assurance, and long-term operational support.
This article details a robust integration design for mapping HL7 v2 messages to FHIR R4 resources. The system addresses the fragility of point-to-point feeds by separating transport, parsing, and mapping, ensuring data integrity and traceability.
CapMinds is a healthcare technology company that helps organizations build secure, connected, and AI-ready digital ecosystems. They specialize in EHR/EMR modernization, HL7/FHIR interoperability, healthcare APIs, and AI-driven solutions.
AeHIN and HL7 International launched the second FHIR Fundamentals Course cohort in the Asia-Pacific region. This cohort brought together 109 participants from 10 countries, aiming to strengthen regional capacity in health information standards and interoperability.
InterSystems IRIS for Health allows developers to perform FHIR CRUD operations directly from ObjectScript routines, bypassing the standard HTTP REST layer. This method utilizes `HS.FHIRServer.Service` to achieve high performance by enabling native query construction, schema validation, and storage-level resource access.