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

AuditEvent.subType should merge into type.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R4
    • Security
    • AuditEvent
    • Hide

      The valueSets are being radically re-designed in to example binding. 

      See related https://jira.hl7.org/browse/FHIR-32443 that changes element to .code

       

      Show
      The valueSets are being radically re-designed in to example binding.  See related https://jira.hl7.org/browse/FHIR-32443  that changes element to .code  
    • Kathleen Connor / Luis Maas: 8-0-1
    • Correction
    • Compatible, substantive
    • R5

    Description

      It's not clear why a sub-type is necessary. Multiple codings at different levels of granularity can be sent as codings within AuditEvent.type, so generally speaking, there's no need for a sub-type. We have a pattern where there's a code that specifieds the detail of what's happening and then a separate 'category' element thtat categorizes the type of action in a variety of possibly orhogonal ways - but that's not what's happening here.

      (Comment 2 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            john_moehrke John Moehrke
            lloyd Lloyd McKenzie
            Lloyd McKenzie, Ron G. Parker
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: