This resource describes the required and desired behavior of systems acting as SDOH clinical care ‘coordination platforms’ (CPs).

This resource describes the required and desired behavior of systems acting as apps for patients and care-givers who need to monitor progress on SDOH referrals and may need to take actions such as filling out forms, booking appointments, etc.

This resource describes the required and desired behavior of systems acting as SDOH clinical care ‘referral recipients’.

This resource describes the required and desired behavior of systems acting as ‘light-weight’ SDOH clinical care ‘referral recipients’.

This resource describes the required and desired behavior of systems acting as SDOH clinical care ‘referral sources’.

Profile for Social Determinants of Health (SDOH) conditions.

Profile for consent related to the release of Social Determinants of Health (SDOH) information to non-HIPAA covered organizations.

Profile for goals that address Social Determinants of Health (SDOH).

Profile for identifying groups of patients who have a Social Determinants of Health (SDOH) condition and are members of a specific payer organization.

Profile that describes the means by which a healthcare service can be contacted.

Profile that describes address information for a healthcare service.

Profile for Social Determinants of Health (SDOH) observations that involve assessment (e.g., by a provider, payer, etc.) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). The Cross-Group Projects work group granted a variance to US Core on 06/10/2021 - Jira ticket FHIR-32892.

Profile for observations that represent question and answer pairs from Social Determinants of Health (SDOH) screening instruments that are represented in LOINC. The Cross-Group Projects work group granted a variance to US Core on 12/03/2020 - Jira ticket FHIR-29795.

Profile for interventions that address Social Determinants of Health.

Profile for service requests that address Social Determinants of Health.

Profile for SDOH-related tasks to be carried out by the patient or someone acting on their behalf.

Profile for tasks requesting fulfillment of an SDOHCC ServiceRequest (i.e. referral for service) and subsequently tracking and managing the fulfillment of that referral.

This value set contains all of LOINC and SNOMED CT.

Codes for the status of a screening response observation.

Codes that represent Social Determinants of Health (SDOH) domains.

Codes that represent categories of Social Determinants of Health (SDOH) questionnaires.

Codes for the general action a task involves.

Codes for the priority of a task for a patient.

Codes for the status of a task for a patient.

A local code system defined within the context of the SDOH-CC IG.

An example of a patient. This example is used as the referenced patient in other examples in this IG.

An example of a Consent for information disclosure related to SDOH information.

An example of a food security Goal that addresses a food insecurity Condition.

An example of Group for patients that have any SDOH condition and are members of a specific payer organization.

An example of a HealthcareService with telecom(s) that can be used to make an appointment flagged. This example is used as the referenced healthcare service in other IG examples.

An example of a Location for a HealthcareService that the patient might want to schedule an appointment at. This example is used as the referenced location in other IG examples.

An example of a social isolation Observation that is not necessarily derived only from a screening survey. This observation involves additional assessment (e.g., by a provider, payer, etc.). This example also includes an Observation.category (i.e., Social Connection) that, at the time the example was added to the IG, was not yet in the “SDOHCC ValueSet SDOH Category”. The example illustrates that categorization is possible using category codes that may not yet be included in the SDOHCC ValueSet SDOH Category (which will continue to be expanded as the Gravity Project continues to develop SDOH terminology content).

An example of an inadequate food intake Observation that is not necessarily derived only from a screening survey. This observation involves additional assessment (e.g., by a provider, payer, etc.).

An example of a transportation Observation that is not necessarily derived only from a screening survey. This observation involves additional assessment (e.g., by a provider, payer, etc.). This example also includes an Observation.category (i.e., Transportation Insecurity) that is included in the “SDOHCC ValueSet SDOH Category”. Additionally, a subcategory of Transportation Insecurity (i.e., Transportation Insecurity Financial) is included to illustrate that it is possible to further subcategorize a “SDOHCC ValueSet SDOH Category” code with a code that is not in the ValueSet.

An example of a clinic Organization. This example is used as the referenced organization in other IG examples.

An example of a coordination platform Organization. This example is used as the referenced organization in other IG examples.

An example of a payer organization. This example is used as the referenced organization in other SDOHCC examples.

An example of a Practitioner. This example is used as the referenced practitioner in other IG examples.

An example of a family medicine physician PractitionerRole. This example is used as the referenced practitioner role in other IG examples.

An example of a completed Procedure for assistance with applying to a food pantry that is based on a ServiceRequest and references as its reason a food insecurity Condition.

An example of a completed Procedure for provision of food.

An example of a completed Procedure for assistance with applying to a summer food program that is based on a ServiceRequest and references as its reason a food insecurity Condition.

An example of an active ServiceRequest for assistance with applying to a food pantry that references as its reason a food insecurity Condition.

An example of a completed, original-order ServiceRequest (i.e., SDOHCC Service Request Active Food Pantry Application Assist Example) that is based on a Service Request to an intermediary organization (e.g., a Coordination Platform) that then created this Service Request (i.e., Assistance with application for garden program) to be fulfilled by a Community Based Organization.

An example of a completed, original-order ServiceRequest (i.e., SDOHCC Service Request Active Food Pantry Application Assist Example) that is based on a Service Request to an intermediary organization (e.g., a Coordination Platform) that then created this Service Request (i.e., Assistance with application for Summer Food Service Program) to be fulfilled by a Community Based Organization.

An example of an accepted Task For Referral Management that has as the Task.focus a ServiceRequest for assistance with applying to a food pantry.

An example of a completed Task For Referral Management that has a ServiceRequest for assistance with applying to a food pantry as the Task.focus and a Procedure for assistance with applying to a food pantry as the Task.output.

An example of an accepted Task For Referral Management that delegates responsibility to fulfill a referral from an intermediary organization to another organization (e.g., when a Coordination Platform receives a Task from a referral source and passes it on to a Community Based Organization).

An example of a completed Task For Referral Management that delegates responsibility to fulfill a referral from an intermediary organization to another organization (e.g., when a Coordination Platform receives a Task from a referral source and passes it on to a Community Based Organization).

An example of a completed Task For Patient where the task was to make an appointment.

An example of a completed Task For Patient where the task was to complete a Hunger Vital Signs questionnaire (a questionnaire of the category ‘risk questionnaire’).

A Questionnaire instance that represents the questions and answers from the LOINC Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9).

An example of an SDC QuestionnaireResponse that represents questions and selected answers from the LOINC Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9). The example is generated using the LHC-Forms SDC Questionnaire App.

A StructureMap instance that represents the resource that transforms specific questions and answers from the LOINC Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9) into their corresponding Observations (SDOHCC Observation Response Hunger Vital Sign Q1 Example, SDOHCC Observation Response Hunger Vital Sign Q2 Example, and SDOHCC Observation response Hunger Vital Sign Q3 Example) and derived Condition (SDOHCC Condition Food Insecurity Example).

An example of an Observation grouping that has as its members the 3 Observations generated from the LOINC Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9).

An example of a screening response Observation that represents the first question (LOINC code 88122-7) and answer from the Hunger Vital Sign [HVS] screening questionnaire represented in LOINC.

An example of a screening response Observation that represents the second question (LOINC code 88123-5) and answer from the Hunger Vital Sign [HVS] screening questionnaire represented in LOINC.

An example of a screening response Observation that represents Food insecurity risk [HVS] (LOINC code 88124-3) from the Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9). This Observation is derived from the two Observations generated from the first two questions in the Hunger Vital Sign [HVS] questionnaire. This Observation does not have an Observation.performer because Food insecurity risk [HVS] is derived as opposed to answered directly on the questionnaire.

An example of a food insecurity Condition (a health concern) that references, as evidence, Observations derived from the LOINC Hunger Vital Sign [HVS] questionnaire (88121-9).

An example of a software device. This example is used as the referenced device in other SDOHCC examples.

An example of a food insecurity Condition that references, as evidence, Observations derived from the LOINC Hunger Vital Sign [HVS] questionnaire (88121-9) and uses an extension on Condition.asserter to reference the software device that uses the answers to HVS questions 1 and 2 to derive the answer to HVS question 3 (at risk for food insecurity).

A Questionnaire instance that represents the questions and answers from the PRAPARE questionnaire represented in LOINC (code 93025-5).

An example of an SDC QuestionnaireResponse that represents questions and selected answers from the PRAPARE questionnaire represented in LOINC (code 93025-5). The example is generated using the LHC-Forms SDC Questionnaire App.

A StructureMap instance that represents the resource that transforms specific questions and answers from the PRAPARE questionnaire represented in LOINC (code 93025-5) into their corresponding Observations and derived Conditions (health concerns).

An example of a screening response Observation that represents a question and answer related to unmet child care needs from the PRAPARE questionnaire represented in LOINC.

An example of a screening response Observation that represents a question and answer related to unmet clothing needs from the PRAPARE questionnaire represented in LOINC.

An example of a screening response Observation that represents a question and answer related to employment status from the PRAPARE questionnaire represented in LOINC.

An example of a screening response Observation that represents a question and answer related to housing status from the PRAPARE questionnaire represented in LOINC.

An example of a Condition (a health concern) that is based on an Observation related to employment status that is derived from a QuestionnaireResponse to PRAPARE (represented in LOINC).

An example of a homelessness Condition (a health concern) that is based on an Observation related to housing status that is derived from a QuestionnaireResponse to PRAPARE (represented in LOINC).

Extension for flagging a HealthcareService.telecom as one the patient can use to make an appointment.

Extension for allowing the asserter of a condition to be Device (that was used to perform an operation to arrive at the condition).

Any resources referenced by ServiceRequest.supportingInfo

The value of any outputs of type ‘Reference’

Defines constraints that represent the minimum requirement for personal characteristic observations which are observations that are usually self-attested but may be attested to on behalf of the subject and are generally only verifiable by the source of attestation (e.g., race, ethnicity, sexual orientation, gender identity and personal pronouns), but may sometimes be verifiable by someone other than the source of attestation (e.g., recorded sex). This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for observations about the pronouns and possessive adjectives a person wishes to be addressed by. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for ethnicity observations that use Office of Management and Budget (OMB) ethnicity category codes and CDC ethnicity codes. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for race observations that use Office of Management and Budget (OMB) race category codes and CDC race codes. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for observations about “recorded sex and gender” which, in the past, were often used interchangeably. In this context, sex is a biological construct and pertains to a person’s genetics, hormones, and anatomy. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for observations about the sexual orientation of an individual. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37583. For further details on this profile see Draft Specifications for Personal Characteristics.

Profile for gender identity observations which are based on a person’s inner sense of being a girl/woman/female/feminine, boy/man/male/masculine, nonbinary, something else, or having no gender. This profile is intended for draft use only. The Cross-Group Projects work group granted a variance to US Core on 06/23/2022 - Jira ticket FHIR-37582. For further details on this profile see Draft Specifications for Personal Characteristics.

Codes for identifiers of target resources from which recorded sex or gender information can be derived.

Codes for the reason an observation does not have a value.

Codes that represent specific methods by which an individual’s race or ethnicity information can be elicited.

Codes for the ethnicity categories - ‘Hispanic or Latino’ and ‘Not Hispanic or Latino’ - as defined by the OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997. This value set was created (as opposed to using the US Core OMB Ethnicity Categories value set) to deliberately prevent inclusion of null flavors.

Codes for the five race categories - ‘American Indian’ or ‘Alaska Native’,’Asian’, ‘Black or African American’, ‘Native Hawaiian or Other Pacific Islander’, and ‘White’ - as defined by the OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997. This value set was created (as opposed to using the US Core OMB Race Categories value set) to deliberately prevent inclusion of null flavors.

Codes for the personal pronouns of an individual.

An example of an ethnicity Observation where the subject self-reports as Hispanic or Latino with detailed ethnicity information that highlights elements and repetitions.

An example of a gender identity Observation where the subject self-reports their gender identity as male.

An example of a personal pronoun Observation where the subject self-reports their pronoun preference.

An example of a race Observation that uses Observation.focus to make an Observation about the race of the subject’s mother (who is his caretaker).

An example of a race Observation where the subject self-reports as more than one race with detailed race information that highlights elements and repetitions.

An example of a race Observation that uses a FHIR extension on Observation.subject to make an Observation about the practitioner’s race.

An example of a recorded sex or gender Observation where a clinic has derived the designation M (male) from the subject’s driver’s license.

An example of a sexual orientation Observation where the subject self-reports as homosexual.

An example of a Related Person who is the mother of the subject/patient (Colin Abbas).