Description
Qualify an explicit clinical endpoint identifier by source version.
Research records need explicit date origins, visit definitions, consent context and observation states. Study day one can omit day zero, whereas ordinary elapsed-day arithmetic starts at zero. A supplied report label or date difference is not a validated clinical finding or a complete research endpoint.
Qualify an explicit clinical endpoint identifier by source version.
When to use this tool
Use Clinical Endpoint Source Key when you already have studyId, endpointId, sourceVersion and need to qualify an explicit clinical endpoint identifier by source version.
How to use the tool and how it works
- Enter studyId, endpointId, sourceVersion. 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.
Enter studyId, endpointId, sourceVersion using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| studyId | Study Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| endpointId | Endpoint Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceVersion | Source Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"studyId": "ST17",
"endpointId": "EP2",
"sourceVersion": "v2"
},
"output": {
"token": "[\"ST17\",\"EP2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without deriving endpoint values. Sources and asserted relationships are not independently authenticated.
- 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
Review the protocol, source documents and study-day convention before combining records. Use the complete research and clinical assessment for interpretation; local labels, offsets and comparisons do not establish data validity, participant status or an outcome.
References
Similar or alternative tools
- Clinical Record Source Correction Marker
Qualify an explicit clinical-record correction reference by source version.
- Clinical Reported Timestamp Precision
Preserve explicit timestamp text and reported precision.