Sessions ensure that user orders and exams can be tracked in a transactional fashion, and allow for patients to return to their test if they don’t finish it in one sitting.
A session does not expire, and a patient should utilize the same session until it reaches the terminal event of Session Completed.
Each session maintains the context of a specific order, including:
- User's age, region, email, name
- What products were ordered (Rx types or acuity service)
- How much the user was charged, in cents
- What prior prescriptions were provided, if any
- Where in the user is in the experience
Do not use a user's personal information (such as the values in the
userobject) in theuser_keyorsession_keyfields when generating a session. Not only are they potentially non-unique, they are not PHI compliant.