Description
Label a supplied clinical visit's protocol day under a day-zero/day-one policy.
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.
Label a supplied clinical visit's protocol day under a day-zero/day-one policy.
When to use this tool
Use Research Visit Protocol Day Label when you already have referenceDate, visitDate, referenceIsDayOne and need to label a supplied clinical visit's protocol day under a day-zero/day-one policy.
How to use the tool and how it works
- Enter referenceDate, visitDate, referenceIsDayOne. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read protocolDay, label. Use the output convention below.
Parse real UTC dates and calculate visit-reference day offset. When referenceIsDayOne=true add one only to nonnegative offsets; negative offsets remain unchanged. Return protocolDay and Day label.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| referenceDate | Reference Date | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| visitDate | Visit Date | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| referenceIsDayOne | True adds one only to nonnegative elapsed days, so dates around reference are -1,1 with no day zero. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| protocolDay | Protocol Day | Required. Safe integer. |
| label | Label | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"referenceDate": "2026-11-01",
"visitDate": "2026-11-03",
"referenceIsDayOne": true
},
"output": {
"protocolDay": 3,
"label": "Day 3"
}
}Limitations and assumptions
- Day-one convention yields -1 then +1 around the reference with no Day 0. No actual visit, protocol, clinical timing or appropriate schedule is verified.
- 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
- Trial Data Cutoff Inclusion Flag
Check a supplied trial-record date against a cutoff policy.
- Pharmacy Care Plan Follow Up Date
Shift a supplied care-plan reference date by signed calendar days.