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

Security, Authorization, and Knowledge Artifacts

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot2
    • Clinical Decision Support
    • Artifact Repository Service
      Artifact Terminology Service
    • Overview
    • Hide

      Agreed, will add documentation that although knowledge artifacts typically would not be expected to contain PHI, test cases are sometimes authored by deriving datasets from production data. In these cases, extreme care must be taken to ensure that PHI cannot be discovered through the resulting test data

      Show
      Agreed, will add documentation that although knowledge artifacts typically would not be expected to contain PHI, test cases are sometimes authored by deriving datasets from production data. In these cases, extreme care must be taken to ensure that PHI cannot be discovered through the resulting test data
    • Howard Strasberg / Greg White: 21-0-0
    • Enhancement
    • Non-substantive

    Description

      While pointing to the "FHIR standard security mechanisms" is good, please add some content on considerations specific to knowledge artifacts.

      For example, highlighting cases where knowledge artifacts may or may not contain PHI and how that affects security.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: