Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-27396

Possibly re-position the text

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US FHIR Guidance - Quality Reporting (FHIR)
    • 0.1
    • Clinical Quality Information
    • Home
    • Expressivity
    • Hide

      For the first bullet, these concepts were covered in the table above and are introduced in the Expressivity section to define how they relate to one another.  

      The second bullet has been addressed as part of the resolution of FHIR-27404.

       

       

      Show
      For the first bullet, these concepts were covered in the table above and are introduced in the Expressivity section to define how they relate to one another.   The second bullet has been addressed as part of the resolution of FHIR-27404 .    
    • Floyd Eisenberg/Rob Samples: 27-0-1
    • Correction
    • Non-substantive

    Description

      • Why do we need to relate Expressivity, Alignment and Fitness in this section? This seems to be something more to the summary. the Alignment and Fitness are even not officially defined yet.
      • The 'Semantic Fitness' is named just 'Fitness' In the table on page 9. Please make this consistent.

      Existing Wording:

      Expressivity, Alignment, and Semantic Fitness are related concepts. Expressivity addresses whether explicit, unambiguous meaning can be sufficiently represented in a model. Alignment addresses closeness of data semantics across use cases, most importantly existing systems of record. Fitness addresses how closely data semantics convey or express real-world concepts.

      Proposed Wording:

      ?

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivan_zapreev Ivan Zapreev (Inactive)
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: