Type 2 Gap Coverage

Measure the uncovered gap between Type 2 report periods.

Description

Type 2 reporting gaps depend on days between consecutive covered periods.

Type 2 reporting gaps depend on days between consecutive covered periods. Endpoint dates are excluded from the gap.^[1]

Measure the uncovered gap between Type 2 report periods.

When to use Type 2 Gap Coverage

Use this tool to measure the uncovered gap between Type 2 report periods.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use Type 2 Gap Coverage and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter priorReportEndDate, currentReportStartDate, coveredGapDays using the field table and calculation rules, then run the tool.
Read calendarGapDays, uncoveredGapDays, fullyCovered. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
priorReportEndDate	Prior report end date	string	Required
currentReportStartDate	Current report start date	string	Required
coveredGapDays	Gap days covered by other procedures	integer; minimum: 0	Required

Enter date-only strings parsed at UTC midnight with current start≥prior end and nonnegative integer covered days. Return gap/uncovered/fully-covered flag.

gap=max(0,floor((start−end)/day)−1); uncovered=max(0,gap−covered)

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
calendarGapDays	Calendar gap days	integer; minimum: 0
uncoveredGapDays	Uncovered gap days	integer; minimum: 0
fullyCovered	Gap fully covered	boolean

json

{
  "input": {
    "priorReportEndDate": "2025-01-01",
    "currentReportStartDate": "2025-01-12",
    "coveredGapDays": 10
  },
  "output": {
    "calendarGapDays": 10,
    "uncoveredGapDays": 0,
    "fullyCovered": true
  }
}

Limitations and assumptions

Native date normalization applies. Covered-day count is not mapped to specific dates; no bridge evidence or assurance sufficiency is assessed.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Trust-Criteria Coverage: Audit trust-services criteria coverage. For a complementary task, use CUEC Coverage: Audit complementary user-entity control coverage.

References

Type 2 Gap Coverage — tool.io

Similar or alternative tools

Trust-Criteria Coverage
Audit trust-services criteria coverage.
CUEC Coverage
Audit complementary user-entity control coverage.