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

Has there been any discussion about scenarios in which the Sender does not send all available data per a patient’s request?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US SDOH Clinical Care (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Patient Care
    • Related Page(s):
      MustSupport and Missing Data
    • Related Section(s):
      12
    • Grouping:
    • Resolution Description:
      Hide

      The standard for this IG is to send only the information required for the recipient to interpret the request for a service.  However, there is no provision for sending less than the elements required by a specific exchanged resource to meet the profile definition. 

      Will include some guidance on the ability to use a Smart on FHIR to app to allow patients to restrict the exchange of information that is not required to interpret the intent of a specific resource (e.g. remove address and/or telephone number from the patient resource prior to sending it to a community based organization) but has the potential to cause social risk.

      Show
      The standard for this IG is to send only the information required for the recipient to interpret the request for a service.  However, there is no provision for sending less than the elements required by a specific exchanged resource to meet the profile definition.  Will include some guidance on the ability to use a Smart on FHIR to app to allow patients to restrict the exchange of information that is not required to interpret the intent of a specific resource (e.g. remove address and/or telephone number from the patient resource prior to sending it to a community based organization) but has the potential to cause social risk.
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Follow up on above comment about a patient’s expressed desire to not send all data elements – has there been any discussion about scenarios in which the Sender does not send all available data per a patient’s request (privacy or other reasons)?

      Existing Wording:

      • When receiving a SDOH transaction from the Sender, the Receiving System SHALL interpret missing data elements within resource instances as data not present in the Senders systems.

      (Comment 32 - imported by: Robert Dieterle)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              celine_lefebvre Celine Lefebvre
              Request in-person:
              Celine Lefebvre
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: