Description
Record an asserted mapping from a local code to a LOINC code.
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.
Record an asserted mapping from a local code to a LOINC code.
When to use this tool
Use LOINC Local Code Source Link when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter localCode, loincCode, mappingSource. 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 local code, LOINC code and mapping source. Return their ordered JSON text tuple.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| localCode | Local Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| loincCode | Loinc Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| mappingSource | Mapping Source | 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": {
"localCode": "LAB17",
"loincCode": "1234-5",
"mappingSource": "Mapping v2"
},
"output": {
"token": "[\"LAB17\",\"1234-5\",\"Mapping v2\"]"
}
}Limitations and assumptions
- The mapping is recorded rather than validated; the tool does not query LOINC or establish clinical equivalence of codes.
- 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
- Health Record Retracted Result Link
Link a clinical result identifier to a supplied retraction-record identifier.
- Health Care Consent Purpose Code
Record a health-consent purpose code together with its coding system.