Building the clinical operating system before selling the library.
The full guides, evidence dossiers, reviewer records, hospital customizations, and clinician tools are private. The public site shows the architecture, governance, pilot model, and controlled product shape without releasing the deployable institutional library.
5
flagship modules
15
coordinated assets per topic
6
required release gates
Controlled preview—not a clinical handout.
No public page should be used as a substitute for orders, discharge instructions, medical advice, or emergency care. No module is represented as hospital-approved, clinically validated, or pilot-ready until its documented release gates are complete.
Adoption, comprehension, workflow, continuity, usefulness, safety signals, and explicit limits on outcome claims.
Recognizable guide anatomy
Patients should know where to look before they read every word.
Every module follows the same navigation and warning hierarchy while preserving topic-specific clinical review, equipment, medication, and local workflow requirements.
Example visual hierarchy
Routine action: What the patient should do now.
Call today: A concern that should be reviewed promptly.
Emergency: A clearly labeled action—not color alone.
1
The most important thing
One dominant action before background explanation.
2
What to do today
A short checklist for the immediate transition home.
3
When to get help
Emergency, call-today, and follow-up levels using words, icons, and color.
4
Your personal plan
Fields for actual orders, schedules, contacts, refills, suppliers, and follow-up.
5
How to do it
Numbered steps, accurate visuals, show-me checks, and topic-specific troubleshooting.
6
When the plan breaks
Practical instructions for failed refills, delayed supplies, missing home health, weekends, and conflicting instructions.
Initial flagship portfolio
Five modules selected to prove the system across different discharge risks.
The first module is in evidence development. The remaining modules are planned and will not bypass qualified review or patient testing.
Build a general anticoagulant guide plus medication-specific inserts, a personal plan, refill continuity, procedure planning, and emergency escalation.
A hospital licenses a workflow-ready module—not one PDF.
Each topic is designed to serve patients, caregivers, bedside staff, reviewers, informatics teams, and governance owners through coordinated assets.
1Full patient guide
2One-page quick-start sheet
3AVS-compatible summary
4Patient-specific plan
5Daily schedule or tracker
6Troubleshooting decision guide
7Red-flag escalation sheet
8Caregiver edition
9Teach-back checklist
10Show-me competency checklist
11Clinician reference sheet
12Evidence dossier
13Version and approval record
14Implementation workflow
15Patient and staff feedback tools
The operational moat
The guide continues where ordinary discharge documents often stop.
01
Clinical action
What the patient must do, how to do it, and which instructions are individualized.
02
Operational continuity
Who owns follow-up, refills, supplies, DME, home health, weekends, and failed handoffs.
03
Verified understanding
Teach-back and show-me workflows that test the explanation instead of asking only whether the patient understands.
04
Governed content
Named reviewers, evidence records, versioning, update triggers, correction routes, and recall capability.
05
Measurable implementation
Adoption, comprehension, workflow, continuity, usefulness, and safety signals with explicit claims boundaries.
Versioned technical platform
One governed source package, multiple controlled outputs.
The engine validates content structure, package metadata, versions, source-dossier references, release gates, distribution boundaries, and asset compatibility before producing any delivery bundle.
Every heading, action, warning, procedure, teach-back prompt, troubleshooting branch, and personalization field is validated before compilation.
Release bundle compiler
Package versions, source-dossier references, asset types, supported formats, output paths, checksums, and release states must reconcile.
Controlled proof registry
Public schemas and a nonclinical preview demonstrate the platform while reviewer provenance, clinical payloads, PHI-capable fields, and client material remain withheld.
Safety-critical content remains blocked until the evidence, qualified review, health-literacy, accessibility, patient-testing, and institutional-localization records are complete.
1
Evidence
A claim-level source map and unresolved-decision log are complete.
2
Clinical review
Each reviewer approves only the content within their professional competence.
3
Health literacy
Main action, wording, structure, numeracy, and actionability pass internal thresholds.
4
Accessibility
Web, print, PDF, visual, keyboard, contrast, and non-color-dependent communication are reviewed.
5
Patient testing
Representative patients or caregivers can locate, explain, and use the critical information.
6
Institutional localization
The hospital approves local contacts, policy language, workflow, formulary, and escalation routes.
Private pilot scoping tool
Build a non-identifying pilot starting brief.
Choose five fixed options. The tool assembles a proposed guide package, accountable team, implementation sequence, measures, prerequisites, and claims boundaries.
No patient information and no free text. Selections remain in this browser tab. They are not saved, added to the URL, or sent as answer-level analytics.
Clear boundaries before procurement
The product description stays narrower than the ambition.
CAF is building toward an institutional education product. It is not currently representing a deployed EHR platform, a certified security program, a clinical service, or proven outcomes.
Development-stage product: no guide is represented as hospital-approved, clinically validated, or pilot-ready until its documented release gates are complete.
CAF does not diagnose, prescribe, determine coverage, replace discharge orders, or provide emergency or individual clinical support.
The initial product is designed not to receive PHI. Patient-specific personalization should occur inside the healthcare organization's approved environment.
Pilot engagement does not prove fewer readmissions, adverse events, calls, costs, or other clinical outcomes without an agreed evaluation method and adequate evidence.
Review the procurement boundary
See current capabilities, scoped-review items, and services not represented.