2015May core #198 - How are variables being identified?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Devices
    • DeviceMetric
    • 5.12.7
    • Hide

      Enhance the documentation with an example that makes clear this is an identifier and unique within the device.

      ?

      Now we have an example (from other updates), and a description of the element. Identifier is not the codeable concept identifier but instead an internally generated ID.

      Show
      Enhance the documentation with an example that makes clear this is an identifier and unique within the device. ? Now we have an example (from other updates), and a description of the element. Identifier is not the codeable concept identifier but instead an internally generated ID.
    • Stefan Schlichting / Chris Courville: 19-0-0
    • Clarification
    • Non-substantive

      Existing Wording: DeviceMetric.identifier - Describes the unique identification of this metric that has been assigned by

      the device or gateway software. For example: handle ID. It should be noted

      that in order to make the identifier unique, the system element of the

      identifier should be set to the unique identifier of the device.

      Comment:

      IEEE 11073 has two ways to identify a variable. 1) a code that begins with MDC and 2) a numeric code for the same variable. Not crystal clear which one they are referring to. But the example shows a pure numbers

      These serve exactly the same role as LOINC codes and are IDs for observations (Mostly)

            Assignee:
            Unassigned
            Reporter:
            clemmcdonald
            clemmcdonald
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: