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

Informative vs Standard for Trial Use

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIR Data Segmentation for Privacy (FHIR)
    • 0.1 [deprecated]
    • Security
    • Background
    • Hide

      This abstract IG includes 4 extensions on meta.security, and guidance on how to structure meaningful security labels to convey real world privacy and security policies. We will be adding addtional guidance such as search parameters for the extension. Given the lack of such guidance in FHIR and the presence of similar syntax and semantic guidance in CDA and V2 for conformance to the HL7 Healthcare Privacy and Security Classification System, this IG does supply useful implementer guidance on how to utilize the otherwise agnostic meta.security. We are developing an implementable profile for priority US regulatory security labels, which is what most implementers will be interested in. However, a implementer of data segmentation services can profile this abstract IG so that customers can create their own security labels based on the full HCS vocabulary.

      Show
      This abstract IG includes 4 extensions on meta.security, and guidance on how to structure meaningful security labels to convey real world privacy and security policies. We will be adding addtional guidance such as search parameters for the extension. Given the lack of such guidance in FHIR and the presence of similar syntax and semantic guidance in CDA and V2 for conformance to the HL7 Healthcare Privacy and Security Classification System, this IG does supply useful implementer guidance on how to utilize the otherwise agnostic meta.security. We are developing an implementable profile for priority US regulatory security labels, which is what most implementers will be interested in. However, a implementer of data segmentation services can profile this abstract IG so that customers can create their own security labels based on the full HCS vocabulary.
    • Mohammad Jafari/Kathleen Connor:5-0-0

    Description

      A majority of content in this IG is the Background section. There's very limited normative language. From an implementer's perspective, this IG does not contain enough information to develop an interoperable implementation. It seems like a ballot status of Informative is more appropriate than STU.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: