Description
Calculate the signed time gap between participant and investigator consent signatures.
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.
Calculate the signed time gap between participant and investigator consent signatures.
When to use this tool
Use GCP Consent Signature Time Pair when checking the stated benign clinical-research record or date convention.
How to use the tool and how it works
- Enter consentVersion, participantSignatureSeconds, investigatorSignatureSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read investigatorMinusParticipantSeconds, token. Use the output convention below.
Require nonempty consentVersion. Return investigator-minus-participant signature time in seconds and encode [version,participantSeconds,investigatorSeconds] as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| consentVersion | Consent Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| participantSignatureSeconds | Participant Signature Seconds | Required. Finite number. |
| investigatorSignatureSeconds | Investigator Signature Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| investigatorMinusParticipantSeconds | Signed investigator-signature minus participant-signature time; no required ordering is imposed. | Required. Finite number. |
| token | JSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"consentVersion": "v2",
"participantSignatureSeconds": 1000,
"investigatorSignatureSeconds": 1060
},
"output": {
"investigatorMinusParticipantSeconds": 60,
"token": "[\"v2\",1000,1060]"
}
}Limitations and assumptions
- Times may be signed and no required order is enforced; numerical concordance does not verify signatures or valid informed consent.
- 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 verified protocols, consent and source records under the applicable complete research requirements with qualified responsible personnel for actual study or participant decisions.
References
Similar or alternative tools
- GCP Reconsent Version Label
Identify a supplied clinical-research reconsent version.
- GCP Delegation Task Effective Flag
Check a recorded delegation flag within a closed supplied effective-date interval.