Jan 2015 Ballot Comment #32

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Modeling & Methodology
    • Datatypes
    • Data Types
    • Hide
      • rename Quantity to MeasuredQuantity, but leave the definition otherwise the same
        * define a new constraint on Measure called "Quantity" that prohibits the use of comparator
        * change the following elements to reference MeasuredQuantity instead of Quantity
        • Observation.value[x]
          ** Observation.component.value[x]
          ** QuestionnaireAnswers.group.question.answer.value[x]
      • leave all the other references to Quantity as they are.

      Under eVote on MnM list

      Quantity is used in a wide variety of circumstances where "comparitor" is unnecessary. ?Every place in the financial resources we have a numeric amount, all places in scheduling where there's an ability to have a quantity or a range, and even within range, it would be wrong/inappropriate to have comparitor present. ?Primary use-case is Observation.value, which is already a choice of data types. ?Agree that using Range for this would be incorrect, but agree to introduce a new data type for this purpose.

      ?

      2015-01-19 MnM Q2 Bill/Gaby 16-0-0

      OO reviewed.? Motion to accept the disposition where Observation.value will have a choice of data types.? Eric Haas, Patrick Loyd.? 9-0-0

      Show
      rename Quantity to MeasuredQuantity, but leave the definition otherwise the same * define a new constraint on Measure called "Quantity" that prohibits the use of comparator * change the following elements to reference MeasuredQuantity instead of Quantity Observation.value [x] ** Observation.component.value [x] ** QuestionnaireAnswers.group.question.answer.value [x] leave all the other references to Quantity as they are. Under eVote on MnM list Quantity is used in a wide variety of circumstances where "comparitor" is unnecessary. ?Every place in the financial resources we have a numeric amount, all places in scheduling where there's an ability to have a quantity or a range, and even within range, it would be wrong/inappropriate to have comparitor present. ?Primary use-case is Observation.value, which is already a choice of data types. ?Agree that using Range for this would be incorrect, but agree to introduce a new data type for this purpose. ? 2015-01-19 MnM Q2 Bill/Gaby 16-0-0 OO reviewed.? Motion to accept the disposition where Observation.value will have a choice of data types.? Eric Haas, Patrick Loyd.? 9-0-0
    • Lloyd Mckenzie / Grahame Grieve: 11-1-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      Comments
      The Quantity type allows a Comparator, which turns the Quantity into a QuantityInterval with unspecified boundaries. The comparator property fundamentally changes the nature and semantics of Quantity. In order to capture the proposed semantics, we recommend that a different approach be taken, one based on a quantity range that represents an open interval.

      The problem is that when dealing with Quantities in a reasoning context, the execution environment must always deal with the possibility that the Quantity isn't a specific quantity, but rather a range of quantities with a boundary on one side only if this attribute is filled.

      Disposition WG
      Modeling & Methodology

      Grahame's Comments
      Well, it's not a range either; its a single value whose value has a known bound. If you're going to reason, you'll have to reason between that differences too. And it just moves the pain around, if you make every quantity a choice between Quantity and QuantityBoundedValue (and many of them will be). Definitely deck chairs on the titanic. I definitely favour not changing this; it would make reasoning ever so slightly easier, while making normal implementation harder

            Assignee:
            Unassigned
            Reporter:
            Bryn Rhodes
            Bryn Rhodes
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: