Message events

introduction to keep your app informed about the user's progress within the plug in, we transmit data via message events at various stages this document describes the different types of events, when they are sent, and their data format the events are in json format and contain information about the health check's progress and the final results prerequisites make sure you've gone through the following documentation request plug in url docid\ odjxifncpcgwmttwd6j1c embed plug in docid\ vywpzgyzobqqswusjqy 4 to learn how to listen for these data messages in web apps, refer to the listening to message events docid\ w5rbnpzndxl8rzkeo pji page overview we currently distinguish the following events startnewmeasurement recordingstarted recordingstopped results buckets bucketsummaries userfinished dismiss error (informative) summary of event occurrences when the user clicks the 'perform measurement' button on the welcome screen, a start new measurement event is sent upon reaching the recording screen, users encounter the camera stream along with a start button pressing the start button initiates the quality checking process if the conditions are favourable and the check passes, the actual recording starts and a recording started event is sent the timer begins counting down, and upon reaching zero, the measurement concludes, prompting a recording stopped event the subsequent events depend on the outcome of the measurement if the measurement is successful, three events containing the health check results are sent results , buckets and bucketsummaries however, there might be instances where the quality deteriorates too much during the health check, rendering an accurate assessment unfeasible for instance, this could occur if the lighting abruptly dims in such cases, an ' error ' event is sent and users are presented with two choices they can restart the health check by selecting the ‘ try again ’ option, or they can opt to conclude the health check without completing it successfully by clicking the ‘ continue ’ button choosing the 'try again' option brings them back to the start of the health check process if they select the 'continue' option, no biomarker results will be generated, and a userfinished event will be sent the dismiss event is sent whenever the web plugin should be closed the event types are further explained in detail below event types the diagram below illustrates the different stages within the plug in and the corresponding events triggered start new measurement sent when the user clicks on the 'perform measurement' button on the welcome screen event data success { "stage" "startnewmeasurement", "data" { "onboarding" true } } stage "startnewmeasurement" data additional details onboarding boolean; when true , the user first landed on the onboarding screen when false , the user immediately advanced to the recording screen recording started sent when the user clicks the record button and the timer starts event data success { "stage" "recordingstarted", "uuid" "380cae2a32ed4023be60a63c3ee97e95", } stage "recordingstarted" uuid health check uuid recording stopped sent when the recording stopped, i e the recording timer ends event data success { "stage" "recordingstopped", "uuid" "380cae2a32ed4023be60a63c3ee97e95", } stage "recordingstopped" uuid health check uuid results the results of the health check in their most basic form, listing the extracted biomarker values sent after the recording is completed this takes between 1 to a maximum of 20 seconds after the recordingstopped event intelliprove calculates the following biomarkers heart rate heart rate in beats per minute respiratory rate respiratory rate in breaths per minute (nullable) heart rate variability heart rate variability or hrv in milliseconds ans balance balance of autonomous nervous system, dimensionless resonant breathing score resonant breathing score in percentage morning readiness morning readiness score, dimensionless (only available between morning hours) acute mental stress score acute mental stress score, dimensionless mental health risk mental health risk as enumerator 1 ("low"), 2 ("medium") or 3 ("high") for more info on how to interpret these values, please refer to our insights & biomarkers docid 3pruszmjt22mzxvkufpwd documentation please note that one or more biomarker values may be unavailable if the measurement quality is insufficient or if not relevant for the current time of the day (e g morning readiness) biomarkers of such are set to null in addition to the biomarkers we also provide the timestamp and epoch properties representing both an iso and integer (utc) representation of the time of the measurement event data success { "stage" "results", "uuid" "380cae2a32ed4023be60a63c3ee97e95", "patient" "5jb54ojlk23m", "performer" "083lna91utnz4v", "data" { "epoch" "1692282217", "timestamp" "2023 08 17t16 23 37+02 00", "heart rate" "54", "respiratory rate" "6", "heart rate variability" "87", "ans balance" "2", "resonant breathing score" "99", "morning readiness" "8", "acute mental stress score" "3", "mental health risk" null } } stage "results" uuid health check uuid patient (nullable) patient reference, initially passed in the web plug in url performer (nullable) performer reference, initially passed in the web plug in url data results data object buckets the biomarker buckets provide the results in an alternative format, grouping them in logical sets and providing more context to the values in each set (bucket) sent after the recording is completed this takes between 1 to a maximum of 20 seconds after the timer ends intelliprove offers a holistic approach to well being by organizing information into distinct buckets; i e physical health , mental health, sleep and energy, and mindfulness each bucket has the following properties the name distinguishes the specific bucket a list of the currently available buckets "physical", "mental", "energy sleep", "mindfulness" the timestamp and timestamp epoch properties present both an iso and integer (utc) representation with the time of the measurement the biomarkers represent a list of selected biomarkers relevant to the specific bucket the status indicates the overall users' health state for the current bucket, based on the biomarker values we define three different states "good", "neutral" and "bad" each biomarker consists of the following properties the value is the actual numerical value obtained for the biomarker during the health check it can be an integer or a floating point number the range represents the entire span of possible values for that the biomarker, indicated by minimum and a maximum the zone indicates where the biomarker value falls among three categories "good," "neutral," and "bad", which relates to health condition the optimum defines how the range should be interpreted and visualized there are three possible values for optimum "low," "high," and "middle " for "low" lower values are categorized as "good" (green color), while higher values are categorized as "bad" (red color) for "high" higher values are categorized as "good" (green color), while lower values are categorized as "bad" (red color) for "middle" the "good" zone (green color) is centered around the middle of the range values lower or higher than this midpoint are categorized as "bad" (red color) for each bucket, we provide personalised feedback and tips tailored to their specific values learn more about this in the next event type event data success { "stage" "buckets", "uuid" "380cae2a32ed4023be50a63c3ee97e95", "patient" "test patient", "performer" "test performer", "data" { "buckets" \[ { "name" "physical", "timestamp epoch" 1692282217, "timestamp" "2023 08 17t16 23 37+02 00", "status" "good", "biomarkers" \[ { "name" "heart rate", "value" 54 0, "zone" "good", "unit" "bpm", "range" \[ 36 0, 216 0 ], "optimum" "low" }, { "name" "respiratory rate", "value" 6 0, "zone" "good", "unit" "brpm", "range" \[ 4 0, 48 0 ], "optimum" "middle" } ] }, // other buckets ] } } stage "buckets" uuid health check uuid patient (nullable) patient reference, initially passed in the web plug in url performer (nullable) performer reference, initially passed in the web plug in url data buckets data object bucket summaries for each bucket, we also provide a human readable representation of the results in the format of personalised feedback (summary) and tips sent after the recording is completed since feedback and tips are generated on the fly, it takes some additional time before this event is sent expect up to 5 seconds extra event data { "stage" "bucketsummaries", "uuid" "380cae2a32ed4023be60a63c3ee97e95", "patient" "test patient", "performer" "test performer", "data" { "summaries" \[ { "name" "physical", "summary" "your heart rate is very low, suggesting a state of rest or recovery your respiratory rate is slow, indicating a relaxed and calm state ", "tip" "based on your heart rate and respiratory rate, it appears that you are in a state of deep relaxation and calmness this suggests that you are in good physical and mental health it is important to continue practicing stress management techniques to maintain this state of wellbeing " }, { "name" "mindfulness", "summary" "congratulations! your mindfulness exercise is highly effective your resonant breathing score of 99 indicates a strong synchronization between your breathing frequency and heart rate variability additionally, your low respiratory rate and heart rate suggest that you are in a state of deep relaxation and good cardio health keep up the excellent work!", "tip" "to further improve your mindfulness exercise, you can try incorporating longer exhales during your breathing practice this can help enhance the relaxation response and promote even greater synchronization between your breathing and heart rate variability keep up the great work!" }, // other buckets ] } } stage "bucketsummaries" uuid health check uuid patient (nullable) patient reference, initially passed in the web plug in url performer (nullable) performer reference, initially passed in the web plug in url data (nullable) buckets summaries data object userfinished occasionally, the conditions may deteriorate while performing the health check, making an accurate health assessment unfeasible for instance, this might happen if the lighting suddenly gets very dim in such instances, users are presented with two choices they can restart the health check by selecting the ‘ try again ’ option, or they can opt to conclude the health check without completing it successfully by clicking the ‘ continue ’ button if they select the latter option, no biomarker results will be generated we will notify you of this outcome with a “userfinished” event this event is also sent when the user's device does not have a camera or when the necessary permissions to access the camera have not been granted sent in the situation where the user ends the health scan without successfully performing a measurement event data json { "stage" "userfinished", "data" { } // rfu } stage "userfinished" data reserved for future use dismiss we will notify you with a "dismiss" event when the web plugin can be closed this can be because of the following reasons the user chose to abort the health check without starting it, i e by clicking the "return" button the measurement is finished and the results are sent via the "results" event (only sent when not using the built in results screen) the user chose to continue without performing the health scan sent when the web plugin should be closed event data json { "stage" "dismiss", "data" { } // rfu } stage "dismiss" data reserved for future use error (informative) if the health check did not complete successfully, we handle the error and retry internally for full transparency, we forward this error as an event in case your app needs to keep track of this sent to inform the platform that a health check the actual error handling is managed internally in the web plugin app event data { "stage" "error", "uuid" "380cae2a32ed4023be50a63c3ee97e95", "patient" "test patient", "performer" "test performer", "data" { "code" 10, "description" "", "fatal" false } } stage "error" uuid health check uuid patient (nullable) patient reference, initially passed in the web plug in url performer (nullable) performer reference, initially passed in the web plug in url data (nullable) error data object