> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirobody.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Device Crosswalk

> デバイスの項目を調べ、確認済み・未確認・対応なしの結果を見分けます。

対象 mirobody
`1.5.10`
· 元ファイル
[`docs/site/device-crosswalk.md`](https://github.com/thetahealth/mirobody/blob/b37cd7b24af5251a4364aab30905a7497fc69dcb/docs/site/device-crosswalk.md)

> [!NOTE]
>
> このページの日本語版はまだありません。以下は英語の原文です。

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

| Status | Meaning |
| - | - |
| `confident` | The vendor definition matches the reviewed LOINC axes. |
| `unverified` | A possible match needs confirmation. |
| No code | The field has no suitable mapping; the explanation is retained. |

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:

```python theme={null}
from mirobody.standardize import devices

field = devices.lookup("apple", "HKQuantityTypeIdentifier", "stepCount")
print(field.metric, field.loinc, field.confidence)
```

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](https://docs.mirobody.ai/en/providers/using-providers.md)
for the integrations available in the application.

For the complete tables and mapping rationale, see the
[crosswalk data](https://github.com/thetahealth/mirobody/tree/b37cd7b24af5251a4364aab30905a7497fc69dcb/mirobody/res/crosswalks) and
[technical reference](https://github.com/thetahealth/mirobody/blob/b37cd7b24af5251a4364aab30905a7497fc69dcb/docs/device-crosswalk.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.