rag-patient-folder-memory

Maintain per-patient longitudinal context with local-first RAG retrieval.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JustinChaney2023/orate --skill rag-patient-folder-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rag-patient-folder-memory
Source: https://github.com/JustinChaney2023/orate/tree/main/roles/rag-patient-memory
Command: npx skills add https://github.com/JustinChaney2023/orate --skill rag-patient-folder-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables per-patient folder memory with a local-first RAG approach to maintain longitudinal context (prior visits, summaries, trends) while preventing hallucinations and ensuring that the standardized form is filled only from current-visit evidence.

Core Features & Use Cases

  • Local-first patient memory with strict per-patient isolation to prevent cross-patient leakage.
  • Contextual retrieval for visit history, trends, and provenance, supporting HIPAA-grade controls.
  • Delta detection for changes across visits and automated change summaries to assist review.

Quick Start

Use the rag-patient-folder-memory skill to scaffold a patient folder with today's transcript and OCR evidence, then compare against prior approvals to produce a folder_context_pack and delta_report for review.

Frequently Asked Questions about rag-patient-folder-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain longitudinal patient context for RAG without leaking PHI across patients?

Patient-scoped memory uses local-first RAG to maintain longitudinal context with strict per-patient isolation, preventing cross-patient data leakage. This ensures HIPAA-grade controls while retaining historical visit data securely.

How do I fill standardized medical forms using only current-visit evidence without losing prior context?

Standardized forms are filled only from current-visit evidence while local-first memory retains prior visit summaries. Safe memory updates prevent historical context from overriding today's source spans, ensuring accurate form completion.

Can I track changes in patient conditions across visits using local-first RAG?

Delta detection compares current patient folder evidence against prior approvals to identify changes across visits. Automated change summaries are generated to assist clinical review of longitudinal trends and new findings.

Does local-first patient memory support HIPAA compliance requirements like audit trails and encryption?

Local-first patient memory satisfies HIPAA-grade controls including encryption at rest, audit trails, and evidence provenance to today's source spans. These features ensure regulatory compliance for PHI handling.

What's the best way to scaffold a patient folder for contextual retrieval and review?

Scaffold a patient folder with today's transcript and OCR evidence, then compare against prior approvals to produce a folder_context_pack and delta_report. This workflow enables contextual retrieval and comprehensive clinical review.

Why does patient memory not override current-visit evidence during form filling?

Safe memory updates are designed to not override current-visit evidence during form filling. This prevents hallucinations by ensuring the standardized form is populated only from today's verified source spans.