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

Why is event.type required and event.code optional?

    XMLWordPrintableJSON

Details

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

      change type to category and subtype to code

      where

      • code 1..1 CodeableConcept example binding to a sample of specific codes
        • Type of event 
        • Describes what happened. The most specific code for the event.
        • maps to DICOM EventTypeCode
        • example binding to a valueSet including some IHE transaction use codes, and some FHIR REST codes, dicom start/stop profiles,  logical-Delete/permanent-delete
      • category 0..* CodeableConcept example binding
        • Classification of the type of event
        • Codes that classify the general type of event that happened
        • maps to DICOM EventID
        • example binding to a valueSet including the DICOM EventID  (not other) and codes from known IG., import/export, lifecycle events disclosure/archive/approve

       

      Show
      change type to category and subtype to code where code 1..1 CodeableConcept example binding to a sample of specific codes Type of event  Describes what happened. The most specific code for the event. maps to DICOM EventTypeCode example binding to a valueSet including some IHE transaction use codes, and some FHIR REST codes, dicom start/stop profiles,  logical-Delete/permanent-delete category 0..* CodeableConcept example binding Classification of the type of event Codes that classify the general type of event that happened maps to DICOM EventID example binding to a valueSet including the DICOM EventID  (not other) and codes from known IG., import/export, lifecycle events disclosure/archive/approve  
    • Kathleen Connor / Luis Maas: 8-0-1
    • Correction
    • Compatible, substantive
    • R5

    Description

      The one 'simple' element that seems to be one there could be universal interoperability on is marked as optional, while the complex detail concept where we're unlikely to get interoperability is required. That doesn't make much sense to me…

      (Comment 5 - 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: