Confidential Proposal
Statement of Work

Revive
Onboarding Portal

Recruiting Visibility for Families
Prepared for
Revive Private CareRevive Private CareMegan Fenceroy, NP-C, Clinical Director
Prepared by
Jae McKinneyFounder & Chief AI Strategist, Divigner Group
Date
May 2026Discovery complete
01 — Project Overview

Project Overview

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.

At a glance

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.

1–2
Weeks to Live
~24
Functional Reqs
$10K
Investment
0
PHI in Portal
02 — Parties & Contacts

Parties & Contacts

Revive Private Care

Clinical Director: Megan Fenceroy, NP-C

Clinical Lead: Andrew

Contact: info@reviveprivatecare.com

Divigner Group LLC

Lead: Jae McKinney

Title: Founder & Chief AI Strategist

Contact: jae@divigner.com

Discovery Status

Complete—build-ready

Go-Live Target

1–2 weeks from kickoff

03 — The Challenge

The Challenge

Current State

  • Parents wait with no visibility and no ETA
  • Inquiries produce conflicting answers from staff
  • Recruiting tracked across email, text, and a spreadsheet
  • Full HIPAA transaction layer was descoped by the client

What’s Needed

  • A single, trustworthy view parents can self-serve
  • One source of truth, identical to what staff see
  • A structured pipeline that drives the parent view
  • A PHI-safe design that avoids the exposure entirely
04 — How It Works

How the Portal Works

Five steps, built so the system never links an identifiable person to PHI.

1

Case & nurse profile created

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.

2

Credentials generated

System generates a non-email username and password. No PINs.

3

Delivered off-line

Revive hands credentials to the family by phone or manual text—never logged in the platform.

4

Family logs in

Parent reaches the portal and signs in with anonymous credentials.

5

Family sees status

Matched nurse profile, recruiting kanban with current stage, remaining steps, and ETAs.

Privacy by design

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.

05 — Requirements

Functional Requirements

A · Case & Recruiting (Internal)
FR-A1Create a case capturing child and parent details
FR-A2Move a case through defined recruiting stages
FR-A3Pair a nurse with a case
FR-A4Set and edit ETA values for a case
B · Nurse Profiles
FR-B0Create and manage nurse profiles from the internal dashboard
FR-B1Maintain nurse profile with photo, bio, credential, specialties, experience
FR-B2Distinguish parent-facing fields from internal-only fields
FR-B3Display only parent-facing fields in family portal
C · Family Portal Access
FR-C1Generate non-email username and password on case setup
FR-C2Not record channel or moment of credential delivery
FR-C3Authenticate families by username and password only
D · Family Portal Experience
FR-D1Display matched nurse’s parent-facing profile
FR-D2Display kanban of recruiting stages with current stage marked
FR-D3Display remaining steps and ETAs per display mode
FR-D4Allow families to select canned questions, routed to Revive
E · Revive Backend Controls
FR-E1ETA display-mode setting: per-stage ETAs or single care-start date
FR-E2Set and edit ETA values per case
FR-E3Login activity log keyed to anonymous username
FR-E4Surface which canned questions a family submitted
F · Compliance & Privacy
FR-F1Store no PHI, collect no personal info from families
FR-F2Never persist link between contactable identity and case PHI
FR-F3Login activity log records anonymous username only
G · Reporting & Analytics Dashboard
FR-G1Graphical dashboard with charts showing case volume and recruiting stage distribution
FR-G2Task management module embedded within the dashboard, surfacing staff task completion rates and team performance metrics
FR-G3Export case, nurse, and recruitment metrics to .xlsx or .csv
H · Task Management
FR-H1Create, assign, and complete internal staff tasks from the dashboard
FR-H2Per-staff and per-case task views with priority, due date, and status tracking
FR-H3Configurable notification preferences per staff member (email or in-app) for task assignments and approaching due dates
06 — Scope

Scope

In Scope
  • Internal case & recruiting pipeline
  • Nurse profile creation, management, and parent / internal field split
  • Anonymous credential generation
  • Family portal: nurse card, kanban, ETAs
  • Canned-question selection routed to Revive
  • ETA display-mode setting & login activity log
  • Reporting & analytics dashboard with charts and .xlsx / .csv export
  • Internal task management module with notification preferences
Out of Scope
  • Full HIPAA transaction layer (descoped by client)
  • ALORA EMR integration—no APIs exist
  • Two-way messaging / free-text chat
  • PIN codes (removed)
  • In-portal responses to family questions
  • Indeed integration (separate SOW)
07 — Assumptions & Responsibilities

Assumptions & Responsibilities

Revive Provides

  • Delivers credentials to families off-line
  • Sets ETAs and selects ETA display mode
  • Supplies nurse photos & bios, with consent
  • Confirms recruiting stage labels
  • Responds to family questions by email, SMS, or call

Divigner Provides

  • Builds and hosts the portal & backend
  • Anonymous credential system
  • Parent-facing kanban & nurse card
  • Canned-question selection & routing
  • Login activity logging
Important

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.

Interactive Prototype

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.

08 — Timeline

Timeline

A structured build designed to deliver a production-ready portal quickly while keeping Revive in control of content and workflow.

Access & Parent Board

Days 1–3

Anonymous credential system, login, and read-only parent recruiting kanban.

Profiles & ETA Controls

Days 4–7

Nurse profile parent/internal split, ETA values, display settings.

Questions & Logging

Days 8–9

Canned-question selection routed to Revive, login activity log.

Reporting & Task Management

Days 10–12

Analytics dashboard with charts for case, nurse, and recruitment metrics; .xlsx / .csv export; internal task management with per-staff views and notification preferences.

UAT

Days 13–14

User acceptance testing with Revive team, pilot run on one live case.

Launch

Go-Live

Production deployment and handoff. Families begin receiving credentials.

Discovery is complete. Target time to launch is 1–2 weeks from kickoff.

09 — Investment

Investment

Fixed Project Fee
$10,000
One-time
Complete design, build, and launch of the Revive Onboarding Portal with anonymous credential system, family-facing kanban, and backend controls.
Deposit Paid
Status
The deposit has been received and discovery is complete. The remaining balance is due on go-live per the agreed schedule.
  • Anonymous credential system
  • Internal case & recruiting pipeline
  • Parent-facing kanban & nurse profile cards
  • Canned-question selection & routing
  • Login activity logging & ETA controls
  • Reporting dashboard with charts & .xlsx / .csv export
  • Internal task management & notification preferences
  • Hosting & deployment on Vercel
10 — Partnership & Next Steps

Partnership & Next Steps

Divigner designs and delivers purpose-built web applications for healthcare, with a disciplined approach to privacy, usability, and speed to market.

Purpose-built for healthcare

HIPAA-conscious design from the ground up, with deliberate architectural choices that avoid PHI exposure.

End-to-end delivery

From requirements to production deployment, we manage the full lifecycle.

Privacy by design

The anonymous credential model keeps the platform clear of HIPAA exposure without sacrificing usability.

Fast to market

Discovery is complete. The portal goes live in 1–2 weeks from kickoff.

Ready to begin?

Discovery is complete and the deposit is received. We begin building immediately and target go-live within two weeks.

Jae McKinney
Founder & Chief AI Strategist, Divigner Group
jae@divigner.com · 732.328.2407 · Divigner.com