Capsule Negative Stain Halo Presence Detector

Record independently observed Capsule Negative Stain Halo Presence Detector evidence with explicit knownness and valid controls. Does not inspect images, infer species, diagnose infection or recommend treatment.

Description

Record supplied capsule-halo evidence without inspecting microscopy or confirming a capsule.

A capsule-like halo is an observed microscopy feature rather than a complete biological identification. Recording whether the observation and controls are valid keeps the feature label appropriately limited.

When to use this tool

Record supplied capsule-halo evidence without inspecting microscopy or confirming a capsule.

  • Prepare the supplied capsuleHalo, observationKnown, controlValid fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter capsuleHalo, observationKnown, controlValid. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.assayObservation, result.diagnosticConclusion. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Supply capsuleHalo as true for the observed feature or false for its observed absence, together with explicit observationKnown and controlValid booleans. Return assayObservation indeterminate if observationKnown is false or controlValid is false; otherwise return positive when capsuleHalo is true and negative when false. Return diagnosticConclusion as not-established in every case. No image processing or measurement is performed.1

Input fieldMeaning and representationAccepted input
capsuleHaloExplicit choice for capsule halo; supply a boolean rather than a text label.true or false
observationKnownTrue only when the feature observation is actually known; false preserves an indeterminate/unknown outcome.true or false
controlValidWhether the relevant assay control or observation-validity condition is established.true or false
Output fieldInterpretation
resultObject containing the named outputs below.
result.assayObservationPositive or negative only when both observation and control validity are established; indeterminate otherwise.
result.diagnosticConclusionAlways not-established: the recorded feature does not establish a diagnosis.
json
{
  "input": {
    "capsuleHalo": true,
    "observationKnown": true,
    "controlValid": true
  },
  "output": {
    "result": {
      "assayObservation": "positive",
      "diagnosticConclusion": "not-established"
    }
  }
}

Limitations and assumptions

  • The tool does not inspect images, stain a sample or confirm a capsule. capsuleHalo is supplied by the caller, and diagnosticConclusion remains not-established.
  • Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
  • Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
  • Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Retain specimen context, controls and independently observed features alongside a test label. Use a complete validated identification or analytical workflow when conclusions require several assays; a single stored morphology definition, feature flag or threshold comparison does not identify an organism.

References

  1. Tool behavior and example: Capsule Negative Stain Halo Presence Detector — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies