Union of ehealth-max-participants Profiles
This resource defines a union of two ehealth-max-participants profiles. It specifies the structure for tracking the maximum number of participants allowed in a video meeting using a FHIR extension.
1,953 FHIR-related articles (latest first)
This resource defines a union of two ehealth-max-participants profiles. It specifies the structure for tracking the maximum number of participants allowed in a video meeting using a FHIR extension.
USys provides multiple integration models to achieve interoperability between laboratory and healthcare systems. It supports major standards including HL7 v2.x, FHIR R4, and ASTM, enabling seamless data exchange among analyzers, internal systems, and external partners.
Apple has published the prerequisites for healthcare organizations to participate in Health Records. Participation requires healthcare providers in the US, UK, or Canada to secure a public FHIR API endpoint for patient authentication and utilize a compatible EHR system.
The Data Integration Toolkit, provided by Microsoft Cloud for Healthcare, is a management suite designed to securely synchronize and manage patient health information between Electronic Health Record (EHR) systems, FHIR servers, and Microsoft Dataverse.
CENS offers an 'HL7 FHIR® Intermediate' course for healthcare professionals, aiming to enhance knowledge and practical skills regarding interoperability in digital health. The course allows participants to develop advanced FHIR® solution implementation capabilities by applying theory to real-world projects.
AdvancedMD has released an API for handling the 'Organization' resource, which adheres to the HL7 FHIR standard. This API allows for searching by organization name or address, and retrieving detailed information using a specific ID, positioning it as a foundation for healthcare data exchange between institutions.
This page displays an HTTP 200 OK response body received from the HAPI FHIR server. The data includes a detailed FHIR Bundle for a specific binary resource (ID: 2856882), allowing confirmation of its history and metadata.
HL7 Workbench provides an FHIR implementation guide for the Da Vinci Drug Formulary. This page references various FHIR R4 elements (resources, data types, code systems, etc.), offering a structure useful for standardizing drug formularies.
Microsoft reported a vulnerability in Azure Health Data Services FHIR, allowing data exfiltration through Server-Side Request Forgery (SSRF). This flaw could expose sensitive FHIR records and storage metadata from separate accounts accessible by the service identity.
Integrating speech transcription into Electronic Health Records (EHR) requires advanced engineering to map unstructured audio data to correct FHIR resources. Key challenges include managing SMART on FHIR OAuth 2.0 and building resilient asynchronous write pipelines that survive rate limits and EHR downtime.
Mential offers an API that converts unstructured clinical data (notes, transcripts, etc.) into FHIR R4 format and provides behavioral intelligence. This allows developers to easily integrate enterprise-grade clinical data into their own digital health products.
Phronexis announced a demonstration of an engine that integrates fragmented patient records from multiple sources with different structures, such as HL7v2, CCDA, and FHIR. The system demonstrated the ability to construct a single, reliable timeline by tracking every decision process in an auditable manner.
Developers can build custom clinical applications using FHIR4DS in a WebAssembly environment. This technical guide explains how to execute advanced clinical logic (CQL) directly in the browser by utilizing DuckDB extensions and Python translation modules.
This article details the FHIR resource API specification for a Practitioner. It outlines how to read by ID, create new records, and update existing data via various endpoints. Searching is supported using identifiers like NPI, based on the US Core profile.
This article details the FHIR R4 ImagingStudy resource. This resource handles metadata related to DICOM imaging studies, providing structured information such as which patient was studied, what type of image was taken, and when. It establishes a foundation for searching and linking image data within electronic health records.
This article guides healthcare organizations on selecting a strategic software development partner that offers more than just a FHIR API. It compares key companies like InterSystems, Edenlab, and Firely, detailing their specialized strengths to help users choose the best fit based on project needs.
Edenlab presented how to utilize openEHR's structured longitudinal records as a foundation, leveraging FHIR APIs for external system integration and advanced analysis to extract clinical insights. This enables the utilization of comprehensive medical data beyond standard EHR records.
The SQL on FHIR WG plans to define ViewDefinition as an 'additional resource' in R6. Separately, two approaches were discussed for terminology querying: tabular abstraction versus using FHIRPath functions.
At the Asia READY summit, InterSystems announced that enterprise interoperability and unified EHR foundations can connect fragmented clinical data to practical AI tools. The goal is to integrate diverse data sources from hospitals and clinics into a standardized format, building a reliable foundation necessary for effective AI utilization.
A developer built a pipeline that processes both clinical data formats, FHIR R4 bundles and raw HL7v2 messages, normalizing and validating them into a single internal model. It is implemented in Go and serves the data via GraphQL API and FHIR REST API.