USCDI Structure Docs
Browse USCDI classes against actual FHIR R4 structures, profile requirements, and eClinicalWorks support patterns.
Clinical Data Classes
Choose a class on the left and browse the full structure on the right.
Problems and Conditions Structure
Condition is split into profile families for longitudinal problems and health concerns versus encounter-specific diagnoses.
Problem List and Health Concerns
Use this profile for active problem list items and broader health concern tracking.
Key Fields
| Field | Card. | Type | Requirement | Description |
|---|---|---|---|---|
| Condition.category | 1..* | CodeableConcept | Mandatory | Carries the problem-list-item or health-concern classification. |
| Condition.code | 1..1 | CodeableConcept | Mandatory | The diagnosis/problem/concern itself. |
| Condition.subject | 1..1 | Reference(Patient) | Mandatory | The patient whose chart holds the problem. |
| Condition.clinicalStatus | 0..1 | CodeableConcept | Must Support | Active, inactive, remission, or resolved. |
| Condition.onset[x] | 0..1 | choice | Must Support | Estimated or actual onset. |
| Condition.recordedDate | 0..1 | dateTime | Must Support | When the condition record entered the chart. |
| Condition.recorder | 0..1 | Reference | Additional USCDI | Who recorded the condition record. |
Relationships
| Path | References | Why It Matters |
|---|---|---|
| Condition.subject | Patient | The patient record. |
| Condition.recorder | Practitioner | PractitionerRole | Patient | RelatedPerson | Who recorded the data. |
Representative JSON Shape
{
"resourceType": "Condition",
"id": "problem-example",
"category": [
{
"text": "problem-list-item"
}
],
"code": {
"text": "Type 2 diabetes mellitus"
},
"subject": {
"reference": "Patient/patient-example"
},
"clinicalStatus": {
"text": "active"
},
"recordedDate": "2024-10-14T10:00:00Z"
}Encounter Diagnosis
Encounter diagnosis records a condition in the context of a specific visit or encounter.
Key Fields
| Field | Card. | Type | Requirement | Description |
|---|---|---|---|---|
| Condition.category | 1..* | CodeableConcept | Mandatory | Must be categorized as encounter-diagnosis. |
| Condition.code | 1..1 | CodeableConcept | Mandatory | The diagnosis captured for the encounter. |
| Condition.subject | 1..1 | Reference(Patient) | Mandatory | The patient. |
| Condition.encounter | 0..1 | Reference(Encounter) | Must Support | The visit or encounter context. |
| Condition.recordedDate | 0..1 | dateTime | Must Support | When the diagnosis was first recorded. |
| Condition.recorder | 0..1 | Reference | Additional USCDI | Who recorded the encounter diagnosis. |
Relationships
| Path | References | Why It Matters |
|---|---|---|
| Condition.encounter | Encounter | The visit that produced the diagnosis. |
| Condition.subject | Patient | The chart owner. |
Representative JSON Shape
{
"resourceType": "Condition",
"id": "encounter-diagnosis-example",
"category": [
{
"text": "encounter-diagnosis"
}
],
"code": {
"text": "Acute sinusitis"
},
"subject": {
"reference": "Patient/patient-example"
},
"encounter": {
"reference": "Encounter/encounter-example"
}
}Canonical Sources
These links are the standards baseline for this page. The local docs summarize them, but the official profile and resource pages remain the source of truth.
eCW Resource Support
| Resource | USCDI Support | Search Params | Description |
|---|---|---|---|
| Condition | v1 + v3 | _id, patient, clinical-status, code, onset-date, category | Detailed information about conditions, problems, or diagnoses |
Interpret support carefully
These pages separate three different ideas on purpose: the official ONC USCDI data element list, the US Core profile constraints that explain the actual field structure, and the eCW implementation notes that explain what you can realistically expect to fetch today.