Search results for "FHIR": 3,948 articles
HL7 has raised a specification update to include MedicationRequest within the workflow 'instantiates' extensions. This change is part of the ongoing development of FHIR extensions to better model clinical workflows.
A discussion was held regarding the potential of FHIR and openEHR standards. These standards are noted for paving the way for seamless healthcare data exchange.
A contest focused on Predictive AI and FHIR integration was announced. The contest offers prizes and aims to improve integration with EHR systems.
A contest focused on Predictive AI and FHIR integration was announced. The contest aims to advance the use of the FHIR standard for incorporating more data.
A query was posted on the NHS England Developer Community regarding the documentation schema for the A008 API. The query specifically questioned the inclusion or absence of the 'emptyReason' field in the response schema.
HL7 International released updates related to its terminology resources, utilizing FHIR standards. This update supports the standardization and interoperability of clinical terminology across different systems.
HL7 is focusing on the technical challenge of identifying sensitive data points within intricate FHIR structures. This effort aims to improve data security and compliance when exchanging complex healthcare information.
A new implementation, Kotlin FHIR, was created for the HL7 FHIR data model. This implementation maps FHIR primitive data types to Kotlin for efficient use.
A digital health consultant spoke about the potential use of FHIR technology. This discussion highlights FHIR's relevance in advancing digital health standards.
Onyx Health and Emids announced a partnership focused on enhancing interoperability compliance. This collaboration aims to help organizations meet the evolving standards set by the Centers for Medicare & Medicaid Services (CMS).
The initiative focuses on converting unstructured patient records, such as doctor's notes and lab results, into a standardized format. This process utilizes FHIR structuring to enable integration with Azure platforms.
NIH made an index available for FHIR resources, including versions like R4 and STU3. This provides access to various FHIR implementation guides and files for developers.
A new LOINC code, 41005-0, was published for detecting Human coronavirus NL63 RNA [Presence] in specimens. This standardizes the reporting of specific viral presence testing results within healthcare data exchange.
The session provided guidance on connecting the OpenMRS system to either HAPI FHIR or OpenHIM. This integration aims to utilize modern interoperability standards for healthcare data exchange.
Onyx Health and Emids have formed a partnership focused on accelerating compliance with CMS interoperability requirements. This collaboration aims to leverage FHIR-based solutions for improved data exchange.
A ValueSet Editor tool was released, allowing users to manage FHIR ValueSets. This tool supports specific implementations and guides related to the ValueSet structure.
A new FHIR Profile, ehealth-clinicalimpression, has been defined for structuring eHealth documentation content. This profile provides detailed descriptions and examples for implementing eHealth documentation using FHIR standards.
HL7 UK showcased a use case demonstrating the sharing of health and social care data. This initiative utilizes FHIR to ensure data consistency and interoperability across different systems.
Onyx Health and Emids announced a partnership aimed at improving compliance with CMS interoperability standards. This collaboration utilizes Onyx Health's platform, OnyxOS, to meet regulatory requirements.
A bug was identified concerning the FHIR Patch replace operation when handling elements with multi-cardinality. This issue was reported in a GitHub context, suggesting a technical limitation in the operation's current implementation.