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

Security Integrity tag for a Copy/Dup

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Security
    • Security Labels
    • Hide

      add to Security Policy valueset

          http://build.fhir.org/v3/SecurityPolicy/vs.html

      the v3 act codes from PrivacyMark

      Here is the specific exercpt

      <compose>
      <include>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/>
      <filter>
      <property value="concept"/>
      <op value="is-a"/>
      <value value="PrivacyMark"/>
      </filter>
      </include>
      </compose>

      Show
      add to Security Policy valueset      http://build.fhir.org/v3/SecurityPolicy/vs.html the v3 act codes from   PrivacyMark Here is the specific exercpt <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> <filter> <property value="concept"/> <op value="is-a"/> <value value="PrivacyMark"/> </filter> </include> </compose>
    • Kathleen Connor/Beth Pumo: 8-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      During discussions in FHIR-I, there are use-cases that appear with use-cases enabled by FHIR where a sender wants to tag the resources they are sending as a "Copy" or "Duplicate". Much like in the paper world where paperwork that is copied from the original is marked as a copy.

      This would most likely be in PUSH cases or Document cases, and not in cases where a FHIR server is serving up queries (REST). Although this is just to help clarify the use-case, not to create rules of use.

      A Copy is a complete copy at the time the copy was made. So it is different from SubSetted or Abstracted.

      A Copy can be used as a copy, but any changes must go back to the official copy.

      I think this is a code that should be part of the Integrity group

      http://build.fhir.org/v3/SecurityIntegrityObservationValue/vs.html

      aka

      http://build.fhir.org/v3/ObservationValue/cs.html#v3-ObservationValue-_SECINTOBV

      Note, that this code might be used in the .meta element, but might also be used in Provenance.

      ACTION: First we need a new code added, if added to the _SECINTOBV then it will autuomatically become part of HCS and the valueset in FHIR. If this is done, then this is just a vocab task.

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_moehrke John Moehrke
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: