Description
Pair an existing patient-record pseudonym with its namespace.
Health-information systems separate identifiers, code-system namespaces, source versions, missing-value states and reference syntax. Recording a mapping or recognizing a restricted token does not validate its clinical meaning or a complete HL7/FHIR resource. Explicit null, empty text, unknown status and numeric zero are different states.
Pair an existing patient-record pseudonym with its namespace.
When to use this tool
Use Patient Record Pseudonym Namespace Key when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter namespace, suppliedPseudonym. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Require nonempty namespace and supplied pseudonym. Encode [namespace,suppliedPseudonym] as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| namespace | Namespace | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedPseudonym | Existing supplied pseudonym; the tool generates no pseudonym and performs no anonymization. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | JSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"namespace": "N17",
"suppliedPseudonym": "P00024"
},
"output": {
"token": "[\"N17\",\"P00024\"]"
}
}Limitations and assumptions
- The tool records an existing pseudonym; it does not generate one, anonymize patient data or authorize disclosure.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the intended complete interoperability specification, authoritative terminology and verified source records for actual resource validation, semantic mapping or clinical use.
References
Similar or alternative tools
- Clinical Unit Code Namespace Label
Identify a clinical unit code by its namespace and version.
- Clinical Code System Edition Key
Keep a clinical code, code system and edition together as a record key.