SHAPTH and XWasser: Is Your Laboratory Ready for 2027?
Written by Markus Reicke
The digital reporting of drinking water data in Germany is entering a new phase. The federal states intend to introduce SHAPTH and the XWasser standard as the standard, and ultimately the sole, transmission channel for reportable drinking water data from January 1, 2027. Transitional arrangements may vary between federal states.
For many water laboratories, the question is no longer whether they need to address SHAPTH, but how quickly and comprehensively they should prepare. What is often underestimated is that implementation involves much more than providing a new technical interface. Even if a LIMS vendor already offers SHAPTH connectivity, this does not automatically mean the laboratory as a whole is ready for the new requirements. Master data, sampling processes, data quality, error handling, and reporting workflows must all be considered.
A New Standard for Data Exchange
For many years, the exchange of drinking water data has been shaped by Germany’s federal structure. Different state-level solutions and data formats created significant administrative effort, particularly for laboratories operating across multiple regions. Systems such as NiWaDaB, TEIS, LabDüs, and Octoware exemplified a heterogeneous landscape where requirements and interfaces varied from one federal state to another.
SHAPTH aims to replace this fragmented environment with a unified approach. It is based on the XÖV standard XWasser, which provides a nationally harmonized data model for the exchange of drinking water information. SHAPTH serves as the shared and secure exchange platform for the federal states. XWasser documents, such as analytical reports, are transferred via REST-based interfaces, while GraphQL is primarily used for registry data and related queries.
The objective is to establish a standardized and seamless flow of information between laboratories, public health authorities, and other stakeholders. To achieve this, however, the underlying data must be far more standardized than is currently the case in many laboratories.
The Biggest Challenge Is Usually Not the Interface
In many projects, the technical connection itself represents only a relatively small portion of the overall effort. A far greater challenge is determining whether the required data already exists in the necessary structure and quality.
Over the years, laboratories have developed highly individualized data structures. Parameter names, units, sample types, and sampling information have often been adapted to local operational needs. XWasser, however, requires a clear and standardized description of data. Every relevant data element must be mapped to the target structure. This data mapping process forms the foundation of successful data exchange.
Particularly critical are data elements that have historically been documented only in free-text fields. While this may have been sufficient for internal use, automated data exchange can quickly expose limitations. Missing mandatory information or ambiguously documented data may result in rejected submissions or manual rework.
The management of code lists also becomes increasingly important. The regulatory and technical requirements behind XWasser continue to evolve. Laboratories should therefore not only use the latest code lists but also ensure that previously submitted data remains traceable over the long term. Best practice includes retaining transmitted XML documents, schema versions, and applicable code list versions in an audit-proof manner. This provides the ability to determine exactly how a submission was created, even years later.
Another aspect that is often overlooked is that not every analysis performed by a laboratory falls within the scope of the Drinking Water Ordinance. Laboratories should therefore decide early on which additional analyses should be exchanged through SHAPTH in the future and how they will be represented within the master data model and mapping concept.
Which Integration Approach Fits Your Laboratory?
There are several technical options for connecting to SHAPTH. The most suitable approach depends largely on the existing system landscape and the roadmap of the respective LIMS vendor.
Many laboratories prefer direct integration into their existing LIMS. The advantage of this approach is that data can be processed without additional middleware components. However, it requires the vendor to provide the necessary functionality in time and sufficient project resources to be available.
Alternatively, an external integration solution may be used. In this model, operational processes remain within the existing LIMS, while an additional component handles the transformation into the XWasser format and communication with SHAPTH. This approach is particularly suitable when native SHAPTH support is not yet available or when greater independence from the core system is desired.
For organizations that may not achieve fully automated integration by early 2027, the SHAPTH web portal offers a possible interim solution. In the long term, however, most organizations will require automated integration to minimize effort and reduce the risk of errors.
SHAPTH Readiness Must Be Proven
A common misconception is to equate a software vendor's statement regarding SHAPTH compatibility with actual operational readiness.
Ultimately, the critical factor is not whether an interface exists, but whether the entire information flow works reliably. Every laboratory should therefore perform a complete end-to-end test in the SHAPTH PRE environment.
This should include generating a real analytical report, transforming it into the XWasser format, and transmitting it through the intended interface. Equally important is validating the responses returned by SHAPTH. Error scenarios, rejections, corrections, and resubmissions should all be tested deliberately. Only after the entire process has been successfully completed can true operational readiness be confidently assessed.
Define Error Management Processes Early
A technically successful connection alone does not guarantee stable operations. Laboratories must establish early on how errors and rejected submissions will be handled.
Ideally, datasets should be validated against current XWasser structures, mandatory fields, and code lists before transmission. This allows many issues to be identified before submission. Nevertheless, situations will occur where reports are rejected or require correction. Clear responsibilities, transparent escalation procedures, and appropriate monitoring capabilities are therefore essential.
Equally important is comprehensive documentation of all transmissions and responses. This is a prerequisite for meeting reporting deadlines as well as auditability and traceability requirements.
Quality and Compliance Remain Critical Requirements
Regardless of the chosen technical approach, the information management workflow should be appropriately verified or validated. The objective is not to validate the entire software landscape, but rather to demonstrate that the relevant processes function reliably.
Particular attention should be paid to data integrity, traceability, access control, audit trails, and the accurate and complete transmission of data. These aspects are expected to play a significant role within the regulated environment of drinking water analytics.
SHAPTH Readiness Assessment: Where Does Your Laboratory Stand Today?
Many laboratories have already received preliminary information from their software vendors and have familiarized themselves with the basic requirements. However, they often lack a clear understanding of the specific actions required within their own organization.
This is precisely where a structured SHAPTH Readiness Assessment provides value. The goal is to create transparency regarding the current maturity of systems, data, and processes. Existing master data is analyzed, potential data gaps are identified, and the SHAPTH and XWasser readiness of the existing LIMS is evaluated. Integration options are assessed, requirements for mapping and master data management are defined, and error handling and escalation procedures are reviewed.
Another key focus is the definition of practical test and acceptance scenarios, including an end-to-end test in the PRE environment. The result is a concrete roadmap that prioritizes required actions and outlines a realistic path toward productive implementation.
As an independent consultancy specializing in laboratory digitalization, integration, and data management, wega supports laboratories in addressing these challenges in a structured and vendor-neutral manner.
Conclusion
SHAPTH and XWasser establish the foundation for a nationwide standardized exchange of drinking water data. For laboratories, however, the challenge begins long before the first data transmission. Master data quality, mapping, process design, error handling, and testing strategy ultimately determine the success of the implementation.
January 2027 is achievable, but it requires early and focused preparation. Organizations that gain transparency regarding their readiness today can reduce project risks and create the foundation for a smooth transition.
The key question is therefore not whether your software vendor provides a SHAPTH interface.
The real question is: Is your laboratory truly ready for SHAPTH?
Ready to Take the Next Step Toward SHAPTH Compliance?
wega supports water laboratories through the SHAPTH rollout with a gap analysis, a mapping concept, support during implementation, end-to-end testing and training before go-live.