Beyond the data tax: what a biopharma handoff must preserve

The signal: interoperability is becoming an operating question

The ISPE Annual Meeting programme includes the Pharma Open Data Space, or PODS. Our interest is the practical problem behind the topic: teams can exchange data yet remain unable to compare it. Connectivity and scientific interpretability need to be evaluated separately. This article proposes a handoff test; it does not claim to implement or certify a PODS specification. [1]

The familiar data tax is the time people spend finding, reconciling and explaining information before they can use it. A supplier may send a complete file while the receiving scientist still needs a meeting to understand the samples. Eliminating the file transfer is therefore an incomplete definition of the problem.

Interoperability is a cross-team agreement, not just an integration

In a Pharma 4.0 operating model, an interoperable record has both a technical route and an organizational owner. The sending scientist, receiving MSAT team and QC method owner must agree what a result represents and when it can be compared. Information systems carry the agreement; they do not create it automatically. [3]

Culture matters at the point of disagreement. A receiving team needs permission to hold an ambiguous comparison, and the sending team needs time and responsibility to resolve it. Measure clarification work and repeated mapping exceptions, then improve the source process. Counting connected systems misses that operating learning.

Interoperability succeeds when people can preserve and challenge scientific meaning across a handoff. The record must also carry the units, methods and context needed by the next calculation or model.THE BIOMEDANA LENS

A hypothetical chromatography transfer exposes the gap

Imagine a development team transferring a purification study to a receiving site. Both parties can open the chromatogram export. The development team reports recovery using one denominator while the receiving team uses another. Column identities are abbreviated, and an assay result refers to a pooled sample that is not clearly linked to the fraction records.

Nothing needs to be missing at the transport layer for this handoff to fail scientifically. The next decision might concern a loading study, a repeat analysis or an equipment comparison. Each depends on the interpretation of the result, not merely its availability. A technically successful integration should not be allowed to stand in for that interpretation.

Define a record that survives an independent review

Our proposed minimum record includes stable material and sample identifiers, process stage, equipment context, time basis, units, method version, original source and transformation history. Some workflows need additional fields, such as pooling rules or the treatment of below-quantification observations. Define those fields from the comparison the receiving team intends to make.

Include a review state. A result awaiting sample clarification may remain accessible without being accepted for comparison. A later correction should retain the earlier value and its explanation through the appropriate record controls. FDA's data-integrity guidance provides relevant background on reliable and accurate drug CGMP records; the particular handoff schema here is our proposed design. [2]

Separate transport, semantics and permission

A transport test asks whether the expected record arrived intact and on time. A semantic test asks whether a receiver interprets the identity, units and relationships as intended. An authorization test asks whether the requesting person may receive that record for this purpose. These are separate acceptance questions, even when one integration component helps answer all three.

For a partner exchange, test a user who lacks access to a restricted study and a sample whose identifier resembles an authorized one. Confirm that restrictions survive indexing, caching and export. A clean user interface is insufficient evidence that the underlying retrieval path respects the same boundary. Retain the request, policy decision and relevant source version in the test record.

Different standards do different jobs

A useful interoperability discussion identifies what each component contributes. An Asset Administration Shell can structure information about an asset. MTP addresses integration of modular equipment. Digital calibration information can connect a measurement to an identified device and its calibration history. These functions complement one another; none alone establishes that two scientific records are comparable. [4]

Consider a receiving team evaluating a measurement used in a model. It needs the device identity, units, calibration state, analytical or processing method, relevant time and access rights. It also needs an owner who can resolve a disputed mapping. A record that arrives successfully but loses those relationships has passed a transport test and failed the scientific handoff.

PODS provides an important direction for this discussion. A roadmap or named standard should lead to a practical acceptance test, not an assumption that a platform already supports the whole ecosystem. Any BioMedAna integration claim should be tied to the interface and workflow actually demonstrated.

Version the contract without freezing the science

Scientific methods and operating needs change. The contract should identify a schema version and the transformations used to map a source into it. A new method should trigger an explicit decision about comparison, rather than being silently accepted because its result fits an existing numeric field. Compatibility at the file level is not a scientific comparability assessment.

We would keep a short compatibility register: what changed, which analyses depend on it, who reviewed the effect and how older records remain interpretable. Resist both extremes of never evolving the schema and allowing every team to redefine a term locally. Versioned translation can be useful when the receiver knows exactly which differences remain unresolved.

Make disagreement an integration acceptance test

Prepare two small representative handoffs, one straightforward and one with a deliberate conflict. Ask a receiving scientist to explain the comparison without a call to the original author. The conflict might involve a changed assay version, a timezone shift or a recovery calculation that uses a different starting quantity. The intended outcome can be a documented refusal to compare.

Measure clarification effort, identity mismatches and the time to an interpretable review. Track which failures the interface detects and which still depend on expert recognition. A workflow that identifies its own boundary can be more useful than one that always produces a consolidated table. Successful transport should never force acceptance of an ambiguous scientific record.

BioMedAna: preserve the inputs that the scientific engines actually need

BioMedAna’s Hub-to-Twin-to-agent workflow gives interoperability a scientific purpose. A physics-based calculation needs compatible geometry, units and operating conditions. A reaction-kinetics model needs species, stoichiometry, concentration, temperature and time definitions. A hybrid model needs traceable training and evaluation runs. Moving a file without preserving those meanings cannot establish model readiness.

The differentiation is the connected path from records to explicit scientific calculations and a reviewed operating decision. BioMedAna implements engineering and chemistry services alongside mechanistic and machine-learning models; the assistant helps coordinate the work. For a receiving site, acceptance should include reconstructing a model input from its original record and explaining why that input is suitable for this comparison.

A scientific handoff acceptance matrix

An original BioMedAna working framework. Adapt the decisions and evidence to the actual process, people and intended use.

The questions behind the headline

Follow the evidence

1. ISPE 2026 Annual Meeting & Expo - live agenda, accessed 21 October 2026 ↗
2. FDA - Data Integrity and Compliance With Drug CGMP, final, December 2018 ↗
3. ISPE - Pharma 4.0 operating model ↗
4. IDTA - Asset Administration Shell and MTP submodel resources ↗

Original BioMedAna editorial analysis. The linked sources support the reported developments; examples, frameworks and product implications reflect our perspective.

Explore the underlying concepts

Explore the ISPE & Pharma 4.0 series ↗

• What is bioprocess data contextualization?
• Preserving process knowledge through technology transfer
• CHO process-transfer investigation
• Explore BioMedAna Hub