What does categorising approach by Re-use and Adoption apply to?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
    • 3.0.2 Overview of approaches
    • Hide

      We will add clarification that the assertions around degree of re-usability and degree of community adoption are not Da Vinci specific and are not based on formal measures, but rather from an informal subjective evaluation based on what's been observed in the area of implementation questions, global and regional IGs and feedback from implementers. 

      While formal metrics would be a wonderful addition to the chart, as yet, we have none that even capture resource usage, let alone architectural approach to exchange.

      Show
      We will add clarification that the assertions around degree of re-usability and degree of community adoption are not Da Vinci specific and are not based on formal measures, but rather from an informal subjective evaluation based on what's been observed in the area of implementation questions, global and regional IGs and feedback from implementers.  While formal metrics would be a wonderful addition to the chart, as yet, we have none that even capture resource usage, let alone architectural approach to exchange.
    • Marti Velezis / Jimmy Tcheng : 6-0-1
    • Clarification
    • Non-substantive

      What does categorising approach by Re-use and Adoption apply to? Is it the recommendation of the HREX IG that should be followed in all cases when HREX is being implememed or is it a series of assertions about the experience that has been observed. These are very different and if the latter I'd like to see some more quantative measure of frequency of use of each approach and the cost of adoption.

            Assignee:
            Unassigned
            Reporter:
            Hugh Glover
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: