GCP Source Entry Late Entry Lag Tool

Description

Return entry lag, correction lag or zero, and late when entry lag strictly exceeds the maximum.

Clinical-trial record intervals track events, query clocks, pauses, and delegation periods. Duration arithmetic requires a common time origin and policy for excluded intervals; it does not authenticate records or establish acceptable trial conduct.

Return entry lag, correction lag or zero, and late when entry lag strictly exceeds the maximum.

When to use this tool

Use GCP Source Entry Late Entry Lag when you need an explicit clinical-trial record-duration or overlap calculation.

How to use the tool and how it works

Enter eventDay, enteredDay, correctionDay, corrected, suppliedMaximum. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read entryLag, correctionLag, late. Inspect late before interpreting the associated values.

Require nonnegative integer suppliedMaximum, enteredDay at least eventDay, and correctionDay at least enteredDay only when corrected is true. Return entry lag, correction lag or zero, and late when entry lag strictly exceeds the maximum.^[1]

Input field	Meaning and units	Accepted input
eventDay	Event Day	Required. Safe integer.
enteredDay	Entered Day	Required. Safe integer.
correctionDay	Correction Day	Required. Safe integer.
corrected	Corrected	Required. Boolean.
suppliedMaximum	Supplied Maximum	Required. Safe integer; minimum 0.

Output field	Interpretation	Returned shape
entryLag	Entry Lag	Required. Safe integer.
correctionLag	Correction Lag	Required. Safe integer.
late	Late	Required. Boolean.

json

{
  "input": {
    "eventDay": 100,
    "enteredDay": 103,
    "correctionDay": 110,
    "corrected": true,
    "suppliedMaximum": 2
  },
  "output": {
    "entryLag": 3,
    "correctionLag": 7,
    "late": true
  }
}

Limitations and assumptions

Day values share an origin and correctionDay is ignored by the chronology check when corrected is false. The limit is caller supplied and zero correction lag may be a placeholder; no GCP deadline or acceptability is determined.
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.
Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the trial protocol, controlled records, and relevant procedures for actual decisions. Resolve time units, clock references, pause authorization, and source evidence before applying a timing rule.

References

Calculation and input contract: gcp/gcp-source-entry-late-entry-lag — tool.io

Similar or alternative tools

GCP Ecrf Edit Original Correction Link
Compare recordId with parentId, require a nonblank trimmed reason for reasonPresent, a positive-length authorId for attributed, and editTimestamp at least originalTimestamp for chronological.
Trial Document Age At Event
Return eventAt minus documentAt as age and flag futureDocument when documentAt is later than eventAt.