# Interface Validation Checklist

Version 1.0 | CSVtoCSA practitioner template | Updated 12 September 2026

## Purpose

Define and verify data meaning, mapping, error handling, retry, reconciliation, security, and monitoring across systems.

## When to use

For new or changed application, equipment, laboratory, data, and service interfaces.

## Instructions

- Define the specific system, service, change, population, and intended use.
- Complete each field from available records and accountable interviews; record unknowns rather than guessing.
- Link conclusions to affected GxP functions, failure scenarios, controls, evidence, and approval.
- Adapt the structure to the organization’s approved procedures and document-control process.

## Blank template

1. Source and destination

   Response: 

2. Authoritative data and owner

   Response: 

3. Data elements, units, and identifiers

   Response: 

4. Mapping and transformation

   Response: 

5. Trigger and sequence

   Response: 

6. Acknowledgement and error handling

   Response: 

7. Retry and duplicate control

   Response: 

8. Security and audit trail

   Response: 

9. Monitoring and reconciliation

   Response: 

10. Positive, negative, and recovery tests

   Response: 

11. Deviations and limitations

   Response: 

12. Conclusion and approval

   Response: 

## Completed fictional example

The example below is teaching material, not an executed or approved validation record.

1. Source and destination

   Fictional LIMS to ERP result interface

2. Authoritative data and owner

   Approved LIMS result; Laboratory owner

3. Data elements, units, and identifiers

   Result, unit, material, batch, sample, method, status, time

4. Mapping and transformation

   Unit and status mappings defined in approved specification

5. Trigger and sequence

   LIMS final approval; one ordered message per result revision

6. Acknowledgement and error handling

   ERP response retained; invalid unit held for review

7. Retry and duplicate control

   Immutable message ID prevents duplicate effect

8. Security and audit trail

   Mutual authentication; service account and transaction audit

9. Monitoring and reconciliation

   Daily source, queue, destination, and exception totals

10. Positive, negative, and recovery tests

   Valid, missing, invalid, duplicate, delayed, outage, retry, partial, and mapping cases

11. Deviations and limitations

   Initial unknown-unit default corrected and retested

12. Conclusion and approval

   Released after reconciliation and Quality approval

## Use and limitations

Adapt this template to the applicable regulation, approved validation procedure, document-control process, risk method, and approval roles. CSVtoCSA does not present this template as a universally required validation record.