Description
Return a JSON-array identityKey of system, version, and code, and independent nonempty version and display flags.
Clinical identifiers and references have a namespace, target, and sometimes a version or contained-resource scope. Parsing their spelling does not resolve the target or establish semantic identity.
Return a JSON-array identityKey of system, version, and code, and independent nonempty version and display flags.
When to use this tool
Use FHIR Coding Version Display Pair when you need one supported clinical-reference or scoped-identifier component.
How to use the tool and how it works
- Enter system, code, version, display. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read identityKey, hasVersion, hasDisplay. Inspect hasVersion, hasDisplay before interpreting the associated values.
Require nonempty system and code. Return a JSON-array identityKey of system, version, and code, and independent nonempty version and display flags.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| system | System | Required. Text; maximum UTF-16 length 8192. |
| code | Code | Required. Text; maximum UTF-16 length 8192. |
| version | Version | Required. Text; maximum UTF-16 length 8192. |
| display | Display | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| identityKey | Identity Key | Required. Text; maximum UTF-16 length 8192. |
| hasVersion | Has Version | Required. Boolean. |
| hasDisplay | Has Display | Required. Boolean. |
{
"input": {
"system": "urn:example:codes",
"code": "001",
"version": "v2",
"display": "Example"
},
"output": {
"identityKey": "[\"urn:example:codes\",\"v2\",\"001\"]",
"hasVersion": true,
"hasDisplay": true
}
}Limitations and assumptions
- Display does not enter the key; lexical identity does not verify terminology membership, semantic equivalence, or an authoritative version.
- 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 a complete standard-aware resolver and verify terminology, resource identity, and applicable profiles separately.
References
Similar or alternative tools
- Terminology Code System Token
Return a JSON-array key with version or null when unknown.
- FHIR Identifier System Value Pair
Return their JSON-array key.