Regulated shapes, without regulated records
Healthcare, finance, insurance and automotive systems are where real data is most tempting to copy into a test environment and most dangerous to have there. Under GDPR and HIPAA, a production record in staging is still a production record. These generators produce the shapes those systems validate — check digits, code formats, field relationships — with nothing behind them. Production data in test environments covers the legal side.
- Healthcare — the mock medical record generator builds patient charts with an MRN, vitals, diagnosis, medications, allergies and insurance — with optional out-of-range vitals so alerting logic gets exercised; the ICD-10 generator supplies common diagnosis codes with descriptions, or structurally valid codes, CPT-style procedure codes and SNOMED CT-style concept IDs.
- Company and tax data — the company name generator and tax ID & EIN generator produce entities with US EINs and checksum-valid UK VAT, German USt-IdNr., French TVA, Spanish CIF, Australian ABN and Canadian Business Numbers.
- Vehicles — the VIN generator computes the position-9 check digit North American VINs require and encodes the model year in position 10; the license plate generator follows regional plate formats.
- Travel, property and education — flight numbers and IATA codes, real estate listings and education records for booking, listing and HR systems.
- Legal documents — the legal clause generator produces contract-shaped text for document-assembly and e-signature tools. It is placeholder text, not legal advice.
What the check digits buy you
A tax ID or VIN with a wrong check digit is rejected at the first validator, so the code you meant to test — the lookup, the formatting, the audit trail — never runs. Computing the check digit is what makes a fake identifier useful. Check digits that test data must satisfy walks through each algorithm with worked examples.