SDOHCC Consent profile only covers release information on a patient to a community-based organization. However, @ http://hl7.org/fhir/us/sdoh-clinicalcare/2021JAN/StructureDefinition-SDOHCC-Consent.html#additional-guidance, payers, CBSC, and CBOs, share information with the provider and among themselves.
This Consent profile should cover all of these exchanges, either by including these exchanges as permissible under the initial consent, or by specifying how the Consent profile is to be used for each of these further exchanges. Specifically, this IG specifies how "The Provider’s System provides (via a FHIR API) the ability to share information with: Community Based Organization (CBO) – share Task and ServiceRequest and allow the CBO to respond by updating the Task status and providing feedback on the service(s) performed (Procedure(s)). Community Based Social Care Services Platform (CBSC) – share Task and ServiceRequest and allow the CBSC to respond by updating the Task status and providing feedback on the service(s) performed (Procedure(s)). Note: Typically, the CBSC interacts with the Patient and CBOs to perform the requested referrals/services using a variety of methods. Responsible Payer – provide access to health concerns (Problems) and Interventions to faciliate shared care planning for the covered member.

Existing Wording:

The SDOHCC Consent profile allows the representation of SDOH consent. One specific use for this profile is to represent a consent to release information on a patient to a community-based organization. This is usually necessary when PII or PHI is moving from a HIPAA covered entity (e.g. provider) to a non-HIPAA environment. The patient must usually consent to this exchange of personal information. The section that follows provides additional guidance on some elements in the SDOHCC Consent profile.

(Comment 197 - imported by: Robert Dieterle)