4,036 FHIR-related articles (latest first)
AgentCare is an MCP server designed to provide tools for interacting with FHIR data and medical resources. These tools facilitate integration with major Electronic Medical Records (EMRs) including Cerner and Epic.
NHS England released an API and integration catalogue. This resource provides documentation for various integrations, including FHIR API access for GP Connect.
A playbook for public health interoperability training has been released. This resource is designed to guide the implementation of public health data using FHIR standards.
Agent Care configured its MCP Server to connect to the Azalea Health FHIR API. This integration facilitates data exchange using the FHIR standard.
eHealth Infrastructure released documentation for its eHealth platform, specifically version 2.10.0. This update provides structured definitions for the eHealth FHIR extension.
The KBV released a specific FHIR mapping for diastolic blood pressure (2.30.5.7) as part of the DiGA Toolkit. This update aims to standardize the representation of diastolic blood pressure measurements within the German healthcare digital infrastructure.
acme.canada conducted a demonstration project related to FHIR North. This project serves as an example implementation of the FHIR North standard.
Clover released documentation detailing the CarePlan resource, which is a key component in healthcare data exchange. This resource supports various interactions and mappings, facilitating structured care planning within FHIR R4.
Shisetsu Kijun on X: "ๆ ๅ ฑใใใๅใใใใใใฎ่ฆๆ ผ๏ผๅ ฑ้่จ่ชใฎใใใชใใฎ๏ผใHL7-FHIRใง ... X ๆ ๅ ฑใใใๅใใใใใใฎ่ฆๆ ผ๏ผๅ ฑ้่จ่ชใฎใใใชใใฎ๏ผใHL7-FHIRใงใ้ปๅญใซใซใใทในใใ ใฏ3ๆๆธ6ๆ ๅ ฑใHL7-FHIRใซๅคๆ๏ผ็ฟป่จณ๏ผใใฆใใ้ปๅญใซใซใๆ ๅ ฑๅ ฑๆ ... Facebook
FHIR technology is being utilized to streamline clinical workflows. This technology aims to make digital health interoperable and intelligent.
NHS England has released an API and integration catalogue. This resource provides access and updates for various FHIR APIs, such as the Immunisation API.
A new FHIR extension, ehealth-view-type, was identified for mapping purposes. This extension relates to the Danish eHealth Infrastructure and was documented in a FHIR Implementation Guide.
The need for improved interoperability in medical devices was highlighted. Leveraging FHIR-based APIs is suggested as a method to achieve plug-and-play functionality.
The French healthcare sector is undergoing a transformation driven by AI, compliance requirements, and the need for better interoperability. FHIR and openEHR are identified as key technical standards driving these 2025 trends.
The content demonstrated the technical process of transmitting multiple Patient resources using the FHIR standard and HAPI FHIR library. This method helps streamline the efficient exchange of patient data records.
ACC Provider has released an updated FHIR Implementation Guide (v1.1.0) for its Resource Profile. This guide specifies the technical details for the New Zealand ICP standard.
Microsoft is providing a briefing on implementing FHIR, HL7, and HIPAA compliance within the Azure cloud environment. This initiative aims to assist organizations with migrating or implementing cloud-based solutions for healthcare data standards.
eHealth Suisse released a guide detailing FHIR R4 extensions for the CH EPR standard. This resource is intended to guide implementation within the Swiss healthcare ecosystem.
The discussion focused on the relationship between FHIR standards and TEFCA. This suggests ongoing industry interest in standardizing health data exchange.
A job advertisement for a Senior Clinical Data Modeller was posted by NHS. The role requires expertise in FHIR profiles and involves ensuring their proper use within an Implementation Guide.