Gynecologic Record Original Collection Key Tool

Description

Compare original with parent and return JSON-array keys for original/collection and original/collection/revision.

Gynecologic research and care records can contain specimen labels, questionnaire states, source keys, and consent flags. A local metadata check preserves a supplied convention without determining a clinical finding or verifying permission.

Compare original with parent and return JSON-array keys for original/collection and original/collection/revision.

When to use this tool

Use Gynecologic Record Original Collection Key when you need one explicit research-record or permission-metadata component.

How to use the tool and how it works

Enter originalId, collectionId, revisionId, parentOriginalId. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read sameOriginal, collectionKey, revisionKey. Inspect sameOriginal before interpreting the associated values.

Require nonempty original, collection, revision, and parent-original identifiers. Compare original with parent and return JSON-array keys for original/collection and original/collection/revision.^[1]

Input field	Meaning and units	Accepted input
originalId	Original Id	Required. Text; maximum UTF-16 length 8192.
collectionId	Collection Id	Required. Text; maximum UTF-16 length 8192.
revisionId	Revision Id	Required. Text; maximum UTF-16 length 8192.
parentOriginalId	Parent Original Id	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
sameOriginal	Same Original	Required. Boolean.
collectionKey	Collection Key	Required. Text; maximum UTF-16 length 8192.
revisionKey	Revision Key	Required. Text; maximum UTF-16 length 8192.

json

{
  "input": {
    "originalId": "R1",
    "collectionId": "C1",
    "revisionId": "v2",
    "parentOriginalId": "R1"
  },
  "output": {
    "sameOriginal": true,
    "collectionKey": "[\"R1\",\"C1\"]",
    "revisionKey": "[\"R1\",\"C1\",\"v2\"]"
  }
}

Limitations and assumptions

Revision does not enter collectionKey; literal identifiers do not authenticate record lineage, specimen identity, legal permission, or clinical correctness.
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 records, privacy and consent requirements, and appropriate professional interpretation before clinical or contact decisions.

References

Calculation and input contract: gynecology/gynecologic-record-original-collection-key — tool.io

Similar or alternative tools

Pharmacy Aseptic Record Label Version Pair
Compare recordId with labelParent and recordVersion with labelVersion, then flag a released record when either comparison fails.
FHIR Identifier System Value Pair
Return their JSON-array key.