Skip to content

Main content

Clinical Result Status Transition Pair

Check a recorded result-status transition against an explicit caller-supplied transition list without inventing workflow rules.

Loading tool…

Description

Check a recorded result-status change against supplied allowed transition pairs.

Health-information systems separate identifiers, code-system namespaces, source versions, missing-value states and reference syntax. Recording a mapping or recognizing a restricted token does not validate its clinical meaning or a complete HL7/FHIR resource. Explicit null, empty text, unknown status and numeric zero are different states.

Check a recorded result-status change against supplied allowed transition pairs.

When to use this tool

Use Clinical Result Status Transition Pair when checking the stated restricted health-data record, token or transition convention.

How to use the tool and how it works

  1. Enter previousStatus, nextStatus, allowedFrom, allowedTo. Follow any array-alignment requirements below. 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 changed, listedTransition. Inspect changed, listedTransition before interpreting the associated values.

Require aligned allowedFrom/allowedTo arrays and nonempty previous/next statuses. changed compares the statuses; listedTransition means at least one aligned pair matches both.1

Input fieldMeaning and unitsAccepted input
previousStatusPrevious StatusRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
nextStatusNext StatusRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
allowedFromAllowed FromRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
allowedToAllowed ToRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
changedChangedRequired. Boolean.
listedTransitionAn aligned allowedFrom/allowedTo pair matches; a self-transition may be listed even when changed=false.Required. Boolean.
json
{
  "input": {
    "previousStatus": "preliminary",
    "nextStatus": "final",
    "allowedFrom": [
      "preliminary"
    ],
    "allowedTo": [
      "final"
    ]
  },
  "output": {
    "changed": true,
    "listedTransition": true
  }
}

Limitations and assumptions

  • A listed self-transition can be unchanged; the supplied transition list does not define a verified clinical workflow or alter records.
  • 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

Use the intended complete interoperability specification, authoritative terminology and verified source records for actual resource validation, semantic mapping or clinical use.

References

  1. Calculation and input contract: health-informatics/clinical-result-status-transition-pair — tool.io

Similar or alternative tools