| Left: | US Core Condition Encounter Diagnosis Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis) |
| Right: | SDOHCC Condition (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-Condition) |
| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-Condition' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0-ballot' vs '2.1.0' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreConditionEncounterDiagnosisProfile' vs 'SDOHCCCondition' |
| Information | StructureDefinition.title | Values for title differ: 'US Core Condition Encounter Diagnosis Profile' vs 'SDOHCC Condition' |
| Information | StructureDefinition.status | Values for status differ: 'active' vs 'draft' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2024-03-21T14:07:32+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care' |
| Error | StructureDefinition.baseDefinition | Values for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Condition' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition' |
| Information | StructureDefinition.short | Values for short differ: 'Detailed information about conditions, problems or diagnoses' vs 'Detailed information about SDOH conditions, problems or diagnoses' |
| Information | StructureDefinition.definition | Values for definition differ: '\-' vs 'For representation of SDOH conditions.' |
| Information | StructureDefinition.comment | Values for comment differ: '\-' vs 'Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths (e.g., to arrive at SDOH Conditions) are also possible. One specific use for this profile is to represent a Health Concern that is either; 1) directly asserted based on the patient’s answer to a specific question from an SDOH screening questionnaire or 2) computed/generated based on the patient’s answers to multiple questions. The questions and answers from the screening questionnaire are also represented using SDC Questionnaire, SDC QuestionnaireResponse and SDOHCC Screening Response Observation.' |
| Information | StructureDefinition.comment | Values for comment differ: 'verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' vs 'verificationStatus is not required. For example, when a patient complains of stress during a provider encounter, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. For SDOH conditions that are autogenerated based on a questionnaire response, the Condition.asserter is a “Device” AND Condition.Category should be 'health-concern'. In that case, Condition.verificationStatus should be 'unconfirmed' and should be changed to “confirmed” only after review and concurrence by the provider and patient.' |
| Information | StructureDefinition.short | Values for short differ: 'category codes' vs 'problem-list-item | encounter-diagnosis | health-concern' |
| Information | StructureDefinition.requirements | Values for requirements differ: '0..1 to account for primarily narrative only resources.' vs 'Code is required and must be selected from the bound value set.' |
| Information | Condition.bodySite | Element maximum cardinalities differ: '2147483647' vs '0' |
| Information | StructureDefinition.definition | Values for definition differ: 'Indicates the patient or group who the condition record is associated with.' vs 'Indicates the patient who the condition record is associated with.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Group is typically used for veterinary or public health use cases.' vs 'US Core Condition Profile restricts subject to patient.' |
| Warning | Condition.encounter | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Estimated or actual date, date-time, or age' vs 'Estimated dateTime or Period' |
| Information | StructureDefinition.definition | Values for definition differ: 'Estimated or actual date or date-time the condition began, in the opinion of the clinician.' vs 'Estimated or actual dateTime or Period the condition began.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Age is generally used when the patient reports an age at which the Condition began to occur.' vs 'For SDOH conditions that have their onset over an extended (or fuzzy) period (e.g., the past month), Condition.onset may use a lower precision representation (e.g., month/year or year) as opposed to a higher precision representation (e.g., year/month/date/hour/min).' |
| Information | StructureDefinition.definition | Values for definition differ: 'The date or estimated date that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution' - Conditions are never really resolved, but they can abate.' vs 'The estimated or actual dateTime or Period that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution'.' |
| Information | StructureDefinition.comment | Values for comment differ: 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.' vs 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. For SDOH Conditions that have a fuzzy abatement period, a lower precision representation (e.g., month/year or year) may be used. However, for SDOH Conditions that end at a specific point in time (e.g., food insecurity may abate upon acquiring a new job or gaining eligibility to a food program) a higher precision representation (e.g., year/month/date) may also be used.' |
| Warning | Condition.recordedDate | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Person who asserts this condition' vs 'Person or device that asserts this condition' |
| Information | StructureDefinition.definition | Values for definition differ: 'Individual who is making the condition statement.' vs 'The individual or device making the condition statement.' |
| Warning | Condition.asserter | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Error | Condition.asserter | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole]]) |
| Information | Condition.stage | Element maximum cardinalities differ: '2147483647' vs '0' |
| Warning | Condition.evidence | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Condition | http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition |
|
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
| date | 2023-10-17 | 2024-03-21T14:07:32+00:00 |
|
| description | The US Core Condition Encounter Diagnosis Profile is based upon the core FHIR Condition Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 *Encounter Diagnosis* requirements. In version 5.0.0, The US Core Condition Profile has been split into the US Core Condition Encounter Diagnosis Profile and US Core Condition Problems and Health Concerns Profile. To promote interoperability and adoption through common implementation, this profile defines constraints and extensions on the Condition resource for the minimal set of data to record, search, and fetch information about an encounter diagnosis. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. | Profile for Social Determinants of Health (SDOH) conditions. |
|
| experimental | false |
| |
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreConditionEncounterDiagnosisProfile | SDOHCCCondition |
|
| publisher | HL7 International / Cross-Group Projects | HL7 International / Patient Care |
|
| purpose | |||
| status | active | draft |
|
| title | US Core Condition Encounter Diagnosis Profile | SDOHCC Condition |
|
| type | Condition | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis | http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-Condition |
|
| version | 7.0.0-ballot | 2.1.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Condition | C | 0..* | Condition | Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error | C | 0..* | USCoreCondition | Detailed information about SDOH conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error us-core-1: A code in Condition.category SHOULD be from US Core Condition Category Codes value set. SDOH-Con-1: Can only have a max of one asserter. | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 Slices for extension | 0..* | Extension | Extension Slice: Unordered, Open by value:url | 0..* | Extension | Extension Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | External Ids for this condition | Σ | 0..* | Identifier | External Ids for this condition | |||||||||
| clinicalStatus | ?!SΣC | 0..1 | CodeableConcept | active | recurrence | relapse | inactive | remission | resolved Binding: ?? (required) | ?!SΣC | 0..1 | CodeableConcept | active | recurrence | relapse | inactive | remission | resolved Binding: ?? (required) | |||||||||
| verificationStatus | ?!SΣC | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required) | ?!SΣC | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required) | |||||||||
| Slices for category | S | 1..* | CodeableConcept | category codes Slice: Unordered, Open by pattern:$this Binding: ?? (extensible): A category assigned to the condition. | SC | 1..* | CodeableConcept | problem-list-item | encounter-diagnosis | health-concern Slice: Unordered, Open by value:$this Binding: ?? (extensible) | |||||||||
| severity | 0..1 | CodeableConcept | Subjective severity of condition Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician. | 0..1 | CodeableConcept | Subjective severity of condition Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician. | |||||||||||
| code | SΣ | 1..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: ?? (extensible): Valueset to describe the actual problem experienced by the patient | SΣ | 1..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: ?? (required): Valueset to describe the actual problem experienced by the patient | |||||||||
| bodySite | Σ | 0..* | CodeableConcept | Anatomical location, if relevant Binding: ?? (example): Codes describing anatomical locations. May include laterality. | Σ | 0..0 |
| ||||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile S | Group) | Who has the condition? | SΣ | 1..1 | Reference(US Core Patient Profile) | Who has the condition? | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter created as part of | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
| ||||||||
| onset[x] | SΣ | 0..1 | dateTime S, Age, Period, Range, string | Estimated or actual date, date-time, or age | SΣ | 0..1 | dateTime, Period | Estimated dateTime or Period | |||||||||
| abatement[x] | SC | 0..1 | dateTime S, Age, Period, Range, string | When in resolution/remission | SC | 0..1 | dateTime, Period | When in resolution/remission | |||||||||
| recordedDate | SΣ | 0..1 | dateTime | Date record was first recorded | Σ | 0..1 | dateTime | Date record was first recorded |
| ||||||||
| recorder | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Who recorded the condition | Σ | 0..1 | Reference(Practitioner | PractitionerRole) | Who recorded the condition | |||||||||
| asserter | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Person who asserts this condition | SΣC | 0..1 | Reference(RelatedPerson | US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile) | Person or device that asserts this condition |
| ||||||||
 stage | C | 0..* | BackboneElement | Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment | C | 0..0 |
| ||||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| summary | C | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). | C | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). | |||||||||
| assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment | |||||||||
| type | 0..1 | CodeableConcept | Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). | 0..1 | CodeableConcept | Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). | |||||||||||
| evidence | C | 0..* | BackboneElement | Supporting evidence con-2: evidence SHALL have code or details | SC | 0..* | BackboneElement | Supporting evidence con-2: evidence SHALL have code or details |
| ||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| code | ΣC | 0..* | CodeableConcept | Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition. | ΣC | 0..* | CodeableConcept | Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition. | |||||||||
| detail | ΣC | 0..* | Reference(Resource) | Supporting information found elsewhere | ΣC | 0..* | Reference(Resource) | Supporting information found elsewhere Slice: Unordered, Open by profile:resolve() | |||||||||
| note | 0..* | Annotation | Additional information about the Condition | 0..* | Annotation | Additional information about the Condition | |||||||||||
| Documentation for this format | |||||||||||||||||