This page is part of the Application Data Exchange Assessment Framework and Functional Requirements for Mobile Health (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Actors

This section describes the different actors in the Use Cases and their roles in implementing the requirements in this guide.

Implementers

Device

Mobile Health Devices (or simply Devices) include blood pressure cuffs, weight scales, mobile phones, fitness trackers, smart watches, gps trackers, medical devices (e.g., a C-PAP machine), thermometers, SPO2 monitors, respiration devices, and clothing with embedded smart devices. These devices are often accompanied by applications (see below) and may be designed to work with specific data repositories. Devices may or may not be regulated health devices.

Features, Rules and test Scenarios applicable to Device actors will be marked with the @Device tag.

App

Mobile Health Applications (a.k.a. Mobile Health Apps or simply Apps) include integrated smart-phone Apps (e.g., Google Health, Apple Health, and Samsung Health), activity and fitness tracking Apps (e.g., FitBit and Runkeeper), weight and diet monitoring applications (e.g., Withings), and other physical fitness and health monitoring Apps.

Mobile Health Applications can also be web-based applications, so long as they are designed to be accessible via a mobile health device.

Requirements, Rules and test Scenarios applicable to App actors will be marked with the @App tag.

Data Repository

Mobile Health Data Repositories collect mobile health data from multiple devices and make it possible for users to access, analyze and aggregate data across devices. These applications may also enable population analysis for select populations.

Requirements, Rules and test Scenarios applicable to Data Repository actors will be marked with the @Infra tag.

Data Consumer

Mobile Health Data Consumers can access one or more Mobile Health Data Repositories and potentially other sources. These components provide additional tools enabling users to analyze mobile health data.

Requirements, Rules and test Scenarios applicable to Data Consumer actors will be marked with the @Consumer tag.