Docs · Validators
gln validator
GS1 Global Location Number — 13 digits with GTIN-style checksum.
Reference
Format
Matches `/^\d{13}$/`, then delegates to the GTIN checksum (mod-10 weighted 3,1,3,1…) for the trailing digit.
Examples
- 7601001000001 (sample CH GLN)
- 4012345000009 (sample DE GLN)
- 0614141999996
How it runs
Implementation
A faithful summary of lib/validators.ts. Validators are pure functions and run identically in the Worker, the Workbench and the MCP server — one implementation, so the three cannot disagree about whether a value is valid.
function validGln(value) {
if (!/^\d{13}$/.test(value)) return fail('gln_format', 'expected 13 digits')
return validGtin(value) // same mod-10 checksum
}Config
Use in a template
Validators attach to a field on a custom template. The cascade runs them after mapping but before commit; failures surface in the per-row validation report.
fields:
- column: gln
type: string
validators:
- type: glnWatch out
Common gotchas
- GLN and GTIN-13 share the same checksum. A "valid GLN" might syntactically also be a valid GTIN — the namespaces overlap; only the GS1 prefix tells them apart.
- No GS1 GEPIR (company prefix) lookup. We cannot tell you who owns a given GLN.
- Leading zeros are significant. Send as a string.
Where it runs
Three routes, no AI cost.
- POST
/v1/validate-rowValidate one row against a template. Stateless, no key, pure compute — the fastest way to try gln against a real value.no key - POST
/v1/uploads/:id/validateRun every field validator over the parsed upload, without committing. Returns errors and warnings per row.read - POST
/v1/uploads/:id/commitValidates on the way out.skip_invalid_rowsdrops the failures instead of failing the commit.commit
Validators are pure functions, so they add nothing to the AI bill. Every map draws a small flat per-map fee from your prepaid token wallet ($10 minimum, shared across the phi-cloud suite); only columns that reach the metered LLM layer, plus any-to-any convert and structural reshape, bill real AI tokens. See pricing
Catalogue
Related templates
- Employee roster
employee_roster_v1Names, AHV/GLN, contract type, address.
Fields ·
gln - Supplier inventory
supplier_inventory_v1Supplier catalogue with GTIN/IBAN/GLN.
Fields ·
gln - Provider directory
provider_directory_v1Providers with NPI/GLN/license metadata.
Fields ·
gln
Explore
All 19 validator types
The complete list a template field can declare. There is no SNOMED validator — it required an affiliate licence, no template used it, and it was removed in 2026.
- gln
- regex
- enum
- date_range
- number_range
- phone
- url
- iban
- bic
- uuid
- gtin
- pharmacode
- fhir_reference
- loinc_code
- icd10_code
- atc_code
- cpt_code
- npi
Back to the documentation index or browse the template catalogue.
Ready when you are
Validate every row — before it lands.
Attach checksum-strict validators to any field, and gate risky commits behind the requires_hitl flag. One key runs the whole cascade.