mHealth specification
  • Introduction
  • Directory structure
    • Overview of directory structure
  • File types
    • Quick view of supported file types
  • sensor Data
    • Filename convention
    • File format
    • Sensor types
    • Data types
  • event Data
    • Filename convention
    • File format
    • Event types
  • annotation Data
    • Filename convention
    • File format
  • feature Data
    • Filename convention
    • File format
Powered by GitBook
On this page
  • Filename convention
  • SensorType
  • DataType
  • SENSORID
  • DATATYPE
  • VERSIONCODE
  • Timestamp
  1. sensor Data

Filename convention

Used to store raw numerical sensor data in high or low sampling frequency.

Filename convention

SensorType-DataType.SENSORID-DATATYPE-VERSIONCODE.YYYY-MM-DD-HH-mm-ss-SSS-[M/P]HHmm.sensor.csv(.gz)

SensorType

  1. Used to specify the type of sensor (or device, if multiple sensors are on the same device, such as phone, IMU device or smart watch).

  2. Locally unique.

  3. Camel Style, allowed characters: alphabets and digits.

  4. Required.

Examples

AndroidPhone, AndroidWear,GT3X,GT9X

See a complete list of predefined sensor types.

DataType

  1. Used to specify the type of data this file refers to. The same device can support collecting multiple types of data, such as smart phone can be used to collect acceleration, orientation, light and sound.

  2. Locally unique.

  3. Camel Style, allowed characters: alphabets.

  4. Required.

Examples

AccelerometerCalibrated, GPSLocation, Light, Sound, HeartRate

See a complete list of predefined sensor data types.

SENSORID

  1. A global unique identifier for a specific device. For most devices, it could be the serial number. For phone, it could also be the IMEI number.

  2. UPPERCASE, allowed characters: alphabets and digits.

  3. Required.

Examples

,

See the predefined list for recommended sensor id sources for different sensor types.

DATATYPE

  1. Uppercase version of DataType, used as locally unique identifier.

  2. UPPERCASE, allowed characters: alphabets and digits.

  3. Optional, if omitted, don't put - after SENSORID.

Examples

ACCEL, GYRO

See a predefined list for recommended data id sources for different data types.

VERSIONCODE

  1. Used to specify the version for the specific sensor, as firmware or software may be upgraded. This is used to distinguish data collected from the same sensor but with different firmware or software version.

  2. CamelStyle, allowed characters: alphabets and digits.

  3. Optional. If omitted, use NA as default.

Examples

V1, V2, FW10, SW23

Timestamp

  1. Represent the start time or the first row's timestamp of current sensor data file.

  2. YYYY-MM-DD-HH-mm-ss-SSS-[M/P]HHmm

  3. In local time zone.

Examples

M0500 means UTC-5h which is the United States Eastern Standard Time. See wikipedia for a complete map between time zone offset and time zone region code.

PreviousQuick view of supported file typesNextFile format

Last updated 6 years ago