Description
Pair an absent-reason code with its stated code system.
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 absent-reason code with its stated code system.
When to use this tool
Use FHIR Absent Reason Token when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter reasonCode, codeSystem. 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 reason code and code system. Return JSON text encoding [codeSystem,reasonCode].1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reasonCode | Reason Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| codeSystem | Code System | 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": {
"reasonCode": "unknown",
"codeSystem": "http://terminology.hl7.org/CodeSystem/data-absent-reason"
},
"output": {
"token": "[\"http://terminology.hl7.org/CodeSystem/data-absent-reason\",\"unknown\"]"
}
}Limitations and assumptions
- The absent-reason token is recorded without validating its vocabulary, actual observation status or the reason for missing data.
- 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
- FHIR Observation Component Code Pair
Record an observation component code together with its observation and code system.
- Clinical Unit Code Namespace Label
Identify a clinical unit code by its namespace and version.