This ETL is a little bit different than some of the other ETLs. This one places all of its data into an “Incidents” 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 “Incidents [Study Name]” which pre-filters incident information based on the study.

Column	Description	Example Data

Column	Description	Example Data
incident_id	The ID of the incident in Way to Health
study_id	The ID of the study in Way to Health	328
participant_id	The Way to Health ID of the participant this incident is related to	608274
message	The content of the incident	Text failed to get delivered to…
incident_status	The status of the incident	“Resolved”/”New”/”Open”
incident_date	The date and time the incident was created	2020-08-30 15:02:53
incident_type	The type of the incident	“Software”/”Equipment”/”Medical”/”Other”/etc
inbound_message_text	If the incident was triggered by an incoming message, the content of that message

Additional information


How often does this run?	Daily at around 4:40 AM
Can it be run per-study?	No
Incremental?	No. This ETL creates/updates views into a background incident table that gets updated/added to	To make this incremental we would probably want to limit it to recently updated/created incidents
Updates existing rows?	Yes