Skip to content

INDUSTRY FIELD GUIDE

Dialysis center session status and reporting records for AI

A schedule shows intended sessions.

By Fiund · Updated 2026-11-05

NAICS 621492 · Kidney Dialysis Centers

A schedule shows intended sessions. Attendance or completion needs a matching event. CMS publishes dialysis quality measurement resources. A center can use an original scheduling example to test whether software keeps planned, rescheduled and completed states separate. CMS dialysis quality measures

Build a mock weekly schedule with a rescheduled session and a completion entry in the next reporting period. Include a second planned session with no completion record. Ask the model which events the supplied evidence supports and which period each belongs to. Give reviewers an explicit date and status key.

Use invented session labels and dates. Exclude patient schedules, treatment data, machine settings and staff communications. Keep the exercise on records, with no advice about dialysis or quality determinations.

Describe a synthetic session records exercise

Original Fiund exercise

A rescheduled session belongs to the period of its documented event

A fictitious scheduling table uses abstract session IDs and original reporting windows. It contains no patient schedule, treatment, machine setting or quality determination.

Fictional records supplied to the evaluator
RecordSourceWhat it records
DY1Practice periods and schedulePeriod P1 days 1–7; P2 days 8–14. Session A originally planned day 7, session B day 6.
DY2A revision and eventA rescheduled to day 8. Separate original completion card explicitly names A and day 8; supersedes the planned day-7 slot only as a schedule change.
DY3B recordDay-6 planned slot remains, completion field blank. No event card for B supplied.

Question for the model

Which period contains A's documented completion, and can B's scheduled slot be counted as a completed event?

Show the reference answer and checks

DY2 documents A's completion on day 8, within DY1's P2 window, despite the original day-7 P1 plan. A's rescheduling and completion are separate records. DY3 supplies only B's planned day-6 slot, so P1 has no supported B completion from this packet. Preserve event date and state instead of counting intended appointments as observed events or making a care or quality conclusion from missing documentation.

  • Counting completion in the original scheduled period after rescheduling.
  • Treating a planned session or blank completion field as a confirmed event or clinical outcome.

Fields to preserve

Session and schedule version
Preserves the intended timeline.
Completion event and date
Defines the observed state.
Reporting-window rule and missing evidence
Supports correct period assignment.

Test another case

Add a day-8 cancellation rather than completion. Require its period to be identified while the completed-event count stays unchanged.

Use invented dates and session labels. Exclude patient and treatment information, communications and settings; the task provides no dialysis advice or official quality measure.

Download this fictional example and answer key (JSON)

Discuss a contribution

Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.

Primary sources and further reading