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

Clarify differences in VAERS and FAERS MessageHeader profiles

    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
    • FAERS MessageHeader [deprecated]
      VAERS MessageHeader [deprecated]
    • Hide

      ICH R3, which is what VAERS uses, does not have a receiver organization set of data elements so the destination.receiver is not required. However, we agree that for FHIR purposes, it makes sense to have one MessageHeader profile with common constraints. We will change this.

      Show
      ICH R3, which is what VAERS uses, does not have a receiver organization set of data elements so the destination.receiver is not required. However, we agree that for FHIR purposes, it makes sense to have one MessageHeader profile with common constraints. We will change this.
    • Jean Duteau / Peter Bomberg : 14-0-1
    • Enhancement
    • Non-compatible

    Description

      Please clarify why the FAERS MessageHeader profile requires destination.receiver but the VAERS MessageHeader profile does not? If the requirements should be the same is there a need to have 2 separate profiles?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: