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

Coded Observations

Feature: Value Sets for Coded Measurements Are Documented And Can be Mapped to Standards

Fixed values in a list returned by the device or communicated by the App SHALL be documented.

Scenario: Value Sets Are Documented

GIVEN

a <Device>

AND

an <App>

AND

<Documentation> for them

WHEN

a <Data Record> is obtained

THEN

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

Scenario: Value Sets Should be Mappable to Standard Terminologies

GIVEN

a <Value Set> used for a Device or App

WHEN

the <Value Set> is compared to standard terminologies (e.g., SNOMED CT®, LOINC®, UCUM, et cetera)

THEN

the values can be readily mapped.

Feature: Standards Terminology is Used for Measurements

If codes are present in measurements, standard terminology SHOULD be used for observation codes, values and units.

Scenario: Codes Describing Observations Use LOINC® or SNOMED CT®

Measurements should be described using LOINC and/or SNOMED CT

GIVEN

a <Measurement>

WHEN

the <Code> describing it is reviewed

THEN

it comes from SNOMED CT or LOINC

Scenario: Units Are Coded Using the UCUM Unit Terminology System

Units should be coded using UCUM

GIVEN

a <Measurement>

WHEN

the <Code> describing it is reviewed

THEN

it comes from SNOMED CT or LOINC

Scenario: Coded Values Use SNOMED CT or ICD-10

Result values in a measurement should use SNOMED CT or ICD-10 NOTE: ICD-10 may include national variants (e.g., ICD-10-CM in the US)

GIVEN

a <Measurement>

WHEN

the <Value> describing it is reviewed

THEN

it comes from SNOMED CT or ICD-10