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

argumentative negative statement about FHIR core

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Data Segmentation for Privacy (FHIR)
    • 0.3.0
    • Security
    • STU
    • Background
    • Hide

      accepted and will be applied.

      Show
      accepted and will be applied.
    • Mohammad Jafari / Christopher Schaut: 4-0-1
    • Enhancement
    • Non-substantive

    Description

      The first paragraph of 1.2 is not fair. The FHIR core has as much guidance as v2 core and CDA core. All of them require an IG to add to them. This paragraph is unnecessary and not helpful. The previous section has already made the v2 and cda linage clear. Remove this paragraph

      Unlike HCS-based security labeling guidance provided by HL7 Version 2.9, the CDA Data Segmentation for Privacy (DS4P) Implementation Guide, and the CDA Data Provenance IG, the FHIR Security Label Module does not provide detailed implementation guidance for FHIR implementers, because the FHIR core is agnostic to the HCS syntax requirements (although this guidance will likely be updated to reflect this IG’s specifications to some extent.)

      Attachments

        Activity

          People

            jafarim Mohammad Jafari
            john_moehrke John Moehrke
            John Moehrke
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: