Revive Private Care places skilled nurses with medically fragile children. Parents currently wait with no visibility into the recruiting process and no reliable ETA for when care will begin. The Onboarding Portal gives them a single source of truth about their child’s caregiver—and where recruiting stands—without the system ever storing protected health information.
Give parents a single source of truth about their child’s caregiver and where they are in the process—without the system ever holding identifiable PHI.
Clinical Director: Megan Fenceroy, NP-C
Clinical Lead: Andrew
Contact: info@reviveprivatecare.com
Lead: Jae McKinney
Title: Founder & Chief AI Strategist
Contact: jae@divigner.com
Complete—build-ready
1–2 weeks from kickoff
Five steps, built so the system never links an identifiable person to PHI.
Revive creates the case, builds a nurse profile with photo, bio, credentials, and specialties, then pairs the nurse with the case through the recruiting pipeline.
System generates a non-email username and password. No PINs.
Revive hands credentials to the family by phone or manual text—never logged in the platform.
Parent reaches the portal and signs in with anonymous credentials.
Matched nurse profile, recruiting kanban with current stage, remaining steps, and ETAs.
Because credentials are delivered off-line and never logged, the platform holds no connection between a contactable identity and case PHI. That separation is what keeps the portal clear of HIPAA exposure.
| A · Case & Recruiting (Internal) | |
|---|---|
| FR-A1 | Create a case capturing child and parent details |
| FR-A2 | Move a case through defined recruiting stages |
| FR-A3 | Pair a nurse with a case |
| FR-A4 | Set and edit ETA values for a case |
| B · Nurse Profiles | |
|---|---|
| FR-B0 | Create and manage nurse profiles from the internal dashboard |
| FR-B1 | Maintain nurse profile with photo, bio, credential, specialties, experience |
| FR-B2 | Distinguish parent-facing fields from internal-only fields |
| FR-B3 | Display only parent-facing fields in family portal |
| C · Family Portal Access | |
|---|---|
| FR-C1 | Generate non-email username and password on case setup |
| FR-C2 | Not record channel or moment of credential delivery |
| FR-C3 | Authenticate families by username and password only |
| D · Family Portal Experience | |
|---|---|
| FR-D1 | Display matched nurse’s parent-facing profile |
| FR-D2 | Display kanban of recruiting stages with current stage marked |
| FR-D3 | Display remaining steps and ETAs per display mode |
| FR-D4 | Allow families to select canned questions, routed to Revive |
| E · Revive Backend Controls | |
|---|---|
| FR-E1 | ETA display-mode setting: per-stage ETAs or single care-start date |
| FR-E2 | Set and edit ETA values per case |
| FR-E3 | Login activity log keyed to anonymous username |
| FR-E4 | Surface which canned questions a family submitted |
| F · Compliance & Privacy | |
|---|---|
| FR-F1 | Store no PHI, collect no personal info from families |
| FR-F2 | Never persist link between contactable identity and case PHI |
| FR-F3 | Login activity log records anonymous username only |
| G · Reporting & Analytics Dashboard | |
|---|---|
| FR-G1 | Graphical dashboard with charts showing case volume and recruiting stage distribution |
| FR-G2 | Task management module embedded within the dashboard, surfacing staff task completion rates and team performance metrics |
| FR-G3 | Export case, nurse, and recruitment metrics to .xlsx or .csv |
| H · Task Management | |
|---|---|
| FR-H1 | Create, assign, and complete internal staff tasks from the dashboard |
| FR-H2 | Per-staff and per-case task views with priority, due date, and status tracking |
| FR-H3 | Configurable notification preferences per staff member (email or in-app) for task assignments and approaching due dates |
The HIPAA-avoidance design holds only if Revive delivers credentials off-line and the platform never stores the identity-to-PHI link. If credentials are ever delivered or logged inside the system, the separation breaks.
A high-fidelity, clickable prototype of the Onboarding Portal will be presented during the User Acceptance Testing (UAT) phase for hands-on review and feedback before final delivery.
A structured build designed to deliver a production-ready portal quickly while keeping Revive in control of content and workflow.
Anonymous credential system, login, and read-only parent recruiting kanban.
Nurse profile parent/internal split, ETA values, display settings.
Canned-question selection routed to Revive, login activity log.
Analytics dashboard with charts for case, nurse, and recruitment metrics; .xlsx / .csv export; internal task management with per-staff views and notification preferences.
User acceptance testing with Revive team, pilot run on one live case.
Production deployment and handoff. Families begin receiving credentials.
Discovery is complete. Target time to launch is 1–2 weeks from kickoff.
Divigner designs and delivers purpose-built web applications for healthcare, with a disciplined approach to privacy, usability, and speed to market.
HIPAA-conscious design from the ground up, with deliberate architectural choices that avoid PHI exposure.
From requirements to production deployment, we manage the full lifecycle.
The anonymous credential model keeps the platform clear of HIPAA exposure without sacrificing usability.
Discovery is complete. The portal goes live in 1–2 weeks from kickoff.
Discovery is complete and the deposit is received. We begin building immediately and target go-live within two weeks.