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

Basic Spo 2

The Basic SPO2 category supports the measurement of the user’s oxygen saturation.

When this category is evaluated, the Basic Heart Rate (a.k.a. Pulse) category must also be evaluated. This is because oxygen saturation and pulse are very closely related measurements, and it’s nearly impossible for a system to measure oxygen saturation without having some awareness of heart rate.

Feature: Oxygen Saturation Measurement

The system SHALL be able to capture and report a Oxygen Saturation measurement from the user.

Scenario: Capture And Report Heart Rate Measurement

GIVEN

a <System> (App or Infrastructure) that can work with a <Device>

AND

a <User> of that <System>

AND

the <Heart Rate> of that <User>

WHEN

the <System> is operational

THEN

the device can capture a <Measurement> in the <System> associated with <User> that contains that user’s <Oxygen Saturation>

AND

that <Measurement> has units that are %

AND

the precision of that <Measurement> is to the unit of at least whole unit.

Scenario: LOINC Coded Oxygen Saturation Measurement

The system should provide LOINC codes along with measurements.

GIVEN

a <Measurement> of blood pressure

WHEN

the <Measurement> is retrieved

THEN

that <Measurement> is associated with a <LOINC Code> for Oxygen Saturation

AND

that <LOINC Code> is 8462-4 Oxygen Saturation

Scenario: UCUM Coded Oxygen Saturation Units

The measurement should use units coded in UCUM.

GIVEN

a <Measurement> of oxygen saturation

WHEN

the <Measurement> is retrieved

THEN

that <Measurement> is associated with a <UCUM Unit Code>,

AND

that <UCUM Unit Code> is ‘%’