CIMI Principles

Pending

1. ASSERTION vs. EVALUATION_RESULT criteria
   1. from 2017-02-02 CIMI minutes
   2. 'Reasoning' vs. 'Finding', 'Subjective' vs. 'Objective', 'Fact-ish' vs. 'Judgement-ish' categories work > 80% of the time; but, they are not reliable criteria for a small set of "edge cases'.
      1. In most cases it is obvious, when to use ASSERTION (e.g., 'Reasoning', 'Subjective', 'Judgement-ish' things, such as DIAGNOSIS, PROBLEM, COMPLAINT, FAMILY_HISTORY)
         1. The Patient DISCHARGE_DIAGNOSIS is ... (implying the set of findings defining the DISCHARGE_DIAGNOSIS)
         2. John has blue eyes
      2. In the small number of cases, where it is not obvious when to use ASSERTION, CIMI prefers
         1. ASSERTIONS be used when the answer to an EVALUATION_RESULT is 'Present' or 'Absent', 'Yes' or 'No', 'True' or 'False', etc.
      3. Although theoretically possible; but for practical implementation reasons, CIMI does not support round-trip conversion between EVALUATION_RESULT and ASSERTION structures, as shown by the set of ATTRIBUTE vs. EVALUATION_RESULT attributes shown above.

Out of Scope

1. OUT OF SCOPE: Implementations characteristics are out of scope.
   1. CIMI is not directly concerned with wire formats. [principle]
   2. Realms may choose non-CIMI preferred units of measure and terminology for communications; where, it is the realm’s responsibility to have an equivalent concept in their terminology and to produce the mapping to the standard code.
   3. Implementations of user facing point-of-capture and point-of-use applications may use any units of measure or terminologies that they like, as long as communications use CIMI preferred SI units and standard terminologies. [principle, style guide/implementation guidance]
   4. Transformation fidelity (e.g., Millimeters to whole inches may be imprecise, inches to lb. /sq. ft. may be meaningless) and safety as a whole are design specifications, beyond CIMI’s scope.