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

Better explain risk scenarios

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Synchronization considerations [deprecated]
    • 4.2.1
    • Hide

      Note that each of the scenarios does (tersely) explain the rationale for assigning these risk levels. 

      We will also add some additional background at the top of the page, something like this:

      > Each scenario suggests a level of risk resulting from potential context synchronization failure, based upon the user's ability to distinguish between disparate applications. Implementers must assess and determine the appropriate response to potential synchronization failure given their application's workflows and users.

      Show
      Note that each of the scenarios does (tersely) explain the rationale for assigning these risk levels.  We will also add some additional background at the top of the page, something like this: > Each scenario suggests a level of risk resulting from potential context synchronization failure, based upon the user's ability to distinguish between disparate applications. Implementers must assess and determine the appropriate response to potential synchronization failure given their application's workflows and users.
    • Bas van den Heuval / Eric Martin: 5-0-0
    • Clarification
    • Non-substantive
    • Yes

    Description

      Assertions are made throughout this page about levels of risk, e.g. in 4.2.1.1, "Syncronization failure significance" is "low" risk. Additional support or explanation is needed to clarify why these risk levels have been determined. The summaries are overly terse, and do not sufficiently explain why the resulting clinical risk assessment has been given the risk it has.

      (Comment 40 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: