Skip to content

Main content

Pharmacy Care Plan Follow Up Date

Add a caller-supplied calendar-day offset to an explicit care-plan reference date without choosing a follow-up interval.

Loading tool…

Description

Shift a supplied care-plan reference date by signed calendar days.

Clinical pharmacy records preserve medication wording, source dates, supply quantities and reconciliation states. Calendar shifts count weekends unless another rule is explicitly implemented. A supplied discrepancy or dose text describes a record rather than a verified medication history or a recommended regimen.

Shift a supplied care-plan reference date by signed calendar days.

When to use this tool

Use Pharmacy Care Plan Follow Up Date when you already have referenceDate, offsetDays and need to shift a supplied care-plan reference date by signed calendar days.

How to use the tool and how it works

  1. Enter referenceDate, offsetDays. 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 followupDate. Use the output convention below.

Parse a real UTC date and require a signed safe integer offset; add days and require a real result in years 0000..9999.1

Input fieldMeaning and unitsAccepted input
referenceDateReference DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
offsetDaysSigned whole calendar-day offset, including weekends; output must remain in four-digit year range.Required. Safe integer.
Output fieldInterpretationReturned shape
followupDateFollowup DateRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "referenceDate": "2026-10-28",
    "offsetDays": 4
  },
  "output": {
    "followupDate": "2026-11-01"
  }
}

Limitations and assumptions

  • Weekends and holidays count. No appointment, prescription, follow-up need, safe interval or appropriate care plan is selected.
  • 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

Reconcile the original medication, prescription and clinical records through the appropriate professional process. Check actual preparation, supply and patient context; local label formatting and arithmetic do not establish dose safety, therapeutic equivalence or permission to dispense.

References

  1. Calculation and input contract: clinical-pharmacy/pharmacy-care-plan-follow-up-date — tool.io

Similar or alternative tools