Description
Build an unambiguous key from explicit adverse-event identifiers.
Medication-study records distinguish supplied coverage intervals, observed person-days, dispensing reversals and source event definitions. Inclusive calendar-day counting differs from continuous elapsed time. Recorded supply and washout flags are study conventions rather than evidence of ingestion, drug clearance, causal effect or suitable treatment.
Build an unambiguous key from explicit adverse-event identifiers.
When to use this tool
Use Adverse Event Report Duplicate Key when you already have reporterCaseId, eventRecordId, sourceSystem and need to build an unambiguous key from explicit adverse-event identifiers.
How to use the tool and how it works
- Enter reporterCaseId, eventRecordId, sourceSystem. 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.
Enter reporterCaseId, eventRecordId, sourceSystem using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reporterCaseId | Reporter Case Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| eventRecordId | Event Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceSystem | Source System | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"reporterCaseId": "CASE17",
"eventRecordId": "EV2",
"sourceSystem": "Registry A"
},
"output": {
"token": "[\"CASE17\",\"EV2\",\"Registry A\"]"
}
}Limitations and assumptions
- The result records supplied values without probabilistic duplicate detection. Sources and asserted relationships are not independently authenticated.
- 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
Construct exposure episodes from a documented study rule and verified dispensing or observation history. Keep inclusive calendar coverage distinct from elapsed time and actual ingestion; evaluate causal questions with a complete study design rather than one interval flag.
References
Similar or alternative tools
- Safety Report Seriousness Source Label
Preserve explicitly reported seriousness wording and source.
- Exposure Episode Start Tag
Tag an explicit exposure episode with its supplied start reason.