Skip to content

Main content

GCP Visit Protocol Day Offset

Compute signed calendar-day offset from an explicit protocol reference date without choosing a protocol-day convention.

Loading tool…

Description

Measure a clinical-study visit's calendar offset from its protocol reference date.

Clinical-research records connect source fields, protocol dates, training, signatures, safety communications and consent versions. A recorded acknowledgment or date predicate does not establish valid consent, authorized delegation or compliance. Source documentation and substantive participant protections require separate review.

Measure a clinical-study visit's calendar offset from its protocol reference date.

When to use this tool

Use GCP Visit Protocol Day Offset when checking the stated benign clinical-research record or date convention.

How to use the tool and how it works

  1. Enter protocolReferenceDate, visitDate. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read signedCalendarDays. Use the output convention below.

Parse real visit/reference YYYY-MM-DD dates at UTC midnight. Return visitDate-protocolReferenceDate in calendar days.1

Input fieldMeaning and unitsAccepted input
protocolReferenceDateProtocol Reference DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
visitDateVisit DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
signedCalendarDaysSigned Calendar DaysRequired. Finite number.
json
{
  "input": {
    "protocolReferenceDate": "2026-10-28",
    "visitDate": "2026-11-01"
  },
  "output": {
    "signedCalendarDays": 4
  }
}

Limitations and assumptions

  • No protocol window, compliance criterion or actual visit is verified; negative offsets are retained.
  • 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 verified protocols, consent and source records under the applicable complete research requirements with qualified responsible personnel for actual study or participant decisions.

References

  1. Calculation and input contract: gcp/gcp-visit-protocol-day-offset — tool.io

Similar or alternative tools