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

VAERS form allows for multiple outcomes but .seriousness does not

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US ICSR Transfusion and Vaccination Adverse Event Detection and Reporting (FHIR)
    • 0.1.0
    • Biomedical Research & Regulation
    • ICSR Adverse Event
    • Hide

      Yes, this is a problem that it can not repeat. The R5 AdverseEvent resource splits the seriousness into a repeating outcome field. We will relook at how seriousness is mapped and potentially introduce a new extension to carry the repeating seriousness fields. We will also add a section to the Profile Descriptions page that indicates how seriouesness should be handled.

      Show
      Yes, this is a problem that it can not repeat. The R5 AdverseEvent resource splits the seriousness into a repeating outcome field. We will relook at how seriousness is mapped and potentially introduce a new extension to carry the repeating seriousness fields. We will also add a section to the Profile Descriptions page that indicates how seriouesness should be handled.
    • Jean Duteau / Peter Bomberg : 14-0-1
    • Correction
    • Non-substantive

    Description

      It appears that in the VAERS PDF form, Item 21 allows multiple results or outcomes but AdverseEvent.seriousness does not. Assuming this is the cognate element for Item 21, is it a problem that it cannot repeat? Some of the values in the seriousness value set would see to be not mutually exclusive (for example an event could be both life threatening and requiring hospitalization. Please clarify how .seriousness should be used in cases like this.

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: