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

Add "Purpose of Use" at Group.member as an extension

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci ATR (FHIR)
    • current
    • Financial Mgmt
    • ATRGroup
    • Artifacts Summary
    • 8.10.1
    • Hide

      The WG recommends not adding the Purpose of Use at the Group.member level but rather have the Purpose of Use bound to the Group.characteristic.code so that the Export process is simple and is implementable. The implementers can create as many groups as needed for the differing Purpose of Use using the Group.Characteristic code. Add the CDeX value set concepts to the Group.characterstic.code binding to allow broader purpose of use. 

      Show
      The WG recommends not adding the Purpose of Use at the Group.member level but rather have the Purpose of Use bound to the Group.characteristic.code so that the Export process is simple and is implementable. The implementers can create as many groups as needed for the differing Purpose of Use using the Group.Characteristic code. Add the CDeX value set concepts to the Group.characterstic.code binding to allow broader purpose of use. 
    • Nagesh Bashyam/Jeff Brown: 15-0-0
    • Correction
    • Compatible, substantive

      In specific Use Cases for exchanging Patient Lists, you need to know the purpose of Use. That purpose of use for one list being sent to a specific system may have different "purpose of use" so we need an extension at Group.member that allows for this concept. The terminology might be https://terminology.hl7.org/ValueSet-v3-PurposeOfUse.html

            Unassigned Unassigned
            lmichaelsen Linda Michaelsen
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: