Description
Compare exact report/version pairs without treating updates as independent safety cases.
Drug-utilization research often reconstructs exposure from dispensing dates, supplied coverage windows, coding systems, and eligibility records. Day counts depend on endpoint and stockpiling policies. Observed records, assumed exposure, and actual medication consumption are different quantities.
Compare exact report/version pairs without treating updates as independent safety cases.
When to use this tool
Use Safety Report Duplicate Version Suffix Flag when you need this explicit exposure-record, date-window, reporting-base, or evidence-support calculation.
How to use the tool and how it works
- Enter reportId, suffix, knownReportIds, knownSuffixes. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read duplicateVersion, priorReport, key. Inspect duplicateVersion, priorReport before interpreting the associated values.
Require aligned knownReportIds and knownSuffixes. Return duplicateVersion for an exact reportId/suffix pair match, priorReport if any known ID matches, and key=JSON.stringify([reportId,suffix]).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reportId | Report Id | Required. Text; maximum UTF-16 length 8192. |
| suffix | Suffix | Required. Text; maximum UTF-16 length 8192. |
| knownReportIds | Known Report Ids | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| knownSuffixes | Known Suffixes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| duplicateVersion | Duplicate Version | Required. Boolean. |
| priorReport | Prior Report | Required. Boolean. |
| key | Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"reportId": "R1",
"suffix": "v2",
"knownReportIds": [
"R1",
"R1"
],
"knownSuffixes": [
"v1",
"v2"
]
},
"output": {
"duplicateVersion": true,
"priorReport": true,
"key": "[\"R1\",\"v2\"]"
}
}Limitations and assumptions
- Suffixes are compared as strings without ordering or version parsing. A matching identifier does not establish that reports describe the same event or that the record is complete and authoritative.
- 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
Choose a documented exposure and eligibility definition for the study before combining records. Verify the coding version, observation windows, endpoint convention, and the evidence for assumptions about carried supply.
References
Similar or alternative tools
- Guideline Source Version Dategap
Compare supplied source-version tokens and resolved day indices without clinical guideline interpretation.
- Osteopathic Evidence Retraction Parent Pair
Link explicit publication notices without retrieving or adjudicating them.