ITH-000102
Demo Patient 03
- Telephone
- 555-0103
- demo.patient03@example.com
- Source
- Patient or family
- Lead captured by Sales
- Oct 24, 4:49 PM
Tech Support
TS Demo B
Current step
3. Patient authentication sent
Tech Support for 11 h
Patients answer texts, not calls.
Who gets what
Even when a caregiver or home health agency is helping, the authentication link always goes to the patient.
Patient: authentication link
Sent only to the patient’s own phone by text: 555-0103
Not sent yet. It goes out when step 3 (Patient authentication sent) is done.
The patient also gets the enrollment link and token. They are never sent to anyone else.
Caregiver or agency: status notifications only
No caregiver or agency on this case.
If one is added, they get status notifications only (for example “authentication complete”, “device shipped”), never the link.
Steps
-
1. itracHEALTH Tech Support resource assignment
DoneSales management assigns a Tech Support person to the new lead. The unique patient ID is assigned at this moment.
Assigned to TS Demo B.
Entry: Oct 25, 7:49 AM · Demo Sales Manager
-
2. Patient contact info verified
DoneTech Support confirms the name, email and telephone captured by Sales.
Entry: Oct 25, 10:49 PM · TS Demo B
-
3. Patient authentication sent
WaitingTech Support sends the identity check (Persona) link to the patient. The link always goes to the patient's own phone, even when a caregiver or home health agency is helping; they get status notifications only.
Waiting since Oct 25, 10:49 PM (11 h ago)
-
4. Patient authentication complete
Not startedThe patient completes the Persona identity check. Persona returns Passed, Failed or Needs review with a reference number; the photos stay with Persona. Failed raises an alert. Fallback: manual review by Tech Support.
-
5. Consent sent
Not startedTech Support sends the consent to the patient.
-
6. Consent signed
Not startedThe patient signs the consent online.
-
7. Enrollment link and token sent
Not startedThe back end sends the patient a personal enrollment link and token.
-
8. Enrollment inputs 1, 2, 3 and 5 received
Not startedThe patient completes enrollment inputs 1, 2, 3 and 5 in the enrollment portal. Tech Support can correct or complete them for the patient on the Edit inputs page; every change is logged.
-
9. Verify patient's inputs / complete input 4
Not startedTech Support checks the patient's inputs and completes input 4.
-
10. QA (enrollment info verification)
Not startedTech Support verifies all enrollment information before manufacturing.
-
11. eNURSE configuration record sent to manufacturing
Not startedTech Support sends the eNURSE configuration record to manufacturing.
-
12. Shipment notification sent
Not startedTech Support lets the patient know the eNURSE has shipped.
-
13. Schedule installation support call
Not startedTech Support schedules the installation support call with the patient.
-
14. Installation complete
Not startedThe patient finishes installing the eNURSE, with Tech Support on the call.
-
15. Generate eSSIST token (if required)
Not startedThe back end generates the eSSIST token for the caregiver. Not needed if there is no caregiver.
-
16. Generate itracINSITE token (if required)
Not startedThe back end generates the itracINSITE token for the doctor or agency. Not needed is common at first.
-
17. eSSIST installed / active
Not startedThe caregiver installs eSSIST and it becomes active.
-
18. itracINSITE installed / active
Not startedThe doctor (PCP) or home health agency (HHA) installs itracINSITE and it becomes active.
-
19. Final QC
Not startedTech Support does a final quality check of the whole case.
-
20. Case closed
Not startedEnrollment is finished. The case leaves the open list.
Notes
No notes yet.