This article details how to identify hypertensive patients meeting specific criteria using Constraint Query Language (CQL) and FHIR Measures. Based on the Taiwan version of CMS-165, it outlines a process for generating a list of patients requiring medication management by combining historical diagnoses and recent blood pressure measurements.
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.
gematik has released a new FHIR extension, 'GEM_ERP_EX_AcceptDate,' designed to manage payment deadlines for pharmaceuticals within electronic health records. This feature aims to track the final deadline by which an insurer accepts and pays for a prescription.
Accenture has secured a new three-year contract (valued at A$161.6 million) from the Australian Digital Health Agency (ADHA) to provide Application Support and Maintenance (ASM) services for My Health Record. This ensures the continued operation of the national digital health infrastructure.
Tundaris supports the structured, secure, and traceable exchange of clinical data. Instead of replacing existing HIS systems, it utilizes standards like HL7 FHIR and RDA to achieve readiness for healthcare interoperability (IHCE).
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.
gematik has released a FHIR CapabilityStatement for billing data related to the e-prescription. This technical specification standardizes how healthcare providers handle information necessary for billing claims under private health insurance (PKV).
The Uzbekistan Digital Health Platform has released an integration specification for organizational data (Organization) based on the FHIR standard, version 0.8.0. This provides a structured definition for exchanging healthcare institution data.
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.
RSAI has enabled healthcare providers to directly integrate revenue cycle management (RCM) automation functions into their Electronic Health Records (EHR) and billing platforms via its API. This streamlines processes such as eligibility verification, prior authorization, and claims submission.
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.
The Uzbekistan Digital Health Platform has released the resource definition for 'UZ Core ImmunizationRecommendation' based on FHIR standards. This mechanism is designed to facilitate core information exchange regarding vaccinations, expected to be utilized in system development and integration.
Aamako Maya Apps provides a digital health platform in Nepal connecting hospitals and community communities. By achieving structured data exchange through an HL7 FHIR-based interoperability layer, they are building the foundation for national electronic medical records.
This guide publishes detailed mappings for the 'Practitioner' resource profile, based on FHIR R4. This clarifies associations with various data structures and standards, forming a foundation for healthcare information exchange.
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.
Amakomaya has released version 2.0.0 of its FHIR implementation guide, providing detailed examples for the `amk-consent` profile. This defines a standardized process for obtaining 'opt-in' consent in healthcare information, establishing a foundation for system interoperability.