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

AdverseEvent.suspectedEntity.instance should allow CodeableConcept

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • AdverseEvent
    • Hide

      AdverseEvent.suspectEntity.instance should support both CodeableConcept|Reference(...existing...)

      Show
      AdverseEvent.suspectEntity.instance should support both CodeableConcept|Reference(...existing...)
    • Craig/Michael: 16-0-1
    • Enhancement
    • Non-compatible
    • R5

    Description

      Much of the time, suspect products will simply be identified by their codes. It shouldn't be necessary to go to a separate resource to capture these details (and in some cases, systems may not even know if the code is for a device, a drug or some other substance). Having a choice between CodeableConcept|Reference(whatever) as a type is a common convention. So rename to instance[x] and expand the type.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: