CapMinds is a healthcare technology company that helps organizations build secure, connected, and AI-ready digital ecosystems. They specialize in EHR/EMR modernization, HL7/FHIR interoperability, healthcare APIs, and AI-driven solutions.
Developer Tord Glad Nordahl argues that the healthcare sector must invest in open infrastructure and APIs. He warns that when public entities build external applications, workflows risk being dictated outside the system, losing seamless integration.
As HealthTech applications scale and connect to multiple EHR systems, early EHR/EMR integration planning is crucial. This ensures the architecture can handle complex data exchange, identity management, and evolving clinical workflows, especially in light of regulations like the CMS FHIR APIs.
Kaagazy provides an Electronic Medical Record (EMR) system compliant with India's Ayushman Bharat Digital Mission (ABDM) standards and structured for FHIR. Data is hosted on AWS Mumbai, and sensitive data like Aadhaar is encrypted, protected by strict role-based access control and multi-factor authentication.
AeHIN and HL7 International launched the second FHIR Fundamentals Course cohort in the Asia-Pacific region. This cohort brought together 109 participants from 10 countries, aiming to strengthen regional capacity in health information standards and interoperability.
InterSystems IRIS for Health allows developers to perform FHIR CRUD operations directly from ObjectScript routines, bypassing the standard HTTP REST layer. This method utilizes `HS.FHIRServer.Service` to achieve high performance by enabling native query construction, schema validation, and storage-level resource access.
ROOK provides an API for wearable data integration, ensuring compliance with major global privacy regulations including HIPAA, GDPR, and CCPA. By supporting the FHIR standard, it enables the secure and standardized exchange of protected health data.
Optum has published the specifications and a response example for the CRD API endpoint. This endpoint provides the response structure for a successful resource creation, using the 201 status code in FHIR JSON format.
ELGA GmbH published a package for Austrian insurance coverage (PJ1Coverage) based on FHIR v5.0.0. This package standardizes patient insurance information and data communication, providing a foundation for medical data exchange.
Bond Health integrates with major EHR systems (such as Epic and Cerner) and CTMS/eRegulatory tools. It utilizes FHIR R4 APIs and HL7 paths to ensure seamless data flowโsuch as pre-screened patients and consent recordsโbetween systems, preventing double entry.
ELGA GmbH published example definitions for the "AT MOPED Condition Basis" profile (`AtMopedConditionBasis`), based on FHIR v5.0.0. This provides a basic data exchange format for conditions in Austrian healthcare data.
CancerIQ upgraded its platform to integrate natively with Epic Systems across numerous clinics. This enhancement uses HL7 FHIR R4 to automate cancer screening and survivorship care by pulling existing clinical data and embedding decision support directly into Epic workflows.
Intuware addresses data silos undermining care coordination by providing interoperability solutions. They utilize modern standards like FHIR R4 and US Core, alongside legacy formats like HL7 v2 and CDA, ensuring secure and reliable data flow between EHRs, payers, and labs.
ELGA GmbH published a local development build (v0.1.0) for the MOPED profile, focusing on modern patient billing and data communication, based on FHIR v5.0.0. This defines a specific profile for standardizing data exchange within the Austrian healthcare system.
This documentation details the process of searching and configuring FHIR resources within a platform. Users can select from standard schemas, FHIR profiles, or custom FHIR resources, and define parameters like HTTP methods and search criteria to achieve advanced interoperability integration.
eHealth Infrastructure has published the FHIR ValueSet "Data Absent Reason." This standardizes the reasons why expected data elements are missing, allowing systems to specify whether the absence is due to patient refusal or a system error, thereby improving interoperability.
Helix EMR provides functionality to manage clinical research data by structuring it directly from routine care records. By linking trial information and biobank specimen data to the patient record, it enables data export in FHIR R4 format using standard terminologies like LOINC and SNOMED CT, thereby promoting research utilization.
WHO SMART Trust has published version 1.7.2 of the GDHCNParticipant-EST-UAT profile. This profile, based on FHIR v5.0.0, defines the technical endpoints necessary for Estonia's government health data exchange.
The Uganda National Health Terminology Service provides authenticated REST and FHIR interfaces for integration clients. This allows developers to perform standardized terminology operations, such as code lookups and value set expansions, via server-to-server integration.
Health-Connect addresses flawed EMR data by applying predictable repairs using facility-scoped rulesets immediately after ingestion. Integration engineers can dry-run rulesets before publication to measure quality lift.