Condition.clinicalStatus clarification (of invariant con-3)

Background: See the commenter Description and the Background discussion for FHIR-35318 The general guidance section referenced by the commenter states ( with  the text in question highlighted ): For the US Core profiles, the following mandatory status elements with required binding have no appropriate “unknown” concept code: AllergyIntolerance.clinicalStatus * Condition.clinicalStatus * DocumentReference.status Immunization.status Goal.lifecycleStatus * The clinicalStatus element has the following constraints: SHALL be present if verification status is not entered-in-error and SHALL NOT be present if verification Status is entered-in-error. Reasoning: We agree with the commenter that the documentation regarding Condition.clinical status is incorrect and needs to be updated to reflect FHIR R4 constraints.   Proposed Changes: See Resolution Description for FHIR-35318 change  general guidance section as follows: from: For the US Core profiles, the following mandatory status elements with required binding have no appropriate “unknown” concept code: AllergyIntolerance.clinicalStatus * Condition.clinicalStatus * DocumentReference.status Immunization.status Goal.lifecycleStatus *The clinicalStatus element has the following constraints: SHALL be present if verification status is not entered-in-error and SHALL NOT be present if verification Status is entered-in-error. to: ( see colored text) For the US Core profiles, the following mandatory  or conditionally mandatory*  status elements with required binding have no appropriate “unknown” concept code: AllergyIntolerance.clinicalStatus * Condition.clinicalStatus * DocumentReference.status Immunization.status Goal.lifecycleStatus *The clinicalStatus element is conditionally mandatory based on resource specific constraints.