CL-033Clinical Documentation
Plan of Care Configuration
Clinical Experience & Provider Productivity
Recommended pathConfigure / Activate
- Capability status
- To be confirmed with PRN
- Transformation phase
- To be confirmed with PRN
- Effort
- To be confirmed with PRN
Current State / What We Learned
Observed today, as captured in the corrected assessment.
PRN has uncoupled POC from progress notes, but workflow still creates unnecessary documentation in some cases
Desired Future State
The target way of working PRN and Raintree are aiming for.
Optimize POC and progress-note relationship
Requirement / Gap
Configure POC timing and requirements appropriately by payer/workflow
Raintree Recommended Path
- Conduct POC configuration review alongside progress-note review
- Only POC requirements in the system are ICD-10 codes, Planned Services, Frequency/Duration, at least one active goal, and Clinical Impression. These validations exist as part of the TVIST note and do not require the clinician to document them separately. The POC is only required to be updated if the patient’s plan runs out of planned visits or if the date range expires.
Dependencies / Considerations
Regional and payer requirements
Outstanding Questions / Decisions
Can POC and progress-note requirements vary by payer or region?
Evidence
Supporting screenshots from the corrected Detailed Transformation Assessment.
Source
Detailed Transformation Assessment (Corrected)Related opportunities
Related by workstream and subject matter. These are not stated dependencies unless the assessment says so.