Description
Require receivedTimestampSeconds no earlier than sentTimestampSeconds and return their difference.
Care-service administration records appointments, referrals, reimbursements, and contact arrangements. Formatting or comparing these fields supports record keeping; it does not assess a person's needs or replace a professional care decision.
Require receivedTimestampSeconds no earlier than sentTimestampSeconds and return their difference.
When to use this tool
Use Case Handoff Receipt Delay when you need one administrative calculation or label from supplied care-service records.
How to use the tool and how it works
- Enter sentTimestampSeconds, receivedTimestampSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read delaySeconds. Use the output convention below.
Require receivedTimestampSeconds no earlier than sentTimestampSeconds and return their difference.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sentTimestampSeconds | Sent Timestamp Seconds | Required. Finite number. |
| receivedTimestampSeconds | Received Timestamp Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| delaySeconds | Delay Seconds | Required. Finite number. |
{
"input": {
"sentTimestampSeconds": 1000,
"receivedTimestampSeconds": 1090
},
"output": {
"delaySeconds": 90
}
}Limitations and assumptions
- Clocks must share an origin and be synchronized; a receipt delay does not establish service quality, urgency, or case acceptance.
- 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 responsible service's complete workflow and consult an appropriate professional for care decisions.
References
Similar or alternative tools
- Message Ack Delay Pair
Require acknowledgedTimeSeconds no earlier than sentTimeSeconds and subtract for delaySeconds.
- Humanitarian Notification Delay
Require notifiedTimestampSeconds no earlier than eventTimestampSeconds and return their difference.