AWS provided documentation detailing the creation and management of the FHIR Subscription lifecycle using AWS HealthLake. This guide outlines the technical steps for establishing and maintaining data subscriptions.
VectorCare has launched a new application utilizing the SMART on FHIR standard. This initiative aims to accelerate and improve patient logistics integration.
VectorCare launched a SMART on FHIR application to improve patient logistics integration. This allows care teams to request and manage patient-related processes using the app.
A certificate error was encountered while attempting to connect to the e-Referral Service (e-RS) API in the integration testing environment. This issue relates to the handling of FHIR/STU3/ReferralRequest data.
VectorCare launched a new application designed to manage patient logistics and discharge processes. This app was built using the SMART on FHIR interoperability standard.
HL7 has released an experimental CodeSystem related to the Advanced Beneficiary Notice Code. This CodeSystem is part of the broader FHIR standard development.
The service provides an automated solution for converting JSON data into FHIR format. This capability supports seamless HL7 compatibility and automated mapping processes.
A new LOINC code, 24496-2, defining Food Allergen Mix C (Oat+Barley+Rice+Rye+Wheat+Corn) IgE, has been associated with the FHIR standard. This update enhances the interoperability of allergy and food safety data using standardized terminologies.
A converter tool was developed for transforming C-CDA documents into the FHIR standard. This tool aims to demonstrate measurable return on investment (ROI) in healthcare data interoperability.
The Ministry of Health and Welfare announced plans to develop a national medical information standard platform in Taiwan. The goal is to integrate electronic medical records across major hospitals nationwide within two years.
Google Cloud released documentation for updating FHIR resources through its Cloud Healthcare API. This resource update capability supports standard FHIR payloads, such as those for the Patient resource.
FHIR technology is utilized to support compliance with CMS interoperability and patient access regulations. This capability helps drive interoperability and improve patient access.
jpfhir.jp released a JSON representation for the Condition Severity ValueSet, specifically for FHIR v4.0.1. This resource is part of the local development build of the HL7 FHIR JP Core Implementation Guide.
Mount Sinai Tisch Cancer Center debuted a new real-time data integration tool. This tool enables structured data to flow securely and automatically from Epic using FHIR standards.
The content demonstrates a technical route for converting HL7 FHIR JSON data into the X12 278 standard. This process utilizes the PilotFish eiConsole platform to manage the data transformation.
Synthetic EHR announced the development of a comprehensive API ecosystem. This system is designed to facilitate technical integrations and strategic partnerships, specifically supporting the advancement of healthcare artificial intelligence.
A JSON representation for the PCA Type (2.8 - 1.0.0) vocabulary was made available. This resource utilizes the HL7 FHIR Standard and is accessible via FHIR Build Tools.