XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive
    • Specification:
      US FHIR Guidance - Quality Reporting (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Clinical Quality Information
    • Related Page(s):
      Home
    • Related Section(s):
      Aignment
    • Grouping:
    • Resolution Description:
      Hide

      Agree, language will be adjust to the following for clarity.  

       

      In addition, alignment reduces the need for transformation logic, which leads to more fidelity in the exchanged data and higher quality data available for use in all aspects of healthcare, including quality measurement.

      Show
      Agree, language will be adjust to the following for clarity.     In addition, alignment reduces the need for transformation logic, which leads to more fidelity in the exchanged data and higher quality data available for use in all aspects of healthcare, including quality measurement.
    • Resolution Vote:
      Rob Samples/Floyd Eisenberg: 19-0-1
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Please explain in which cases one needs to provide this transformation logic. So it sounds like if all is done with FHIR then it is already aligned with the existing clinical systems. Do you then oppose this to non FHIR implementations that may not be aligned and thus would need an additional data transforming adapter layer? This is a bit arguable then, as other solutions may also be aligned with the existing clinical information systems. So Probably here you mean that because of this existing alignment of FHIR if one uses FHIR then there is no need to writing transformation logic?

      Existing Wording:

      The less transformation logic has to be written

      Proposed Wording:

      ?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ivan_zapreev Ivan Zapreev
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: