CliniGA CRO

CliniGA CRO Blog

Decimal Separators: Preventing Locale Settings from Changing Clinical Numbers

Test locale settings to verify that decimal and thousands separators do not change clinical values during transfer.

Representative research photograph: Decimal Separators: Preventing Locale Settings from Changing Clinical Numbers
Photo: Hope2018 · License: CC BY-SA 4.0 · Cropped and resized.
Published
Updated

Commas and full stops carry different meanings under different locale settings. A value that looks correct in one file can change magnitude when another computer interprets punctuation as thousands grouping or converts the cell to text.

Preserve the meaning of data

Define the numeric interchange format independently of application language. Specify expected handling of decimal separators, grouping, scientific notation and spaces. Separate local screen presentation from machine-transfer representation. Opening and saving a file manually is also a transformation step; test how it affects numeric and date fields rather than assuming that the file remains unchanged.

Worked example

For example, a value displayed as 1,25 is opened under a different locale and later transferred as 125. Format checks pass even though the measurement has changed. The team compares small, large and high-precision examples across both settings, checking expected numeric values as well as row counts. It identifies historical files exposed to the same process.

Review checks

  • Use examples containing commas, full stops and scientific notation together.
  • Compare values after opening and resaving in the target application.
  • Review automatic conversion of text that resembles numbers.

Acceptance and boundaries

Acceptance means the relationship between source number, transferred value and displayed representation is explainable. Matching locale settings today does not establish reliability for every future file; the interchange contract should remain explicit. Correction should not mean blindly replacing every comma. Verify the field type and intended numeric meaning against a trustworthy source first.

Frequently asked questions

Must every file use a full stop?
A technical interchange format can be standardised while local user presentation remains a separate design choice.
Can numeric-looking text be converted?
Do not convert it automatically without confirming the field purpose; identifiers and comments may also resemble numbers.

Sources

  1. FDA — Electronic systems, records and signatures in clinical investigations
  2. MHRA — Guidance on GxP data integrity