This ETL is a little bit different than some of the other ETLs. This one places all of its data into a “Text Message Blood Pressures” table which is accessible from Lens. It then also creates study specific views for each study with this toggle turned on, and makes them accessible as “Blood Pressures [Study Name]” which pre-filters incident information based on the study.

Column	Description	Example Data

Column	Description	Example Data
id	The ID of the text message that help the blood pressure in Way to Health
message_text	The text of the incoming message	115/83 pulse 80
systolic	The systolic value parsed from the message	115
diastolic	The diastolic value parsed from the message	83
pulse	The pulse value parsed from the message (if found). null if not included	80
blood_pressure	The parsed systolic over the parsed diastolic	115/83
participant_id	The Way to Health ID of the participant that submitted this blood pressure	642987
study_id	The ID of the study the participant is in	340
sent_at	The date and time that Way to Health got the text message	2020-09-26 18:13:58

Additional information


How often does this run?	Daily around 6-7AM
Can it be run per-study?	No
Incremental?	No. This ETL creates/updates views into a background table that gets updated/added to	To make this incremental we would probably want to limit it to recently inserted texts. We shouldn’t be updating texts so we can probably rely on just inserting anything created recently
Updates existing rows?	Yes