Mira is a data source that enables researchers to access hormone measurements, menstrual cycle data, and participant-reported daily logs collected through Mira devices This section explains how Mira integrates with Avicenna, making it easier for researchers to understand and use participants’ health data.
Supported Mira Metrics in Avicenna
All metrics include the common data fields, along with the fields specific to each metric.
Mira Cycle
Provides menstrual cycle information. It is internally stored as mira_cycle, and includes the following fields:
- Cycle Length: Length of the cycle, in days. Internally stored as
cycle_length. - Period Start: Start date of menstruation. Internally stored as
period_start. - Period End: End date of menstruation. Internally stored as
period_end. - Fertile Window Start: Estimated start of the fertile window. Internally stored as
fertile_window_start. - Fertile Window End: Estimated end of the fertile window. Internally stored as
fertile_window_end. - Ovulation Date: Estimated ovulation date. Internally stored as
ovulation. - Current Phase: Descriptive phase label. Internally stored as
current_phase. Possible values include:- Menstrual Phase
- Follicular Phase
- Ovulatory Phase
- Luteal Phase
- Phase Start Date: Start date of the current phase. Internally stored as
phase_start_date. - Current Cycle Day: Human-readable cycle day (e.g., Day 10). Internally stored as
current_cycle_day.
Mira Hormone
Provides hormone test results. It is internally stored as mira_hormone, and includes the following fields:
- LH: Luteinizing hormone, in milli-international units per milliliter (mIU/mL). Internally stored as
lh. - E3G: Estrone-3-glucuronide, in nanograms per milliliter (ng/mL). Internally stored as
e3g. - PdG: Pregnanediol-3-glucuronide, in micrograms per milliliter (µg/mL). Internally stored as
pdg. - hCG: Human chorionic gonadotropin, in milli-international units per milliliter (mIU/mL). Internally stored as
hcg. - FSH: Follicle-stimulating hormone, in milli-international units per milliliter (mIU/mL). Internally stored as
fsh.
[!note]
Not all hormone fields are present in every record.
Mira Daily Log
Provides participant-reported daily data. It is internally stored as mira_daily_log, and includes the following fields:
- Date: Calendar date of the log. Internally stored as
date. - Symptoms: List of symptoms with optional severity levels. Internally stored as
symptoms[] { value, level }. Possible values include:- Value: Cramps, Headache, Bloating, Breast tenderness, Fatigue, Acne, Nausea
- Level: Mild, Moderate, Severe
- Skin: Skin descriptors. Internally stored as
skin. Possible values include:- Dry
- Oily
- Glowing
- Breakouts
- Mood: Mood descriptors. Internally stored as
mood. Possible values include:- Happy
- Calm
- Irritable
- Anxious
- Sad
- Energetic
- Sex: Sexual activity type. Internally stored as
sex. Possible values include:- Unprotected
- Protected
- None
- Sex Drive: Libido level. Internally stored as
sex_drive. - Notes: Free-text notes. Internally stored as
notes. - Spotting / Flow: Bleeding or spotting details. Internally stored as
spotting,flow_spotting. - OPK Result: Ovulation test result. Internally stored as
opk. - Pregnancy Test Result: Pregnancy test result. Internally stored as
pregnancy_test. - Medications: List of medications. Internally stored as
medications[] { name, unit, value }. - Cervical Mucus: Description and volume. Internally stored as
cervical_mucous { description, volume }. Possible values include:- Description: Sticky, Creamy, Watery, Egg White, None
- Volume: Low, Medium, High
- Cervical Position: Physical characteristics. Internally stored as
cervical_position { height, openness, texture }. Possible values include:- Height: Low, Medium, High
- Openness: Closed, Slightly Open, Open
- Texture: Firm, Medium, Soft
- Weight: Body weight, in kilograms (kg) or pounds (lb). Internally stored as
weight. - Glucose Control: High-level glucose control status. Internally stored as
glucose_control.
Data Collection Behavior
Mira devices and the Mira app collect hormone measurements, menstrual cycle information, and daily logs directly from participants. Data is first synced from the participant’s Mira device to their Mira account (via the Mira app). Avicenna never connects to the physical device; instead, it integrates with Mira’s cloud servers.
Avicenna periodically checks Mira’s servers for new or updated records and imports them automatically. New hormone tests, cycle updates, and daily logs become visible in Avicenna after the participant has:
- Used their Mira device and/or logged information in the Mira app, and
- Successfully synced the Mira app with Mira’s servers.
[!note]
Because Avicenna depends on Mira’s sync behavior and the participant’s connectivity, there can be short delays between when a participant performs a test or logs an entry in Mira and when that record appears in Avicenna.
Adding Mira As a Data Source
See Adding Data Sources.
Monitoring and Exporting Mira Data
You can monitor and export Hexoskin data using either the Data Export page or Kibana.