Description
Return their overlap as coveredDays, activity duration minus overlap as uncoveredDays, and fullyCovered when activity bounds lie inside approval bounds.
Good clinical practice record checks compare supplied versions, language labels, roles, dates, and source links. A local metadata match can reveal consistency but does not establish valid consent, competent authorization, or regulatory compliance.
Return their overlap as coveredDays, activity duration minus overlap as uncoveredDays, and fullyCovered when activity bounds lie inside approval bounds.
When to use this tool
Use GCP Ethics Approval Effective Period Overlap when you need a literal clinical-trial metadata consistency check.
How to use the tool and how it works
- Enter activityStart, activityEnd, approvalStart, approvalEnd. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read coveredDays, uncoveredDays, fullyCovered. Inspect fullyCovered before interpreting the associated values.
Require ordered activity and approval intervals. Return their overlap as coveredDays, activity duration minus overlap as uncoveredDays, and fullyCovered when activity bounds lie inside approval bounds.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| activityStart | Activity Start | Required. Safe integer. |
| activityEnd | Activity End | Required. Safe integer. |
| approvalStart | Approval Start | Required. Safe integer. |
| approvalEnd | Approval End | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| coveredDays | Continuous numeric day-coordinate intersection length, without inclusive-date counting. | Required. Safe integer. |
| uncoveredDays | Uncovered Days | Required. Safe integer. |
| fullyCovered | Fully Covered | Required. Boolean. |
{
"input": {
"activityStart": 100,
"activityEnd": 120,
"approvalStart": 90,
"approvalEnd": 115
},
"output": {
"coveredDays": 15,
"uncoveredDays": 5,
"fullyCovered": false
}
}Limitations and assumptions
- Numeric endpoints use consistent day units and duration subtraction, without inclusive-date counting. A zero-duration activity outside approval can have zero uncoveredDays yet fullyCovered false; no approval authenticity, scope, or legal validity 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.
- 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
Review the complete controlled trial records and applicable professional process. Verify authenticity, protocol scope, consent, competence, and effective versions through the appropriate responsible reviewers.
References
Similar or alternative tools
- Delegation Period Overlap Share
Return overlap duration and overlap divided by the activity duration.
- GCP Visit Window Precision Token
Return certainlyInside when the entire visit interval is contained and possiblyInside when their closed intervals overlap inclusively.