User manual SAS CLINICAL STANDARDS TOOKIT 1.3

[. . . ] User's Guide SAS Clinical Standards Toolkit 1. 3 ® SAS® Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. SAS® Clinical Standards Toolkit 1. 3: User's Guide . SAS ® Clinical Standards Toolkit 1. 3: User's Guide Copyright © 2010, SAS Institute Inc. , Cary, NC, USA All rights reserved. Produced in the United States of America. [. . . ] T: What follows is a time in a 24-hour clock. Dates and Times: Full Datetime Examples 2009-03-25 March 25, 2009 Year must have four digits. Month, day, hour, minute, and second each must have two digits. Single-digit values must be preceded by a leading zero. Special Topic: SAS Implementation of ISO 8601 String Interpretation Comments 149 2009-03-25T22:29:30 March 25, 2009 10:29 and 30 seconds p. m. T is always required before a time. Times must always be in military time (for example, 24hour clock). The individual parts of a date value must be separated by a hyphen (-). The individual parts of a time value must be separated by a colon (:). 2009-03-25T22:29:30. 333+0 5:00 March 25, 2009 10:29 and 30. 333 seconds p. m. in the time zone GMT + 5 hours If provided, the time zone must be in HH:MM format. It cannot be truncated or a partial value. Some values in ISO 8601 formats can have decimal places. The decimal place can be denoted as either a period (. ) or a comma (, ). When a time zone is provided, it must be accompanied by a complete date. The date cannot be truncated or a partial value. This is necessary because the 24 global time zones force the date to be considered as part of the time. 2009-03-25T22:29Z March 25, 2009 10:29 p. m. Zulu time Z can be used to substitute for times in GMT (or Zulu) time. Dates and Times: Partial Datetime Examples (One or more components of the date or time are not known. Partial values are denoted by a single -, no matter how many digits are absent. Partial values can be expressed by truncating the missing parts. ) -----T22:29 The time 10:29 p. m. A time value must always be prefixed by a date value. In this example, the date value is completely missing, which would be appropriate for timeonly fields. Trailing values can be truncated when the values are missing. 2009 Year 2009. 150 Chapter 6 · Validation String Interpretation Comments 2009---25 The 25th day of an unknown month in the year 2009. The month is missing. If a missing value is embedded in the string, then it must always be denoted by a hyphen (-). Missing year. --03-25 The 25th day of March in an unknown year. [. . . ] No value in &_cstparm1 can be equal to any value in &_cstparm2. CRT0111 Content [ItemRangeChecks] [ItemRangeCheckValues] CRT0111 Content [MDVLeaf] [MDVLeafTitles] CRT0112 Content [CodeListItems] [ExternalCodeLists] [CodeListItems. FK_ CodeLists] [ExternalCodeLists. FK_ CodeLists] [DefineDocument. ID] [ItemGroupLeaf. ID] CRT0112 Content [DefineDocument] [ItemGroupLeaf] No value in &_cstparm1 can be equal to any value in &_cstparm2. No value in &_cstparm1 can be equal to any value in &_cstparm2. No value in &_cstparm1 can be equal to any value in &_cstparm2. CRT0112 Content [DefineDocument] [MDVLeaf] [DefineDocument. ID] [MDVLeaf. ID] CRT0112 Content [ExternalCodeLists] [CodeListItems] [ExternalCodeLists. FK_ CodeLists] [CodeListItems. FK_ CodeLists] [ItemGroupLeaf. ID] [DefineDocument. ID] CRT0112 Content [ItemGroupLeaf] [DefineDocument] No value in &_cstparm1 can be equal to any value in &_cstparm2. No value in &_cstparm1 can be equal to any value in &_cstparm2. CRT0112 Content [ItemGroupLeaf] [MDVLeaf] [ItemGroupLeaf. ID] [MDVLeaf. ID] Module ODM V1. 3. 0 (Run Time) checkid checktype tablescope columnscope messagetext 347 CRT0112 Content [MDVLeaf] [DefineDocument] [MDVLeaf. ID] [DefineDocument. ID] No value in &_cstparm1 can be equal to any value in &_cstparm2. [. . . ]