Description
Expose whether a supplied clinical datetime offset is known and can be applied.
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.
Expose whether a supplied clinical datetime offset is known and can be applied.
When to use this tool
Use Clinical Datetime Offset Known Flag when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter offsetKnown, suppliedOffsetMinutes. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read canApplyOffset, appliedOffsetMinutes. Inspect canApplyOffset before interpreting the associated values.
Return canApplyOffset=offsetKnown and the supplied offset in minutes only when known, otherwise zero.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| offsetKnown | Offset Known | Required. Boolean. |
| suppliedOffsetMinutes | Supplied Offset Minutes | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| canApplyOffset | Can Apply Offset | Required. Boolean. |
| appliedOffsetMinutes | Supplied signed minutes when offsetKnown, otherwise zero placeholder; no datetime is changed. | Required. Finite number. |
{
"input": {
"offsetKnown": false,
"suppliedOffsetMinutes": 60
},
"output": {
"canApplyOffset": false,
"appliedOffsetMinutes": 0
}
}Limitations and assumptions
- Zero can be a placeholder or a known zero offset; no timestamp is parsed, converted or proven comparable across clocks.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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
Similar or alternative tools
- FHIR Timestamp Precision Tag
Attach a caller-declared precision label to FHIR-related timestamp text.
- HL7 Null Empty Value Distinction
Distinguish the raw HL7 two-quote null indicator, empty text and other values.