Parts of the definition for OBX-5 (Value Type) doesn't use the current ANSI modal verbs as recommended in section 2.2.1. Recommend we edit as follows starting with the third paragraph.

For example, if the value is 'CWE' then the result in OBX-5 mustSHALL be a coded entry or text or both. As of v 2.7, the ST data type may notSHALL NOT be used to transmit data that can be more precisely transmitted using other data types, e.g. SN when comparative symbols are needed.
The RP value (reference pointer) mustSHALL be used if the OBX-5 contains a pointer to the data e.g., a URL of an image. The receiving system canMAY use this reference pointer whenever it needs access to the actual data through other interface standards, e.g., DICOM, or through appropriate data base servers.
The structured numeric (SN) data type provides for reporting ranges (e.g., 3-5 or 10-20), titres (e.g., 1:10), and out-of-range indicators (e.g., >50) in a structured and computer-interpretable way.
We allow theThe FT data type SHOULD NOT be used in the OBX segment-, but its use is discouraged-. Formatted text usually implies a meaningful structure, e.g., a list of three independent diagnoses reported on different lines. But ideally, the structure in three independent diagnostic statements would be reported as three separate OBX segments.
TX should notSHOULD NOT be used except to send large amounts of text. In the TX data type, the repeat delimiter can only be used to identify paragraph breaks. Use ST to send short, and possibly encodable, text strings.
CDA documents SHALLare to be exchanged in the OBX segment in any message that can exchange documents (such as MDM or ORU). Within the OBX segment, the MIME package SHALL beis encoded as an encapsulated (ED) data type.