2015May sdc #69 - Add discussion of security labels, etc.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • DSTU1
    • FHIR Infrastructure
    • (profiles) [deprecated]
    • Hide

      Full details on exactly how consent, provenance, etc. are captured (or even if they're captured) is subject to implementation-specific business rules and is outside the scope of the SDC IG beyond what's already documented in the sdc-security page.

      However, we will amend that page to make specific reference to security labels as another aspect of the mix and will also discuss the workflow considerations of how to exchange SDC resources in a RESTful manner while also capturing Provenance and AuditEvent records where systems need to do so.

      Show
      Full details on exactly how consent, provenance, etc. are captured (or even if they're captured) is subject to implementation-specific business rules and is outside the scope of the SDC IG beyond what's already documented in the sdc-security page. However, we will amend that page to make specific reference to security labels as another aspect of the mix and will also discuss the workflow considerations of how to exchange SDC resources in a RESTful manner while also capturing Provenance and AuditEvent records where systems need to do so.
    • Richard/Jenny: 5-0-2
    • Enhancement
    • Non-substantive
    • DSTU1

      Comment:

      Explain how SDC implementers should utilize the FHIR Security Labels, AuditEvent and Provenance Resources, and Consent Directive profile to meet the privacy and security requirements of their domains.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: