Description
Preserve explicit timestamp text and reported precision.
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.
Preserve explicit timestamp text and reported precision.
When to use this tool
Use Clinical Reported Timestamp Precision when you already have recordId, suppliedTimestampText, precisionWording and need to preserve explicit timestamp text and reported precision.
How to use the tool and how it works
- Enter recordId, suppliedTimestampText, precisionWording. 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 recordId, suppliedTimestampText, precisionWording 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 |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedTimestampText | Supplied Timestamp Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| precisionWording | Precision Wording | 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": {
"recordId": "R17",
"suppliedTimestampText": "2026-11-01",
"precisionWording": "day"
},
"output": {
"token": "[\"R17\",\"2026-11-01\",\"day\"]"
}
}Limitations and assumptions
- The result records supplied values without inventing missing date components. 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 Study Screen Fail Code
Qualify an explicit screening failure code by source.
- Clinical Record Source Correction Marker
Qualify an explicit clinical-record correction reference by source version.