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

SDOH Guidance Purpose and Intent needs clarification

    XMLWordPrintableJSON

Details

    • Icon: Comment Comment
    • Resolution: Considered - No action required
    • Icon: Medium Medium
    • US Core (FHIR)
    • 4.1.0 [deprecated]
    • Cross-Group Projects
    • Social Determinants of Health (SDOH) [deprecated]
    • Hide

       See Purpose and Intent : https://build.fhir.org/ig/HL7/US-Core/sdoh.html#purpose-and-intent

      The intent of adding these SDOH data elements to US Core is to be able to use US Core Profiles along with a defined set of FHIR RESTful interactions to represent and access SDOH patient data. This is in contrast to the SDOH Clinical Care HL7 Implementation Guide. This guide was developed by the Gravity Project and documents the orchestration of SDOH data capture and related interventions and how it is represented using FHIR. US Core Profile span across use cases and thus less constrained, but they form backbone for the SDOH Clinical Care Profiles. Many of the additions to US Core Profiles to meet the SDOH data element requirements are based on the efforts by the Gravity led project. In the following sections the interrelation between the SDOH elements is summarized and how each element is represented in US Core documented.

      vs SDOH

      This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases:

      *

      Document SDOH data in conjunction with the patient encounters with providers, payers, and community services

      • Document and track SDOH related interventions to completion

      • Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer

      Show
       See Purpose and Intent :  https://build.fhir.org/ig/HL7/US-Core/sdoh.html#purpose-and-intent The intent of adding these SDOH data elements to US Core is to be able to use US Core Profiles along with a defined set of FHIR RESTful interactions to represent and access SDOH patient data. This is in contrast to the  SDOH Clinical Care  HL7 Implementation Guide. This guide was developed by the  Gravity Project  and documents the orchestration of SDOH data capture and related interventions and how it is represented using FHIR. US Core Profile span across use cases and thus less constrained, but they form backbone for the SDOH Clinical Care Profiles. Many of the additions to US Core Profiles to meet the SDOH data element requirements are based on the efforts by the Gravity led project. In the following sections the interrelation between the SDOH elements is summarized and how each element is represented in US Core documented. vs SDOH This IG addresses the need to gather SDOH information in multiple settings, share that information between stakeholders, and exchange referrals between organizations to address specific social risk needs, all with appropriate patient consent. In addition, the IG demonstrates how to share clinical data to support secondary purposes such as population health, quality, and research. The guide supports the following use cases: * Document SDOH data in conjunction with the patient encounters with providers, payers, and community services Document and track SDOH related interventions to completion Identify cohorts of individuals that have a common relationship to another entity (e.g., covered by the same payer

    Description

      How is the Purpose and Intent of the SDOH Guidance (section 2.6.1) is in contrast to the SDOH Clinical Care IG? Both appear to use SDOH data elements defined by the Gravity Project - please clarify the difference.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ruby_j_nash Ruby Nash
            Ruby Nash
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: