Research consent version reconciliation calculator

Calculate missing signed-record IDs and outdated or differing version IDs with your own figures.

Your numbers

Use the units shown. Results update as you change valid inputs.

Use missing signed-record IDs and outdated or differing version IDs to compare changes to your inputs. The method and limits below explain the scope.

Examples

Examples

Try the starting example

JSON Participants [ID,signed version or empty string]
[["A","v2"],["B","v1"],["C",""]]
Required protocol consent version
v2
Missing signed-record IDs
["C"]
Outdated or differing version IDs
["B"]
Exact-version record coverage
0.333333

Try another scenario

JSON Participants [ID,signed version or empty string]
[["A","v2"],["B","v2"],["C",""]]
Required protocol consent version
v2
Missing signed-record IDs
["C"]
Outdated or differing version IDs
[]
Exact-version record coverage
0.666667
Calculation method

Calculation method

Missing signed-record IDs

J([r[0] for r in a if r[1]==""])

Outdated or differing version IDs

J([r[0] for r in a if r[1] and r[1]!=b])

Exact-version record coverage

sum(r[1]==b for r in a)/len(a)

Symbols and units
a
JSON Participants [ID,signed version or empty string]
b
Required protocol consent version

Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.

Calculation steps and notation

sum(list) adds all entries in the list.

Assumptions & limits

Assumptions & limits

  • Exact supplied consent-version reconciliation only. A matching record is not a judgment that consent is valid or adequate. Supported limits: All numeric inputs must be finite. Only the explicitly described mathematical scenario is supported.
Are these inputs private?

These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.

Share this page
Share this calculator

Leave unchecked to share the page without your entered values.