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

add 'information' as Group.type code and add Evidence as Group.member.entity options

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Evidence
      Group
    • Hide

      There has been scope creep in the Group resource over time; based on the initial intent, we should limit Group to (at most) things that we consider "participants"; see http://build.fhir.org/participant.html#Participant. On this reasoning, we'd align Group with the participants list, removing resources that do not fit the participant pattern and adding any that do. We should update the documentation for Group to clarify that it focused on "participant"-type members.

      (For other collection-type use cases, like lists of evidence we point implementers toward the List resource – e.g. using an Expression extension if needed to attach inclusion criteria).

      This distinction is consistent with the current "boundaries" defined for Group

      Show
      There has been scope creep in the Group resource over time; based on the initial intent, we should limit Group to (at most) things that we consider "participants"; see http://build.fhir.org/participant.html#Participant . On this reasoning, we'd align Group with the participants list, removing resources that do not fit the participant pattern and adding any that do. We should update the documentation for Group to clarify that it focused on "participant"-type members. (For other collection-type use cases, like lists of evidence we point implementers toward the List resource – e.g. using an Expression extension if needed to attach inclusion criteria). This distinction is consistent with the current "boundaries" defined for Group
    • Rick Geimer / Jeff Brown: 7-0-0
    • Enhancement
    • Non-compatible
    • R5

    Description

      September 2019 Connectathon Evidence-Based Medicine Track evaluated changes requested to Group Resource to enable intended use of Evidence Resource. For a common use of Evidence to represent a meta-analysis the Group will be a group of Evidence (from studies) rather than a group of persons (as may occur for the studies). This change request was shared Wednesday Q2 to CDS/CQI/FHIR-I in-person meeting.

      1. Add 'information' as an allowable code to Group.type

      Group.type 1..1 code — person | animal | practitioner | device | medication | substance | information

      2. Add 'Evidence' as an allowable type of resource to Reference in Group.member.entity

      Group.member.entity 1..1 Reference (Patient | Practitioner | PractitionerRole | Device | Medication | Substance | Group | Evidence)

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            balper Brian S. Alper
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: