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

Boundary between Flag, DetectedIssue and AdverseEvent is ambigu

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • Clinical Decision Support
    • STU
    • AdverseEvent
      DetectedIssue
      Flag
    • 9.10, 9.9,8.13
    • Hide

      For the DetectedIssue resource, the boundaries are identified in the Scope and Usage section. Suggest we could add AdverseEvent as one of the resources named there:

      [Current]

      These guidelines can be captured using the AllergyIntolerance, and/or Flag resources.

      [Suggested]

      These guidelines can be captured using the AllergyIntolerance, AdverseEvent, and/or Flag resources.

      Show
      For the DetectedIssue resource, the boundaries are identified in the Scope and Usage section. Suggest we could add AdverseEvent as one of the resources named there: [Current] These guidelines can be captured using the  AllergyIntolerance , and/or  Flag  resources. [Suggested] These guidelines can be captured using the  AllergyIntolerance , AdverseEvent, and/or  Flag  resources.
    • Rob McClure/Howard Strasberg: 17-0-0
    • Clarification
    • Non-substantive
    • R5

    Description

      Flag, DetectedIssue and AdverseEvent all touch the topic that something needs attention. 
      Please extend to boundaries and relationships section of each resource and explain this boundary more clearly.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: