Skip to content

Main content

Clinical Dataset Absent Reason Value Conflict Tool

Audit a supplied value-versus-absent-reason exclusivity rule without interpreting a diagnosis or an absent-reason vocabulary.

Loading tool…

Description

Flag conflict for both value and absent reason, missingRequired for required data with neither, and exactlyOne when one presence flag is true.

Clinical record metadata can describe names, values, missing reasons, versions, and source relationships. Formatting or checking presence preserves supplied structure without authenticating a person or validating clinical content.

Flag conflict for both value and absent reason, missingRequired for required data with neither, and exactlyOne when one presence flag is true.

When to use this tool

Use Clinical Dataset Absent Reason Value Conflict when you need one bounded metadata-formatting or consistency component.

How to use the tool and how it works

  1. Enter hasValue, hasAbsentReason, required. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read conflict, missingRequired, exactlyOne. Inspect conflict, missingRequired, exactlyOne before interpreting the associated values.

Flag conflict for both value and absent reason, missingRequired for required data with neither, and exactlyOne when one presence flag is true.1

Input fieldMeaning and unitsAccepted input
hasValueHas ValueRequired. Boolean.
hasAbsentReasonHas Absent ReasonRequired. Boolean.
requiredRequiredRequired. Boolean.
Output fieldInterpretationReturned shape
conflictConflictRequired. Boolean.
missingRequiredMissing RequiredRequired. Boolean.
exactlyOneExactly OneRequired. Boolean.
json
{
  "input": {
    "hasValue": true,
    "hasAbsentReason": true,
    "required": true
  },
  "output": {
    "conflict": true,
    "missingRequired": false,
    "exactlyOne": false
  }
}

Limitations and assumptions

  • Flags describe supplied metadata without inspecting a value, reason code, clinical record, or applicable FHIR profile; missingRequired and exactlyOne answer different questions.
  • 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 the complete record, privacy requirements, implementation profile, and verified source context.

References

  1. Calculation and input contract: health-informatics/clinical-dataset-absent-reason-value-conflict — tool.io

Similar or alternative tools