Is it a requirement of the spec that this is not allowed or is this a description of the anticipated behavior? - SDC #63

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • (profiles) [deprecated]
    • 10.1 Caveats and con
    • Hide

      We will revise the statement from "should not" to SHALL NOT.(and perhaps reword to read better). I.e. it is a mandatory requirement that the population process not populate information in the form if the user completing the questionnaire would not have permission to see that data if they queried it directly.

      Show
      We will revise the statement from "should not" to SHALL NOT.(and perhaps reword to read better). I.e. it is a mandatory requirement that the population process not populate information in the form if the user completing the questionnaire would not have permission to see that data if they queried it directly.
    • Paul Lynch/Ye Wang: 5-0-0
    • Clarification
    • Compatible, substantive

      Existing Wording: Users should not be able to see information populated into a form that they would not be able to see when navigating the source system directly. In some cases, this means that an answer in a form might not be populated even though the data exists - because the user doesn't have authority to see that data.

      Comment:

      Is it a requirement of the spec that this is not allowed or is this a description of the anticipated behavior?

      Summary:

      Is it a requirement of the spec that this is not allowed or is this a description of the anticipated behavior?

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: