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

Numeric Observations

This section describes requirements of observations which reflect numeric values. It applies to observations from a device, app or infrastructure that provide numeric results.

Feature: Precision is Documented And Appropriate for Each Measurement

Precision SHALL be Documented and Appropriate for each Measurement

Scenario: Precision is Documented

GIVEN

a <Measurement>

AND

a <Device> or <App>

WHEN

<Documentation> is examined

THEN

The precision of the <Measurement> is documented in <Documentation>

AND

The precision is appropriate for the <Measurement>

Scenario: Precision And Units Are Appropriate

The precision and units of a measurement shall be appropriate to the measurement. [Should we just add this for each observation with more detail specific to the measurement? For example, say that heart rate should be measured in beats per minute, precision is to the whole number of beats? – KWB]

GIVEN

A <System> (either a Device or an App)

AND

a set of <Measurements> that can be produced by <System>

WHEN

<Measurements> are examined

THEN

The precision of each <Measurement> in <Measurements> is appropriate

AND

the unit of each <Measurement> in <Measurements> is appropriate

Scenario: Converted Results Are Not Over-precise

A converted result should not be reported with greater precision that the originally measured value.

Unit conversion formulae exist to convert between different systems of units. These values are very precisely know. Simple math used to convert from a measured value in one unit system often results in overprecise reported values in other unit system. The converted value should be limited to be no more precise than the original value. For example, height is often measured in inches or centimeters, and the value when recorded in one unit system can often be reported in a different unit system depending on system configuration. Thus, a value recorded in whole inches should not be reported in more than whole centimeters.

GIVEN

a <Measurement> reported in a <Orginal Unit System> with <Original Precision>

AND

a <Device> or <App>

WHEN

the <Meausurement> is reported <Other Precision> in <Other Unit System>

AND

<Orignal Unit System> != <Other Unit System>

THEN

The <Other Precision> = <Original Precision>

Feature: Value Sets for Units Used in Measurements Are Documented And Can be Mapped to Standards

Fixed values used for units returned by the device or communicated by the App SHALL be documented.

Scenario: Unit Value Sets Are Documented

GIVEN

a <Device>

AND

an <App>

AND

<Documentation> for them

WHEN

a <Data Record> with Units is obtained

THEN

the Unit values that can found in <Data Record> are described in <Documentation>

Scenario: Unit Values Should be Mappable to UCUM

GIVEN

a <Unit Value Set> used for a Device or App

WHEN

the <Unit Value Set> is compared to UCUM

THEN

the values of <Unit Value Set> can be readily mapped to UCUM.

Scenario: Unit Values Use UCUM

Result values in a measurement should use UCUM

GIVEN

a <Quantitative Measurement>

WHEN

the <Unit> describing it is reviewed

THEN

the value of <Unit> is from UCUM

Feature: The Range of Numeric Values is Documented And Appropriate for Each Measure

Scenario: Unit Values Should be Mappable to UCUM

GIVEN

a <Unit Value Set> used for a Device or App

WHEN

the <Unit Value Set> is compared to UCUM

THEN

the values of <Unit Value Set> can be readily mapped to UCUM.

Scenario: Unit Values Use UCUM

Result values in a measurement should use UCUM

GIVEN

a <Quantitative Measurement>

WHEN

the <Unit> describing it is reviewed

THEN

the value of <Unit> is from UCUM