Demo · synthetic data, kept in this browser only · no email, SMS, payment or laboratory is connected · Guide and reset
BeYoung · Heart Check — demo

How the Heart Check works, end to end

This demo walks one customer from sign-up to the finished report, and shows what staff do in between. Everything is synthetic and stays in your browser; opening the link on another device starts a fresh demo.

Customer account

anna@demo.beyoung — one click, no password.

Staff account (physician + operations)

staff@demo.beyoung · demo-password · code 000000

Tip: keep the customer in one tab and staff in another. Current order: not started.

1. Sign up and order

Customer

Profile, mobile number (demo code 123456), eligibility, consent, red-flag questions, checkout, simulated payment.

2. Answer the questionnaire

Customer

Health questionnaire with autosave. Submitting it produces the laboratory form the customer takes to a collection site.

3. Operations: blood pressure and laboratory result

Staff

Under Result documents: record the blood pressure from the collection site, upload the result (any file), then verify the values against the document.

4. Physician: review and sign

Staff

Review queue → open the case → Start review. The right side shows the report as the customer will read it. Write a recommendation, tick the checklist, sign with password demo-password and code 000000.

5. Read the report

Customer

The order page now shows the report: overall result, each marker with its state, the physician's recommendation and the plan.

Which result should the laboratory send?

Choose before the result is uploaded in step 3.

Also in the staff consoles

The physician’s queue holds two more synthetic cases (one urgent, one needing follow-up) and the exception queue shows an urgent message that was not acknowledged. Operations has sample tasks, a quarantined laboratory message, laboratory configuration and settings.

Thresholds and wording are drafts awaiting medical approval. The demo skips what needs a back end: emails and SMS, payment, PDF files, the second person at verification, and the server-side wording check (a small imitation runs here).