Description
Record receipt of a clinical-study safety communication using a supplied code.
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.
Record receipt of a clinical-study safety communication using a supplied code.
When to use this tool
Use GCP Safety Letter Receipt Code when checking the stated benign clinical-research record or date convention.
How to use the tool and how it works
- Enter letterId, recipientId, receiptCode. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Require nonempty safety-letter ID, recipient ID and receipt code. Encode the ordered triple as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| letterId | Letter Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| recipientId | Recipient Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| receiptCode | Receipt Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| 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": {
"letterId": "L17",
"recipientId": "SITE2",
"receiptCode": "acknowledged"
},
"output": {
"token": "[\"L17\",\"SITE2\",\"acknowledged\"]"
}
}Limitations and assumptions
- The code does not prove receipt, awareness, an appropriate safety response or compliance with reporting obligations.
- 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
Similar or alternative tools
- GCP Signature Authority Role
Record the stated authority role attached to a clinical-research signature.
- GCP Reconsent Version Label
Identify a supplied clinical-research reconsent version.