TrueMotion

Owned by Former user (Deleted)
Last updated: Jan 31, 2022 by Christianne Sevinc (Unlicensed)
3 min read

Purchasing & General Information

TrueMotion collects driver data to understand driver risk and crash detections: https://gotruemotion.com/app-solutions/ Penn has a white-label version of this app called Way to Drive which we can collect data from and use to implement in interventions.

The app is available to download on iPhone and Android devices. To use the app with Way to Health (W2H), it will require contacting the TrueMotion team. If you are interested in using TrueMotion to collect driver, please visit: https://gotruemotion.com/contact/

Authorization

To authorize the TrueMotion app with W2H, you will need to contact your implementation liaison to connect the W2H study with the TrueMotion study.* The information needed to make the connection from TrueMotion include:

  • FeatureSetID

  • TreatmentID

When the connection is set up, you will enroll participants and collect the following information:

  • First and Last Name

  • Cell Phone

Once enrolled, W2H will send TrueMotion the participants information. This will send the participants a text from TrueMotion to download the app. One the participant downloads the app, W2H will start to collect trip summary data which will appear in Manage Data.

Incoming Data

W2H pulls data from TrueMotion’s S3 bucket once every hour. Therefore, you should see data appear in W2H on an hourly basis if participants have driven and have downloaded the app.

The data we will be receiving in W2H is the trip summary level data. We will store minute level data in our database that can be requested by study teams via a Help Desk ticket.

Below is the trip summary level data we are collecting:

  • StartTimeZone - Time zone offset at start of trip, as a string using standard military representation (e.g. -0500 is 5 hours behind GMT)

  • ValidUsageTime - Represents the duration of time during each trip for which sensor data is of sufficient quality that distraction events can be detected. In addition, periods of a trip below 6mph are excluded from ValidUsageTime. Units of seconds.

  • EndTimeZone - Time zone offset at start of trip, as a string using standard military representation (e.g. -0500 is 5 hours behind GMT)

  • IsDrivingCorrected - Value indicating the trip type: 0 = Trip is a non driving trip; 1 = Trip is a driving trip; -1 = No correction

  • EndTime - Trip end time

  • DriverID - Unique identifier of the driver

  • Timestamp - Timestamp of record. Used to ensure that an older record will not override a newer one

  • SDKVersion - Version of the SDK used by the app

  • DeviceModel - Device vendor’s model, varies with new releases

  • ValidCallTime - Represents the duration of time during each trip for which we can detect phone call events. Units of seconds.

  • AppVersion - Version of the mobile application

  • ModeOfTransport - Mode of transport identifier with one of the following values: CAR, PUBLICTRANSIT, AIRPLANE, TRAIN, BIKE, WALK, UNKNOWN, OTHER, UNSET

  • DeviceType - Device type (iPhone, Android, Unknown)

  • OSVersion - Device operating system

  • TripDistance - Total trip distance (in meters)

  • TripID - Unique identifier of the trip

  • CompanyID - Unique identifier of the company

  • DrivingConfidence - Signifies the confidence level of the driving prediction, between 0 and 1

  • IsDrivingPredicted - Value indicating the trip type: 0 = Trip is a non driving trip; 1 = Trip is a driving trip; -1 = Unknown

  • StartTime - Trip start time

  • BrakeDistance - The distance in a trip for which GPS speed accuracies are sufficient to detect hard-braking events. Units of meters.

  • DataAlgorithmVersion - The version of the data processing algorithm. Note: this is not the same as the scoring algorithm.

  • CorrectionTime - The time at which the trip was corrected

 

After the study has completed and participants have finished, W2H will automatically stop collecting data from the participant. Once a participant’s status has changed from an Active status (New, Enrolling, Enrolled, Ready, Started) to an Inactive status (Finished, Ineligible, Declined, Unenrolled, Invalid), W2H will alert TrueMotion to deactivate the participant’s account.

Data Syncing

We will start collecting data from participants once they’ve downloaded the app. TrueMotion will send two text reminders to participants enrolled to remind them to download the app. We recommend making sure participants know to keep their phone with them while they’re driving so the app can collect trip data. If the participant uninstalls the app or is unenrolled through W2H, we will stop collecting data from them.

If a participant is unenrolled and you’d like to re-enroll them, updating the status in W2H will NOT start the process to receive app data again. Will need to coordinate with TrueMotion team in order to set up the linkage again so W2H starts receiving data.

*W2H Implementation Lead: Take this information and send to a developer to update the TMO Mirth channels.