How Judi handles patient information.
AlayaCare stays your system of record and Judi works alongside it. This page says what Judi keeps, what it never keeps, how it is protected, and what is not finished yet.
At a glance
- AlayaCare stays the record
- Photos stay off the camera roll
- No PHI in a push
- Deactivation cuts access
The detail is below, including what is not finished yet.
On this page11 sections
AlayaCare stays the system of record
Clinical and scheduling data live in AlayaCare. To draw its screens, Judi keeps a synced copy of the schedule details they need (the visit time, the nurse, the patient's name and ZIP) and overwrites it from AlayaCare on every sync. Nothing from the chart is copied. When a nurse declines a visit or says they are running late, the request goes to the Scheduling group. Changes the office approves are made in AlayaCare: keyed by Scheduling, or written back by Judi where the agency has turned that on. Judi never touches a chart, a note or an order.
What Judi stores, and what it never does
Judi keeps only what the clinical system does not. Everything else stays where it already lives.
Judi holds
- User accounts and roles
- Nurse profiles: license state, home ZIP for distance sorting, weekly availability
- A synced copy of the schedule details its screens show: visit time, nurse, patient name and ZIP
- Messages and IV-site photos, encrypted
- Referral records and the referral CRM
- Training completions and the audit log
Judi never holds
- The clinical chart, notes, orders or care plans
- Billing or claims
- Patient addresses sent to any third-party API
- Photos on the camera roll or in iCloud
- Patient information in a push notification
- Plaintext patient information in logs, crash reports or analytics
Encryption
Everything is encrypted in transit and at rest. IV-site photos are taken inside the app, encrypted before they are written, attached to the visit, and never offered to the camera roll or to iCloud backup. There is no library picker. Nothing is kept in plaintext on the phone.
An audit log on every read
Every time a photo or a message is opened, the server writes who, what and when. The log is written server-side, so a client cannot skip it. Role-based access is also enforced server-side; the app never decides on its own what a role may see.
No patient information in a push
A notification carries a title and an ID. The app fetches the content after the person signs in, over the same authenticated connection as everything else. A locked phone on a kitchen counter shows nothing a visitor could read.
Turning someone off takes effect now
When an admin deactivates a nurse, messaging, photos and education on that phone are cut immediately. Deactivation propagates in real time rather than at the next sign-in.
The message archive is exportable by one role
Exactly one role at the agency can export the message archive. Nurses and schedulers cannot. That is a deliberate narrowing, not a missing feature.
No patient address goes to a mapping service
Distance sorting and drive times are worked out between ZIP centres, so no patient address is sent to a mapping service. Directions open Google Maps on the nurse's own phone once the visit is theirs.
AI that stays inside the same agreement
Judi assist, the optional AI in Judi, runs in Judi's own AWS account under the same Business Associate Agreement as everything else. The AI model keeps nothing it reads and is never trained on it. Each tool sends only what it needs: the referral reader and the paperwork matcher send the email or attachment they read, Ask AI Judi sends a report's columns and choices but never a row, and the Monday brief sends counts, never a name.
Every AI tool starts off and is turned on by an admin, one at a time. Each one suggests and a person decides. AI Judi turns away questions about doses, rates, reactions or a patient. How each tool works.
Hosting, and what is not finished yet
Judi runs on AWS under a signed Business Associate Agreement, using only services that agreement covers, with the agency as the covered entity. The database runs in two data centres at once, is backed up to a second region, and is watched for intrusion.
Where it stands today
Judi is in user testing with its first agency, against that agency's AlayaCare test environment and test patients. The production environment is built from the same code under the same agreement before any real patient information goes in. If you are evaluating Judi for your agency, ask us where that stands.
Questions
Compliance questions go to privacy@meetjudi.com. For a walkthrough with your compliance officer in the room, book a demo.
Compliance questions
privacy@meetjudi.com