Hospice software for interdisciplinary documentation workflows addresses a specific operational problem: the IDG must review and revise each patient's plan of care at least every 15 calendar days, and every discipline must document its contribution in a retrievable form [3]. Vendors approach this differently. KanTime describes automated flow of assessment items and visit-note updates into the IDG note [1]. Axxess describes automated IDG workflows and embedded HOPE reminders [4]. Netsmart describes agenda automation and a single patient record across roles [8]. The underlying regulatory requirement is stable, but the software mechanisms, configuration burden, and evidence quality vary. This guide explains the named workflow, the technical decision points that matter during evaluation, and what the available documentation can and cannot establish.

The Regulatory Workflow the Software Must Support

The Medicare hospice Conditions of Participation require the interdisciplinary group to review, revise, and document the individualized plan of care as frequently as the patient's condition requires, but no less often than every 15 calendar days [3]. A revised plan must incorporate information from the updated comprehensive assessment and note the patient's progress toward outcomes and goals [3]. The hospice must also maintain a system of communication and integration that ensures ongoing sharing of information between all disciplines in all settings, whether care is provided directly or under arrangement [3]. These requirements create the documentation workflow that software is expected to support.

CMS guidance identifies common survey deficiencies tied to this workflow. An OIG report found that plans of care were not individualized, staff missed direct-care visits, visit documentation did not meet requirements, plans were incomplete, and IDG meetings were inconsistent with plans not being updated [5]. CHAP standards similarly require policies and procedures that define a system of communication and integration sustaining coordination of services and documenting exchange of information [2]. Software cannot by itself correct these deficiencies, but the documented workflow should show how the system makes the required review, revision, and cross-discipline sharing visible and auditable.

How Vendor Platforms Describe the IDG Documentation Flow

KanTime describes a flow in which items identified as IDG during the initial assessment, updates added during follow-up visit notes, and change orders are automatically flown to the IDG meeting for inclusion in the IDG note [1]. Clinicians can write orders, change frequencies, and update the care plan without leaving the IDG meeting [1]. Each IDG member is prompted to document pertinent information on an individual section of the IDG note [1]. The vendor also states that agencies using KanTime report IDG meetings completed in one afternoon and often in as little as three hours [1]. These are vendor-reported operational claims, not independently verified outcomes.

Axxess describes automated IDG workflows that ensure meetings have comprehensive records, embedded guidance and reminders for HOPE requirements, and integrated IDG workflows that eliminate duplicate documentation [4]. The vendor also describes centralized patient workflows and connected clinical and bereavement workflows [4]. Netsmart describes automation of meeting agenda development, a clinical summary that places relevant details at care teams' fingertips, and data compiled from a single patient record across roles and settings [8]. The vendor also states that patient records can be updated efficiently during meetings [8]. Each vendor emphasizes a different mechanism: KanTime on automatic item flow, Axxess on embedded regulatory guidance, and Netsmart on the single cross-setting record.

Mapping the 15-Day Review to Software Events

A practical way to evaluate a system is to map the 15-day review requirement to specific software events. The facilitator should be able to identify patients whose subsequent IDG review is due today, due in one to three days, or due in four to seven days [6]. The system should also identify patients who have not had an initial IDG review and patients discharged since the last meeting who need a final review [6]. For each patient, the facilitator should be able to create a plan of care update, and each discipline should be able to write its note before or during the meeting [6].

The evaluation should confirm that the revised plan includes information from the updated comprehensive assessment and notes progress toward outcomes [3]. It should also confirm that the system documents the patient's or representative's level of understanding, involvement, and agreement with the plan [5]. If the system cannot produce a report showing which patients are due for review within the next seven days, the facilitator will need a manual workaround, which reintroduces the preparation burden the software is meant to reduce.

Technical Decision Points for Evaluation

A first decision point is where the IDG note originates. In the Epic workflow dress rehearsal, the facilitator creates a Plan of Care Update from a report showing patients needing initial or subsequent review, and other disciplines then add documentation before the meeting [6]. During the meeting, the facilitator refreshes the plan to view notes written during prep, and at least one discipline updates a note while the facilitator reviews changes [6]. This sequence assumes a facilitator role and a shared plan object that multiple disciplines can edit. Evaluators should ask whether the candidate system uses a similar shared object or a separate note per discipline.

A second decision point is how the system handles settings where the patient resides in a nursing home. Wisconsin guidance states that the coordinated plan of care may be divided into two portions, one maintained by the nursing home and the other by the hospice, and both portions should reflect a common problem list, palliative interventions, palliative outcomes, responsible discipline, responsible provider, and patient goals [7]. The hospice IDG establishes and maintains the hospice portion in consultation with nursing home staff [7]. Software that assumes a single hospice-owned record may not map cleanly to this shared-responsibility model. Evaluators should test how the system represents the hospice portion without implying ownership of the nursing home portion.

Evidence Limitations in Vendor Documentation

The available vendor materials are marketing and training documents, not comparative studies. KanTime's claim that IDG meetings are completed in as little as three hours is attributed to agencies utilizing KanTime, but no sample size, denominator, or measurement method is provided [1]. Axxess states that automated IDG workflows ensure meetings always have comprehensive records, but the documentation does not define comprehensive or provide audit results [4]. Netsmart states that CHAP verification confirms readiness to support compliant care, but the verification scope and criteria are not detailed in the retrieved page [8]. These limitations do not make the claims false; they make them unverifiable from the public documents.

The Epic dress rehearsal is a training artifact for a specific organization's implementation, not a product specification [6]. It shows one possible workflow design, including reports for initial review, subsequent review, and recent discharge review [6]. It does not establish that this design is superior to alternatives or that it transfers to other Epic configurations. The Wisconsin nursing home interface document is state guidance, not a software requirement, but it identifies documentation elements that any cross-setting workflow should preserve [7]. Evaluators should treat vendor workflow descriptions as design hypotheses to be tested against their own policies, not as evidence of regulatory compliance.

A Concrete Evaluation Example

Consider a hospice agency with 120 patients, 40 percent of whom reside in skilled nursing facilities, and an IDG meeting structure that currently requires a nurse facilitator to compile paper notes for two days before each meeting. The evaluation team could construct a test scenario using a de-identified patient with a wound care need, a medication change, and a family communication issue. The scenario would require the nurse to flag the wound care item during a visit, the social worker to document the family issue, and the medical director to approve the medication change during the IDG meeting.

The team would then observe whether each candidate system carries the flagged items into the meeting view without manual re-entry, whether each discipline can edit its own section without overwriting others, and whether the final note shows the required progress toward outcomes [3]. For nursing home patients, the team would check whether the hospice portion of the plan can be exported or shared without claiming the nursing home portion [7]. This is a suggestion for a structured evaluation, not a report of testing performed. The results would depend on the agency's configuration and the vendor's implementation.