Assessment and Plan of Treatment
Datasets
US Core 6.1.0 maps each USCDI data element onto a FHIR element.
| Dataset | US Core 6.1.0 target profile(s) |
|---|---|
care_plans | US Core CarePlan |
care_plans
One row per care plan. This dataset carries the Assessment and Plan of Treatment narrative; the SDOH Assessment element of the same class comes from clinical_observations.
| Column | Required | Format / values | Example |
|---|---|---|---|
record_id | Yes | your stable key for this care plan | CP-0001 |
patient_identifier | Yes | patient key | MRN-4471903 |
narrative_text | Yes | text or HTML; the assessment and plan itself | Assessment: … Plan: … |
status | Yes | draft, active, on-hold, revoked, completed, entered-in-error, unknown request-status | active |
intent | Yes | proposal, plan, order, option care-plan-intent | plan |
period_start | If available | datetime | 2026-04-18 |
period_end | If available | datetime | |
is_deleted | If retracting | true retracts this row | true |
narrative_textis the payload of this dataset, not a summary of it. US Core must-supports the narrative and requirestext.divwhenevertextis present, so a row without it produces a CarePlan with nothing to read. Send the assessment and the plan as your source holds them; HTML is preserved, plain text is wrapped.- Payerbox sets the
assess-plancategory and the narrative status on every row. Both are fixed by the profile, so there is nothing for you to send. statusandintentare required bindings, so a value outside these lists is rejected. A plan a payer holds is normallyactivewith intentplan.
These resources are served by Patient Access, Provider Access, Payer-to-Payer, and Prior Auth.