How does the LAMP Data Format Work?

#

Activity Specification


Each activity that patients/participants can interact with is defined and encapsulated in an ActivitySpec that contains the applet (written in HTML), along with a schema to describe the input and output data.


#

Temporal Slices


When a patient begins an interactive session with any activity, session-wide data about who, what, and when is recorded. Each user tap within is then automatically validated and converted into a time-indexed standardized format called a TemporalSlice.


This means data processing code can be written just once and work for any activity or any user.

#

Event Stream


When the user completes the interactive session, all the TemporalSlices are packaged into chronologically ordered ActivityEvents indexed under the user's Participant object as a low-latency stream of continuously generated data.


#

Time Series Query


The researcher/data scientist can query this data at any desired temporal resolution (e.g. one millisecond, one day, one year, etc.) and filter by the type of activity (e.g. Survey, Jewels, etc.). The query can be manipulated using map/reduce document transforms and listened to notify client code directly with real-time updates.


  • Example JSONata

    // Get all participants
    $Participant_all("study").{ id, timestamp }
    // Get all activities
    $Activity_all("study").{ id, ... }
    // Get all activity events for all participants
    $Participant_all("study").$merge([$ActivityEvent_all(id), { "#parent": id }])[$exists(timestamp)]
Last updated on by Rebecca Bilden