Skip to content

Main content

GCP Ecrf Edit Original Correction Link Tool

Audit explicit eCRF edit attribution and chronology without rewriting records.

Loading tool…

Description

Compare recordId with parentId, require a nonblank trimmed reason for reasonPresent, a positive-length authorId for attributed, and editTimestamp at least originalTimestamp for chronological.

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.

Compare recordId with parentId, require a nonblank trimmed reason for reasonPresent, a positive-length authorId for attributed, and editTimestamp at least originalTimestamp for chronological.

When to use this tool

Use GCP Ecrf Edit Original Correction Link when you need a literal clinical-trial metadata consistency check.

How to use the tool and how it works

  1. Enter recordId, parentId, reason, authorId, originalTimestamp, editTimestamp. 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 linked, reasonPresent, attributed, chronological. Inspect linked, reasonPresent, attributed, chronological before interpreting the associated values.

Compare recordId with parentId, require a nonblank trimmed reason for reasonPresent, a positive-length authorId for attributed, and editTimestamp at least originalTimestamp for chronological.1

Input fieldMeaning and unitsAccepted input
recordIdRecord IdRequired. Text; maximum UTF-16 length 8192.
parentIdParent IdRequired. Text; maximum UTF-16 length 8192.
reasonSupplied explanatory text; presence does not verify its truth or adequacy.Required. Text; maximum UTF-16 length 8192.
authorIdAuthor IdRequired. Text; maximum UTF-16 length 8192.
originalTimestampOriginal TimestampRequired. Finite number.
editTimestampEdit TimestampRequired. Finite number.
Output fieldInterpretationReturned shape
linkedLinkedRequired. Boolean.
reasonPresentReason PresentRequired. Boolean.
attributedTrue for any positive-length authorId, including whitespace-only text.Required. Boolean.
chronologicalChronologicalRequired. Boolean.
json
{
  "input": {
    "recordId": "R1",
    "parentId": "R1",
    "reason": "typo",
    "authorId": "A",
    "originalTimestamp": 100,
    "editTimestamp": 105
  },
  "output": {
    "linked": true,
    "reasonPresent": true,
    "attributed": true,
    "chronological": true
  }
}

Limitations and assumptions

  • Whitespace-only author IDs count as attributed while reasons are trimmed. Flags are separate metadata checks, not an authenticated audit trail, identity verification, or evidence that an electronic case-report-form edit is compliant.
  • 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

  1. Calculation and input contract: gcp/gcp-ecrf-edit-original-correction-link — tool.io

Similar or alternative tools

  • GCP Source Entry Late Entry Lag

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

  • GCP Consent Version Visit Date Order

    Compare consentVersion exactly with requiredVersion, test signedDay no later than visitDay and no earlier than versionEffectiveDay, and return recordMatches only when all checks pass and withdrawn is false.