Goals
Datasets
US Core 6.1.0 maps each USCDI data element onto a FHIR element.
| Dataset | US Core 6.1.0 target profile(s) |
|---|---|
goals | US Core Goal |
goals
One row per goal per patient.
| Column | Required | Format / values | Example |
|---|---|---|---|
record_id | Yes | your stable key for this goal | GL-0001 |
patient_identifier | Yes | patient key | MRN-4471903 |
lifecycle_status | Yes | proposed, planned, accepted, active, on-hold, completed, cancelled, entered-in-error, rejected goal-status | active |
description_code | Yes | SNOMED CT or LOINC code, with description_system; or plain text us-core-goal-description | 289169006 exercising to lose weight |
start_date | If available | date | 2026-04-18 |
target_date | If available | date | 2026-10-18 |
is_deleted | If retracting | true retracts this row | true |
description_codeis the one field with no fallback: a row without it cannot become a Goal. Send a SNOMED CT code (description_system=http://snomed.info/sct) or a LOINC code (description_system=http://loinc.org); the binding's own value set spans essentially all of SNOMED CT, and LOINC comes in through its extensibility. A source that records goals only as narrative may put the text itself indescription_codeand leavedescription_systemempty.lifecycle_statusmarks each row:activefor a goal being pursued,completed/cancelled/rejectedfor closed ones,entered-in-errorto retract a record that should never have existed.target_dateis the USCDI "Goal Target Date". US Core requires supporting at least one ofGoal.startDateandGoal.target.dueDate, so send whichever your source tracks — either or both are fine.
These resources are served by Patient Access, Provider Access, Payer-to-Payer, and Prior Auth.