Sabin-Feldman Dye Test Titer Reciprocal Recorder
Record a separately identified Sabin-Feldman reciprocal titer; no automated endpoint reading or infection timing.
Description
Record a separately identified Sabin-Feldman reciprocal titer; no automated endpoint reading or infection timing.
A serologic endpoint is commonly recorded by its reciprocal dilution. Whether the endpoint is known is separate from the numerical value a form requires.
When to use this tool
Record a separately identified Sabin-Feldman reciprocal titer; no automated endpoint reading or infection timing.
- Prepare the supplied reciprocalEndpoint, endpointKnown 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
- Enter reciprocalEndpoint, endpointKnown. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.recordedReciprocal, result.diagnosis. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require reciprocalEndpoint greater than zero. Return that value when endpointKnown is true and null otherwise, while always returning diagnosis not-established.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| reciprocalEndpoint | reciprocal endpoint. | Finite number; greater than zero |
| endpointKnown | Explicit choice for endpoint known; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.recordedReciprocal | The recorded reciprocal value under the stated formula or text convention. |
| result.diagnosis | Always not-established: this operation does not establish a diagnosis. |
{
"input": {
"reciprocalEndpoint": 16,
"endpointKnown": true
},
"output": {
"result": {
"recordedReciprocal": 16,
"diagnosis": "not-established"
}
}
}Limitations and assumptions
- Even an unknown endpoint still requires a valid positive numeric field. The tool does not read an assay, determine an endpoint, interpret timing of infection or diagnose disease.
- 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
Combine recorded observations with a validated method, appropriate controls and the complete specimen context. Use original qualified references when reviewing species, stages or product information; a supplied-record match, sample ratio or historical flag is only the stated piece of evidence.
References
Similar or alternative tools
- Circulating Filarial Antigen Test Positive-Negative Binary Recorder
Record a supplied antigen-line observation with explicit observation and control validity.
- Gonotrophic Cycle Days Duration Recorder
Record observed gonotrophic-cycle elapsed calendar days, not a species-default duration.