Keep the US Core CarePlan Profile, but remove the requirement for CarePlan.text and define a way to communicate the Assessment and Plan content within it (specific reference is TBD e.g., in CarePlan,supportingInfo, CarePlan.CarePlan.note, or CarePlan.activity.detail.reasonReference).

1.  remove the requirement for CarePlan.text - please remove any requirement that CarePlan.text is used only for Assessment and plan of treatment "note" in an EHR. 
2. define a way to communicate the Assessment and Plan content  - yes please. Note that documentation of Assessment and plan of treatment is not limited to "notes". Assessment and plan of treatment can be represented in as structured diagnosis/problems/health concerns/etc and plan of treatment can be structured "orderables/performables". I think doing an exercise similar to what was done for DiagnosticReport and DocumentReference Report Overlap is needed. This will assist in identifying when Assessment and plan of treatment "note" is needed (Using documentReference) and when structured data can be used for Assessment and plan of treatment workflow using CarePlan elements such as CarePlan.addresses; CarePlan.activity; etc.