Release 2025-6

Read in Dutch

Read in German

Platform and Partner Lifecycle PolicyPlatform and Partner Lifecycle Updates

This release brings a combination of platform-wide improvements, regional enhancements, and foundational interoperability work. It includes updates that improve how documents are managed at scale, strengthen the reliability and security of existing XDSCloud deployments, and make data retrieval more precise through consent-aware querying. In parallel, we’re continuing to invest in regulatory readiness for the German market by advancing ISiK-related research and proof-of-concepts, reducing uncertainty around compliance and integration with both modern and legacy EHR environments. Together, these updates focus on making data availability more controlled, predictable, and future-ready, without disrupting existing workflows.

This update enhances the Information Lifecycle Management (ILM) service by enabling partial deletion of document history. Instead of deleting an entire document version history, specific documents can now be deleted selectively by using their document identifiers.

Filtering based on criteria such as status, date range, author institution, document type, format code, class code, or repository is not performed directly within the ILM service. Instead, documents are first identified using filtering capabilities outside of ILM, after which the resulting document IDs can be used to perform a partial deletion.

What this means for you

You gain more granular control over document lifecycle management. This allows you to clean up deprecated or outdated documents without affecting active or approved records, making document repositories easier to manage at scale and control storage costs.

This update introduces smart target querying using Mitz localization to determine which organizations hold patient data and whether valid consent exists before issuing queries. This addresses inefficiencies caused by over- or under-querying connected organizations.

Learn more

What this means for you:

Patient data queries are now more precise and intentional. Instead of querying all connected organizations, requests are targeted only at organizations that are known to hold relevant data and where valid patient consent exists. This reduces unnecessary system load, lowers retrieval latency, and increases the likelihood that returned results are relevant and up to date - while respecting consent requirements by design.

Added support for WID-check (identity verification) validation. When a patient’s identity is not (yet) verified in the EHR/EMR, hospitals can automatically block external data exchange (e.g., outbound sharing/queries) until verification is completed.

What this means for you:

Helps prevent external exchange for patients whose identity isn’t verified yet, acting as an extra safety gate alongside consent. Clinicians can also see the patient’s identity-verification status in forView, reducing the risk of exchanging data under an unverified identity.

Overview of the update

We have implemented and successfully tested support for the ISiK base module using an open-source FHIR server integrated with Founda’s existing infrastructure. All current ISiK base module test cases are covered, providing a production-ready foundation for ISiK-compliant FHIR transactions.

What this means for you

When required, we can now provide ISiK base-module–compliant transactions for German projects. We will continue to expand our ISiK support with additional modules in future releases.

We have completed in-depth research into how Founda can reliably support ISiK-compliant workflows when connecting to EHR systems that communicate via HL7v2. This work focuses on defining a scalable strategy to transform incoming ISiK FHIR requests, such as appointment scheduling and vital signs, into the required HL7v2 message types (e.g. SIU, ORU), and to map HL7v2 responses back into compliant FHIR resources.

What this means for you:

If your EHR landscape relies on HL7v2, this work directly addresses one of the main barriers to ISiK adoption: bridging modern ISiK FHIR requirements with existing HL7v2-based systems. The research clarifies what transformations are feasible today, where limitations exist, and how onboarding effort can be reduced through configurable mappings. While no new feature is enabled yet, this foundation reduces uncertainty around timelines, scope, and feasibility for future ISiK implementations.