Regional coding and OASIS review firms
Manage source-cited packet review across several agency clients.
Healthcare evidence-operations product
Find missing RCD evidence before the packet is submitted.
RCD PacketOps is a file-first evidence and reviewer workbench for regional home-health coding, OASIS, QA, documentation-review, and revenue-cycle partners managing Review Choice Demonstration packets.
Who it is for
RCD PacketOps is built for Medicare home health agencies and their review partners in Texas, Illinois, Ohio, North Carolina, Florida, and Oklahoma, where the Review Choice Demonstration requires pre-claim or post-payment documentation review through Palmetto GBA. It surfaces missing or inconsistent evidence before a packet is submitted, protecting the affirmation rate that determines how much review an agency faces.
The product
A file-first reviewer workbench that sits beside your EHR.
RCD PacketOps is designed for regional firms that already employ credentialed reviewers and manage packet preparation for multiple home-health agencies. The opportunity depends on measurable reviewer-time savings and partner capacity.
Proposed capabilities
- Requirement-to-evidence coverage matrix
- Source-cited missing and conflicting evidence
- Versioned rules with explicit human-decision boundaries
- Reviewer comments, packet versions, and resubmission history
- UTN and outcome tracking without replacing the submission portal
Interactive demonstration
From fragmented records to a source-cited review queue.
The scenario runs on a sample packet and shows the workflow end to end: extraction, rule checks, and a reviewer queue with every finding cited to its source.
Submission tasks
Nigat AI engineEvidence extraction and checks
Ready
Reason codes checkedRun the review
Idle. Run the review to trace each reason code to its source document.
Documents in this task
Human boundary: configured checks can identify evidence presence, identity, dates, signatures, and linkage. Credentialed professionals retain clinical, coding, homebound-status, medical-necessity, and final submission decisions.
The submission tasks, document lists and reason codes are taken from the Palmetto GBA pre-claim review form and checklists and the CMS reason code list. The episode itself, and which items pass or fail, are generated fresh on every run.
Home-health QA and documentation-review partners
Resolve evidence gaps while retaining professional judgment.
Multi-agency revenue-cycle operators in RCD states
Measure packet volume, reviewer effort, resubmissions, and outcomes.
Human and security boundaries
- Not an EHR or OASIS authoring system
- Not a coding engine or medical-necessity decision maker
- Not a claim of denial reduction or clinical accuracy
- Credentialed reviewers retain clinical and coding decisions
Start with the operating problem
Show us where the work slows down.
You do not need a polished technical brief. Describe the decision, handoff, report, document workflow, or AI initiative that is harder than it should be.