メインコンテンツへスキップ
このページの日本語版はまだありません。以下は英語の原文です。
Device vendors use different names and definitions for similar measurements. Mirobody’s crosswalk maps vendor fields to internal metrics and, where a verified match exists, LOINC codes.

Mapping status

A matching label alone is insufficient. For example, SDNN and RMSSD describe different heart-rate-variability statistics and must not share a code simply because both are called HRV. Proprietary scores may have no standard equivalent.

Python lookup

The crosswalk ships with the base Python package and needs no API key:
Mappings describe supported vocabulary, not which data a particular person’s device records. They also do not imply a ready-to-use cloud connection for every vendor. See device connections for the integrations available in the application. For the complete tables and mapping rationale, see the crosswalk data and technical reference.