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

statement on purpose of use should be stronger

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • STU
    • Task Based Approach
    • 4.1
    • Hide

      Will update description to promote the benefit of being able to narrow the POU beyond TPO at the transaction level.

       

      However, in regards to  "we would expect the purpose of use always be indicated for the task"

      Because this capability doesn’t really exist today – typically one overarching PoU defined at a business agreement level ( e.g. at app registration), we can't require it for every transaction. The current CDex design is flexible enough to support the current state of healthcare data and optionally provide additional granularity to define POU with a greater level of discrimination at the transaction level if and when it is implemented or required in the future.  

       

      Show
      Will update description to promote the benefit of being able to narrow the POU beyond TPO at the transaction level.   However, in regards to  "we would expect the purpose of use always be indicated for the task" Because this capability doesn’t really exist today – typically one overarching PoU defined at a business agreement level ( e.g. at app registration), we can't require it for every transaction. The current CDex design is flexible enough to support the current state of healthcare data and optionally provide additional granularity to define POU with a greater level of discrimination at the transaction level if and when it is implemented or required in the future.    
    • Eric Haas/Jay Lyle: 7-0-1
    • Clarification
    • Non-substantive

    Description

      Regarding the following sentence "Provides the ability to represent the Purpose of Use in the Task" Does this statement capture the benefit of being able to filter the information clearly enough, or should that be spelled out? Seem like a big benefit, re: patient privacy. Suggest stronger language, we would expect the purpose of use always be indicated for the task (i.e. why does the payer need the info?).

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: