Make room for reality.
Accents, shared contacts, overseas numbers and missing values need deliberate handling.
DATA QUALITY · IMPLEMENTATION WORKBENCH
From standards
to working rules.
Explore what a data field really needs: usable capture, consistent exchange, faithful storage and clear evidence.
Private workspace for invited reviewers
NAME PROFILEEXAMPLE / 01
CAPTURED VALUE
Siobhán O’Neill
Preserve meaning. Explain the checks.
{
"given": "Siobhán",
"family": "O’Neill",
"normalisation": "NFC"
}
"given": "Siobhán",
"family": "O’Neill",
"normalisation": "NFC"
}
Text integrityLocal check passed
Patient identityNot checked
Illustrative data · format is not identity
01 Capture with care02 Exchange consistently03 Preserve the source04 Show what is known
THE IMPLEMENTATION GAP
One field.
Different responsibilities.
A format rule answers one question. A useful implementation profile also explains what to accept, what to transform and when to ask for review.
Agree the representation.
Define canonical values, versioned rules and the exceptions a receiving system must understand.
Keep the meaning intact.
Preserve spelling, provenance and history. Make transformations visible and reversible where needed.
Make uncertainty visible.
Present readable values and distinguish local validation from external verification.
INSIDE THE WORKBENCH
Explore the reference profiles.
Worked examples, inspectable results and executable local tests.
Names
Unicode, compound names, preferred names and single-name exceptions.
Detailed discussion profileEircode
Formatting and preliminary structure, with address evidence kept separate.
Preliminary local checksBaseline syntax, supported formats and the limits of mailbox assurance.
Baseline local checksMobile
International representation, numbering rules and explicit contact uncertainty.
Versioned numbering metadataTurn a requirement into
a conversation you can test.
Explore the profiles and the new registration reference portal.