Replace description of usage  Clinical scenarios include setting up procedures and interpreting results. For the procedure case, SFCU will be needed on the order, and it may be carried on subsequent descriptions of the procedure. Note that the order concept in CDA is referenced by the somewhat concise Order class, which, being in the header, does not support SFCU. More detailed descriptions of the Procedure or SubstanceAdministration in the body will support SFCU. Since documents are not typically used to place orders, this does not seem to present a problem.   To the following to describe the differences between document header structures and clinical statement structures   Clinical scenarios include setting up procedures and interpreting results. For the procedure case, SPCU will be needed on the order, and it may be carried on subsequent descriptions of the procedure.   An "Order" is represented in the body of CDA documents using most any of the Clinical Statement classes (Act, Procedure, Observation) and applying a moodCode of INT (Intent) or RQO (Request) and therefore can be used in the workflow of Sex Parameter for Clinical Use construct.   The Order Structure  in the document header, is to identify the order(s) (aka RQO or INT) for which the document itself provides information. For example , a Radiology report that is written in response to an Xray order. The Order Structure in the document header does not support entry relationships so the SPCU can not be documented for the whole document but must be documented   individually in the document body.