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

Suggest to remove the statements as there always is authorization somewhere

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • current
    • Patient Care
    • Specification [deprecated]
    • Hide

      clarify the assertion from:

       

      Authorization

      "The most common scenario is where Task can (and even should) exist without an authorization. Task is used alone when there is no need for a formal authorization (order). In other situations when an authorization is needed, the Task.basedOn element references either a CommunicationRequest or ServiceRequest to represent the authorization for data to flow. Both of these use cases ( with and without authorization) are illustrated in the examples below."

      to 

       

      Formal Request To Share Data

      "There are situations where one must provide formal authorization for each individual data request.  In other cases  an overall data sharing agreement makes the need for such individual authorizations unnecessary.  Where such individual authorizations are not required, Task can be used alone.  When a formal request for the information to be shared is needed, it is represented by either a CommunicationRequest or ServiceRequest and referenced by Task using the the Task.basedOn element.  Use cases with and without authorization are illustrated in the examples below."

       

      Show
      clarify the assertion from:   Authorization "The  most common  scenario is where Task can (and even should) exist without an authorization. Task is used alone when there is no need for a formal authorization (order). In other situations when an authorization is needed, the  Task.basedOn  element references either a  CommunicationRequest  or  ServiceRequest  to represent the authorization for data to flow. Both of these use cases ( with and without authorization) are illustrated in the examples below." to    Formal Request To Share Data "There are situations where one must provide formal authorization for each individual data request.  In other cases  an overall data sharing agreement makes the need for such individual authorizations unnecessary.  Where such individual authorizations are not required, Task can be used alone.  When a formal request for the information to be shared is needed, it is represented by either a  CommunicationRequest  or  ServiceRequest  and referenced by Task using the the  Task.basedOn  element.  Use cases with and without authorization are illustrated in the examples below."  
    • Eric Haas/Jay Lyle: 11-0-11
    • Clarification
    • Non-substantive

    Description

      Suggest to remove the statements as there always is authorization somewhere, starting with being granted access to the system to interact, as well as that it is not clear yet, nor fully relevant in this IG, when a request specific authorization is required, a purpose of use level, is sufficient, or otherwise.

      Existing Wording:

      The most common scenario is where Task can (and even should) exist without an authorization.

      (Comment 34 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: