Postpartum support. Connected blood pressure. One focused start.
Add HEART RESERVE Postpartum Advocate to a platform such as Journey, using an already-supported Bluetooth upper-arm cuff and the hospital’s existing care team.
Proposed Phase One setup portion (1A) · No Bluetooth device, live monitoring or clinical response is connected to this demonstration.
THE RECOMMENDED FIRST PRODUCT
HEART RESERVE Postpartum Advocate
The postpartum program within HEART RESERVE Concierge. Start with adults returning home after hypertension or preeclampsia during pregnancy, after vaginal or cesarean birth, at one hospital or clinical service. The first purchase prepares a working, reviewed add-on for a controlled clinical start.
Reuse the platform
Existing accounts, app access, approved AI companion, notifications, messaging, staff dashboard and a demonstrated device connector. Confirm each function in the current release before including it in the quote.
Add the HEART RESERVE program
Pregnancy-to-heart context, a short recovery plan, approved warning-sign education, medicine and appointment support, practical-help requests and visible follow-through.
A useful welcome: the reviewed discharge plan, responsible care service, contact route, coverage hours and next agreed assessment.
Connected BP: cuff setup and automatic transfer through the platform’s supported route, with original measurement time, source and delivery status.
A short check-in: symptoms, medicine access and what is making the plan difficult. Symptoms remain relevant whatever the reading shows.
An advocate that explains: plain-language, clinician-approved teaching and questions for the care team. Treatment changes remain with the treating clinicians.
Follow-through: each need has an owner, due time and recorded outcome; the patient can say it remains unresolved. Use the existing clinical work queue if it can support this.
A continuing-care handoff: the next service and appointment, with the patient’s pregnancy history and unresolved needs preserved.
Broader midlife, GLP-1, surgical recovery, document extraction and ECG interpretation remain later packages. Phase 1 uses a focused content set and one device model; it does not require building the whole HEART RESERVE platform.
BLUETOOTH IS IN THE FIRST SCOPE
Take the reading. Know where it went.
The cuff measures blood pressure; Bluetooth transfers the result to the phone. The supported app or vendor connection then sends it securely to the clinical service. Pairing alone does not prove that the hospital received or reviewed a reading.
1 · Measured on the cuff
Keep systolic pressure, diastolic pressure, units, measurement time, device identity and the correct patient.
2 · Received by the phone
Show the last successful transfer. Distinguish a queued reading from one that reached the service.
3 · Received by the service
Record receipt separately from measurement time. Handle duplicate or delayed uploads without losing the original reading.
4 · Reviewed by the team
Record human review and the next instruction separately. “Uploaded” must never become “reviewed” automatically.
Choose the exact cuff with the partner
Require an upper-arm model with appropriate validation evidence for pregnancy/preeclampsia, a cuff size that fits, applicable U.S. marketing authorization and a working connection to the selected platform on supported phones. A familiar brand name or Bluetooth logo does not establish these requirements.
STRIDE BP lists Bluetooth upper-arm devices with pregnancy/preeclampsia validation, including the exact European model Omron Evolv HEM-7600T-E. This is evidence that the device category exists, not selection of that model for this U.S. program. Confirm the exact U.S. model, validation equivalence, availability and platform compatibility before ordering.
If the connection fails
Keep the reading on the cuff and show that delivery is unconfirmed. Offer the hospital’s agreed telephone or assisted-entry route, label manual entries, and preserve their source. Patients follow their clinical instructions for concerning readings or symptoms without waiting for a successful upload. If a phone cannot support Bluetooth, price a supported cellular or staff-assisted alternative separately.
Journey publicly advertises tracking, alerts, messaging, reports and white-label customization. Its reviewed public pages do not verify the exact Bluetooth cuff model or automatic-transfer route for this project. That demonstration is the first technical acceptance requirement.
SMALL SCOPE · CLEAR ACCEPTANCE
Configure. Rehearse. Then approve a clinical start.
This 8–12-week configuration estimate assumes a ready connector and prompt partner decisions. Hospital procurement, contracting and approvals may extend the calendar. It is a task within the wider 24-month proposal, not a replacement for that proposal’s timetable.
Proposed timing
Work and evidence
Weeks 1–2
Demonstrate the exact cuff-to-dashboard connection. Confirm existing features, content rights, clinical responsibilities and a fixed scope with itemized prices. If the connector requires a new build, reprice before proceeding.
Weeks 3–6
Configure branding, reviewed postpartum content, the care plan, BP transfer and follow-through using the existing platform. Keep clinical deadlines and contact instructions set by the hospital.
Weeks 7–10
Rehearse setup and failed-transfer scenarios. Test essential tasks with 10–15 representative patients or caregivers and staff using fictional records. Record usability problems and correct them.
By weeks 10–12, if ready
Obtain documented technical and clinical acceptance, a funded staffing plan and the next-stage quote. Timing is provisional and assumes an existing supported connector.
What must pass before clinical activation
Correct patient, cuff fit and measurement technique; first reading received end to end.
Bluetooth off, no internet, missing upload, duplicate transfer, wrong device assignment and delayed data tested on each supported phone platform.
Every critical scripted scenario passes after correction; no unresolved critical issue. Passing finite tests does not prove universal reliability.
Proposed usability target: at least 85% complete each essential task without help; report numerator, denominator, errors and access needs. Critical help tasks must be corrected even when the overall target is met.
Approved content and clinical workflow; consent, permissions, privacy arrangements, staff coverage and backup contacts accepted by the responsible partners.
The next stage is a small clinical start: the first 5–10 service recipients within the proposed 50-person program arm, followed for their agreed 90-day episodes. Expand only after operational review. These are part of the larger funded pilot, not extra participants or a second overlapping budget. Clinical monitoring, care delivery and research enrollment do not start under the setup-only allowance. The separate service cost model makes the next-stage resources visible.
COST REVIEW · OCTOBER 22, 2026
Plan $35,000–$60,000 for setup and testing.
The first purchase adds Postpartum Advocate and one supported Bluetooth cuff connection to an existing platform. This is the setup portion of Phase One; it does not fund the whole patient service or 24-month evaluation.
Working setup target: about $50,000, subject to quotes. The earlier $40,000 allowance is replaced by the assumptions below. There is no verified Emagine implementation price yet.
These are bottom-up planning scenarios, not vendor prices, statistical confidence limits or guaranteed maximums. Every hourly rate, workload and subscription allowance below is an estimating assumption. Costs could fall outside the range.
1A · Configure and demonstrate readiness
Initial setup and testing · USD · paired lower and higher assumptions
Work
Lower
Higher
Platform configuration and testing
$12,000
$25,000
Lisa’s program and content work
$6,000
$8,000
Independent clinical review
$3,000
$4,800
Privacy, contracting and implementation review
$2,400
$3,600
Platform, AI and connector test access
$1,500
$3,000
Five test cuff packages
$750
$1,250
Usability participant expenses
$600
$1,200
Subtotal
$26,250
$46,850
20% planning contingency
$5,250
$9,370
Modeled total
$31,500
$56,220
The arithmetic gives $31,500–$56,220; $35,000–$60,000 is a rounded planning envelope. Keep the reserve visible. Grant submissions must use the funder’s permitted, justified cost lines rather than assume this reserve is eligible.
See the hours, rates and quantities behind setup
Platform configuration and testing: 120 hours × $100 to 200 hours × $125. Includes technical scoping, existing cuff connector configuration, staff-workflow configuration, usability sessions and corrections. No new connector build.
Lisa’s program and content work: 60–80 hours × $100. Focused curriculum, onboarding, advocacy workflow, staff materials and project coordination.
Independent clinical review: 20–32 hours × $150. Review the focused content, escalation instructions and clinical rehearsal; live patient care is separate.
Privacy, contracting and implementation review: 16–24 hours × $150 using existing platform and hospital arrangements. A new security assessment, complex negotiation or separate insurance policy must be quoted.
Platform, AI and connector test access: Three setup months × $500–$1,000 as an unverified allowance. Obtain all license, API, AI, device-connector and support charges; annual minimums may exceed this.
Five test cuff packages: Five × $150–$250 including a cuff, delivery and setup supplies. Model, cuff size and price remain unconfirmed. Retain these for testing and training.
Usability participant expenses: 12 representative testers × $50–$100. Fictional records; staff facilitation is already in the work lines above.
Your compensation is included: Lisa’s proposed setup work is $6,000–$8,000 for 60–80 hours at an assumed $100/hour. Pay should follow agreed work and deliverables. A percentage target is not the cost basis; any future licensing royalty is a separate negotiated term.
What must already exist for this range to work
One functioning platform with patient access, AI/content controls, messaging, a staff dashboard and the required follow-through fields.
A demonstrated, supported cuff-to-dashboard route on the selected phones. Bluetooth capability alone does not establish integration.
One hospital partner, one focused postpartum program and a limited approved content set. Additional languages or extensive accessibility remediation must be scoped if the current platform does not already support them.
Existing hospital privacy, security and clinical infrastructure that can accept the configuration without a new enterprise build.
New device software, a new native app, custom EHR integration, new 24/7 staffing, regulatory work beyond the agreed product role, insurance, extensive translation and hospital-required assessments are not priced here. Obtain separate offers if required. Confirm taxes, travel, overhead and any annual licensing minimum before committing; a contingency does not replace a known missing cost.
1B · Budget separately to serve patients
For the proposed 50 service recipients, each followed for 90 days, the model adds $40,800–$93,600 in service costs. Begin with the first 5–10 of those 50 after acceptance. Existing hospital response coverage must be available and explicitly assigned; this allowance does not establish a new round-the-clock service.
Open the 50-patient operating-cost model
Live service, additional to setup · USD · paired lower and higher assumptions
Work
Lower
Higher
50 patient cuff packages
$7,500
$12,500
Clinical monitoring and response
$15,000
$40,000
Clinical supervision and training
$3,000
$6,000
Enrollment and technical support
$2,500
$7,500
Live platform, AI and connector access
$2,000
$6,000
Basic service evaluation
$4,000
$6,000
Subtotal
$34,000
$78,000
20% planning contingency
$6,800
$15,600
Modeled total
$40,800
$93,600
50 patient cuff packages: 50 × $150–$250. These are separate from the five retained test units; credit any approved inventory transfer once.
Clinical monitoring and response: 50 people × 4–8 total staff hours per 90-day episode × $75–$100 loaded hourly cost. A workload assumption to validate, never a limit on needed care.
Clinical supervision and training: 20–40 hours × $150. Separate from the hands-on monitoring time above.
Enrollment and technical support: 50 people × 1–2 hours × $50–$75. Nonclinical setup and access support; avoid billing the same staff time in the clinical line.
Live platform, AI and connector access: Four live months × $500–$1,500, after the three setup months. Assumes enrollment within one month and completion of all 90-day episodes within four months. Contract pricing is unknown.
Basic service evaluation: 40–60 hours × $100 for operational measures, feedback and a descriptive report. No comparator recruitment, claims linkage or formal research analysis.
Staff time must be funded or recorded as an in-kind hospital contribution; it is not free because an employee is already on payroll. These are total program resource costs. A signed responsibility and funding split is needed to establish HEART RESERVE’s cash requirement and the hospital’s contribution. Clinical visits, treatment and downstream hospital care remain outside this program budget and must be counted in any total-cost evaluation.
Setup + the 50-patient service: roughly $75,000–$150,000.
Combined scenario arithmetic is $72,300–$149,820, including the 20% reserve in each stage once. The headline ranges are rounded independently. This covers setup and a limited service launch, not the complete 24-month comparison study.
About $1,450–$3,000 per participant in this first 50-person cohort includes startup work. This is neither a recurring selling price nor evidence of savings. Reuse may spread setup costs over more patients, while clinical workload and contract fees still need measurement.
2 · Keep the larger funding routes separate
The 24-month planning document uses a $250,000 service-pilot alternative and a separate $400,000 research route, provisionally $200,000 per year subject to funder confirmation. Those are broader planning requests, not the price of the first add-on. Formal comparison-group work, research administration and a longer operating period need their own scoped budget. These alternatives overlap; do not add them together.
Map the setup and service costs into a selected larger budget once. The 50 service recipients belong to its proposed 50-person program arm; any 50-person current-care comparison and research data work are additional scope, not included in the smaller service model. The grant plan’s overall “Phase One” includes more than the initial configuration described as 1A here.
The older $150,000 proposal packets remain superseded. A similar number at the top of today’s service range does not validate those older assumptions. The 24-month Word proposal has a separate scope; this cost review updates the app’s initial-purchase estimate.
Make the hospital and insurer case with actual costs
Track staff minutes, completed follow-up, unresolved concerns, device delivery, urgent care use and patient experience. Compare the service cost with the purchaser’s existing program. Use the insurer’s actual allowed amounts for payer savings and the hospital’s actual incremental costs and contract incentives for its business case. Do not count a hospital charge as both a hospital saving and an insurer saving, or assume reimbursement will pay for the app.
No avoided readmissions, savings, reimbursement or grant award is assumed in these totals. The sample is for feasibility and service learning; it cannot establish a reliable mortality or savings effect.
“Please quote a HEART RESERVE Postpartum Advocate add-on using your existing platform, one supported Bluetooth upper-arm blood-pressure cuff, approved postpartum education, practical-help requests and your existing care-team workflow. Please demonstrate one reading reaching the correct patient’s staff record, show the failed-transfer process, and separate setup, ongoing platform charges and clinical-service costs.”
Ask for the exact cuff and connector, supported phones, data path and delivery receipts, what exists today, what needs configuration, and what requires development. Confirm branding and content rights, recurring license terms, support and the clinical organization responsible for review. Require an itemized fixed-price setup offer, the minimum contract term, charges per active patient or month, AI and connector usage fees, onboarding, support, taxes, exclusions and change-order terms. Keep paid scoping within the configuration line or credit it once if the project proceeds.
Suggested purchasing sequence: agree a small, priced scope-and-connector demonstration first, then approve configuration against a written offer and acceptance criteria. Release the patient-service budget only when staff ownership, coverage and costs are agreed. The $50,000 setup target is an internal planning assumption, not an authorization to spend or a vendor price.
The HEART RESERVE screens illustrate the desired experience. No device has been ordered, vendor configuration completed, agreement executed or patient enrolled through this update.
What is verified, and what still needs a quote
Reviewed October 22, 2026. Emagine’s reviewed pages describe white-label customization and remote monitoring but do not publish a project price or confirm the exact cuff connection. Vendor descriptions do not establish this project’s integration or clinical results. The budget rates and quantities are our planning assumptions, not facts supplied by those sources.