The DeviceMetric resource describes mandatory static properties that characterize a direct or derived, quantitative or qualitative biosignal measurement, setting, or calculation produced by a medical device. The DeviceMetric resource can also be used to describe the non-static but highly relevant properties to the metric such as metric status, metric last calibration time and type, measurement mode, color, reference link to the parent DeviceComponent to where it belongs, and any capabilities that the metric offers (for example: setting the metric label).

Note:

For the initial scope, this DeviceMetric resource is only applicable to describe a single metric node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard.

Inclusion of "quantitative or qualitative biosignal measurement... or calculation" seems to border on a clinical Observation or ObservationDefinition. Clarify (without reference to 11073 language) what these terms mean. Indicate how a clinical measurement from a device is represented as an Observation (if it is intended to be) and whether that Observation references DeviceMetric; indicate how a device setting from a device is represented as an Observation (if it is intended to be) and whether that Observation references DeviceMetric; indicate how a consumer can distinguish the above resources to determine whether it is a clinical measurement or a device setting.

There is no DeviceComponent or Device.component resource/element.

Review other language in the scope statement and ensure they add value and are understandable to readers without an IEEE 11073 background. For example, "metric last calibration time" essentially repeats the resource structure; can we find ways of expressing the content that adds value? 

DeviceMetric scope should be widened to consider other than 11073 devices (or ways of describing devices in ways other than the IEEE 11073 model). Regardless of whether the scope is expanded, it should be phrased in a way that makes sense outside of 11073. E.g. what is "metric node in the containment tree that is produced by the context scanner" supposed to mean?

Distinguish scope from ObservationDefinition.

The correct codes for the metric types are registered in the RTM Management service  , but this is not required. See Terminology Systems for the correct representation of these codes in a Coding data type.

How are these codes "correct"? Does that suggest that any other codes are incorrect? The link doesn't actually go to a valueset, and requires accepting a license. There should be a public valueset in FHIR we can reference.