The words "vice versa" are incorrect. The correct statement is that any instance that conforms to the current profile also will conform to the FHIR profile. We disagree with the specific example provided by the voter, however. Child profiles can only add constraints to their parent profiles. Changing cardinality from 0..1 to 0..0 is permitted, but not the reverse. An mCODE-compliant resource that omits an element because the mCODE profile restricts it to 0..0 does indeed comply with its parent profile if the parent profile allows 0..1 occurrences of the element. Regardless, based on the approved ballot proposal in GF#24526, we will be eliminating the mCODE vital sign profiles, and instead, refer to the vital sign profiles provided in the base FHIR standard  (   http://hl7.org/fhir/bp.html   ). Proposed resolution: Persuasive with mod (delete profile)