Multiple comments about the valueset-goal-status-reason

1) Per QA 4a, If defining a CodeableConcept, FHIR-specific codes must only be used when no external code systems apply (and should be verified for 80% if this occurs). http://wiki.hl7.org/index.php?title=DSTU_QA_Guidelines I question why we can't find external code systems that could be used instead of FHIR specific codes. For example, could FHIR code life-event be instead represented by SNOMED 365574009 | Finding of life event?

2) If we keep the FHIR value set, the code definitions are all in context of a goal, but the value set is shared with CarePlan.activity.detail.statusReason as well. Loosen up the definitions to be in context of either goal or activity.

3) If we keep the FHIR value set, per QA 4e, Also ensure all codes are mutually exclusive or are defined in a proper hierarchy where siblings are mutually exclusive - http://wiki.hl7.org/index.php?title=DSTU_QA_Guidelines - it seems there could be some overlap since permanent-not-attainable and temp-not-attainable can overlap with nearly all of the other codes (e.g. patient-request defined as "Patient wishes the goal to be set aside, at least temporarily" which could overlap with temp-not-attainable; other codes defined as "suspended or ended" where suspended would overlap with temp-not-attainable and ended would overlap with permanent-not-attainable)

4) If we keep the FHIR value set, permanent-not-attainable and temp-not-attainable don't sound like reasons to me because they don't explain why the goal or activity is no longer attainable