Description
Label a medical identifier with its assigning authority and identifier type.
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.
Label a medical identifier with its assigning authority and identifier type.
When to use this tool
Use Medical Identifier Assigning Authority Label when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter identifier, authority, identifierType. 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 identifier, assigning authority and identifier type. Encode the three values in that order as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| authority | Authority | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| identifierType | Identifier Type | 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": {
"identifier": "P17",
"authority": "Hospital A",
"identifierType": "local patient ID"
},
"output": {
"token": "[\"P17\",\"Hospital A\",\"local patient ID\"]"
}
}Limitations and assumptions
- No identifier syntax, assigning authority, identity match or patient record is independently verified.
- 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
- Patient Record Pseudonym Namespace Key
Pair an existing patient-record pseudonym with its namespace.
- LOINC Local Code Source Link
Record an asserted mapping from a local code to a LOINC code.