Helsedirektoratet is proposing the reuse of a specific value set from HL7 FHIR IPS. This initiative aims to standardize the definition and reporting of the severity level of a reviewed reaction.
HL7 Hong Kong is organizing its 5th Connectathon Series in 2024. The event aims to establish a community dedicated to developing healthcare solutions using FHIR standards in Hong Kong.
The Ministry of Health and Welfare is revising health data standards to ensure broader interoperability. The updated standards will include detailed specifications for FHIR transmission and will distribute a reference terminology set for international use.
AWS has updated its HealthLake documentation to confirm support for FHIR R4 resource types. This update specifically mentions the availability of the AuditEvent resource type.
AWS has implemented support for SMART on FHIR within its AWS HealthLake service. This feature enhances interoperability and allows applications to securely connect with health data stored in HealthLake.
Elait Health has appointed Michael Boggs as its new CEO. This leadership change aims to drive the company's strategy and expand its adoption of healthcare technologies.
AWS has introduced functionality within AWS HealthLake to bundle multiple FHIR resources. This feature allows users to manage related data points as a single, cohesive unit.
An interactive guide was published detailing various methods for building and publishing FHIR implementations. This resource aims to provide developers with comprehensive knowledge on FHIR development practices.
Black Book Research released a ranking naming Onyx as the top performer for client satisfaction in FHIR-based prior authorization. The survey gathered insights from 665 providers and 718 payers.
The Open Digital Health Summit is scheduled to take place in Nairobi from December 1-3, 2024. The summit will focus on how open standards, Full-STAC approach, and DPIs can accelerate digital health initiatives.
AWS HealthLake allows users to manage FHIR resources directly within the AWS cloud environment. This functionality utilizes the FHIR R4 RESTful API for comprehensive resource management.
AWS provided documentation regarding FHIR profile validations within HealthLake. This documentation clarifies that data ingestion into a HealthLake data store does not require a specific FHIR profile validation.
FHIR API-based Provider Directories are required for certain payers. This requirement outlines the necessary technical standards and implementation deadlines for these entities.
Black Book Research published a ranking recognizing Onyx for its client satisfaction in FHIR-based prior authorization solutions. This ranking highlights Onyx's market standing in the specialized area of healthcare interoperability.
The project utilizes SNOMED-CT codes to map convenient and input medical data. This data is linked with a FHIR terminology server to provide various medical services within a standardized system.
HIMSS published a final rule fact sheet covering TEFCA and the Manner Exception. This document also addresses administrative changes and components like USCDI and Bulk FHIR.
HL7 Austria published the Core Patient Profile Mappings, specifically for the FHIR v5.0.0 standard. This guide provides detailed implementation guidance for the core patient profile within the Austrian healthcare context.