Conventions for displaying TEST data in this document are as follows: The first three digits (prefix) of any Social Security Numbers (SSN) begin with either “000” or “666”. Patient and user names are formatted as follows: <Application Name/Abbreviation/Namespace>PATIENT,<N> <Application Name/Abbreviation/Namespace>USER,<N> Where: is defined in the Approved Application <Application Name/Abbreviation/Namespace> Abbreviations document. represents the first name as a number spelled out and incremented with each new <N> entry. For example, in Kernel (DI or FM) test patient and user names would be documented as follows: FMPATIENT,ONE; FMPATIENT,TWO; FMPATIENT,THREE; … FMPATIENT,14; etc. FMUSER,ONE; FMUSER,TWO; FMUSER,THREE; FMUSER,14; etc. … of computer online displays (i.e., screen captures/dialogues) and computer source “Snapshots” code, if any, are shown in a font and enclosed within a box. non-proportional to online prompts are bold typeface and highlighted in yellow User’s responses (e.g., <Enter>). Emphasis within a dialogue box is bold typeface and highlighted in blue (e.g., STANDARD LISTENER: RUNNING). Some software code reserved/key words are bold typeface with alternate color font. References to within these snapshots indicate that the user should press the Enter “<Enter>” key on the keyboard. Other special keys are represented within < > angle brackets. For example, pressing the PF1 key can be represented as pressing <PF1>. are displayed in italics or as Author’s comments “callout” boxes. NOTE: Callout boxes refer to labels or descriptions usually enclosed within a box, which point to specific areas of a displayed image. All uppercase is reserved for the representation of M code, variable names, or the formal name of options, field/file names, and security keys (e.g., DIEXTRACT). NOTE: Other software code (e.g., Delphi/Pascal and Java) variable names and file/folder names can be written in lower or mixed case (e.g., CamelCase).
Conventions for displaying TEST data in this document are as follows: The first three digits (prefix) of any Social Security Numbers (SSN) begin with either “000” or “666”. Patient and user names are formatted as follows: <Application Name/Abbreviation/Namespace>PATIENT,<N> <Application Name/Abbreviation/Namespace>USER,<N> Where: <Application Name/Abbreviation/Namespace> is defined in the Approved Application Abbreviations document. <N> represents the first name as a number spelled out and incremented with each new entry. For example, in Kernel (DI or FM) test patient and user names would be documented as follows: FMPATIENT,ONE; FMPATIENT,TWO; FMPATIENT,THREE; … FMPATIENT,14; etc. FMUSER,ONE; FMUSER,TWO; FMUSER,THREE; … FMUSER,14; etc. “Snapshots” of computer online displays (i.e., screen captures/dialogues) and computer source code, if any, are shown in a non-proportional font and enclosed within a box. User’s responses to online prompts are bold typeface and highlighted in yellow (e.g., <Enter>). Emphasis within a dialogue box is bold typeface and highlighted in blue (e.g., STANDARD LISTENER: RUNNING). Some software code reserved/key words are bold typeface with alternate color font. References to “<Enter>” within these snapshots indicate that the user should press the Enter key on the keyboard. Other special keys are represented within < > angle brackets. For example, pressing the PF1 key can be represented as pressing <PF1>. Author’s comments are displayed in italics or as “callout” boxes. NOTE: Callout boxes refer to labels or descriptions usually enclosed within a box, which point to specific areas of a displayed image. All uppercase is reserved for the representation of M code, variable names, or the formal name of options, field/file names, and security keys (e.g., DIEXTRACT). NOTE: Other software code (e.g., Delphi/Pascal and Java) variable names and file/folder names can be written in lower or mixed case (e.g., CamelCase).
fm22_2um2.docx