Document Sample
HTML-Guide Powered By Docstoc
					HTML Form Standarization Guide

                    HTML Form Standardization Guide
Purpose: This guide is meant to help understand and show the functionality of the new
techniques used to standardize HTML form development for the UNI/CARE Pro-Filer™
system. Knowledge of the HTML and VBScript languages are expected.

Topics covered in this guide:

Directory Structure .......................................................................................................... 2
UNI/CARE supplied VBScript and CSS files .................................................................... 3
Control Naming Methods ................................................................................................. 7
Pop-up Datepicker .......................................................................................................... 8
Accessing data sent to HTML form.................................................................................. 9
General Form Validation and Input Restriction ................................................................ 9
Custom Form Validation ................................................................................................ 10
Form Versioning ............................................................................................................ 10
Spell Check Options ...................................................................................................... 11
Signature Control .......................................................................................................... 11
Clean Printing................................................................................................................ 12
Print as Report .............................................................................................................. 12
Appendix A: Standard Pro-Filer HTML Parameters ................................................. 14

Supplied Materials:
   - Zip file containing folder structure, style sheets, calendar script and USI VBScript
      library, HTML Template and Sample files.

UNI/CARE STATE REPORTING                                              3/22/2011                                PAGE 1 OF 15
HTML Form Standarization Guide

Directory Structure

To best utilized reusable files, a defined directory structure that is simple and easily
replicated is a must. This defined directory structure makes for effortless distribution of
new and updated forms packages and allows the customer to better manage these files.

The suggested directory structure is as follows:

             <root folder where all UDD forms will be stored>
                  Scripts (folder to contain reusable scripts)
                           usiUDD.vbs
                           calendar.js
                  Styles (folder to contain reusable style sheets)
                           Uddstyles.css
                           Uddprintstyles.css
                           Calendar.css
                     Img (folder to contain all images used in forms)
                     HTML Forms (all HTML forms)
             As seen in Image 1

[Image 1 – Directory structure; manages reusable scripts, styles, and images in separate folders]

With this structure, all HTML files would be placed in the primary <root> folder. To
use the scripts and styles in this directory in HTML forms, simply add the following
inside the <HEAD> section of the file.

<!--Display Style-->
<link rel="stylesheet" type="text/css" href="styles/uddstyles.css" media="screen" title="general"/>
<!--Print Style-->
<link rel="stylesheet" type="text/css" href="styles/uddprintstyles.css" media="print" title="print" />
<!--Calendar Style-->
<link rel="stylesheet" type="text/css" media="all" href="styles/calendar.css" title="cal2" />
<!--Calendar control-->
<script type="text/javascript" src="scripts/calendar.js" language="javascript"></script>
<!--Unicare Functions-->
<script type="text/vbscript" src="scripts/usiudd.vbs" language="vbscript"></script>
The files listed here are covered in the following section "UNI/CARE supplied
VBScript and CSS files”.

UNI/CARE STATE REPORTING                                                                3/22/2011   PAGE 2 OF 15
HTML Form Standarization Guide

UNI/CARE supplied VBScript and CSS files

In an effort to reduce the time required to produce a functional HTML form to work well
with Pro-Filer, UNI/CARE is supplying standardized HTML template, script and style
sheets that give all HTML forms the necessary routines to save, load, and provide
simple validation of form data. These standard files include:

usi_UDD_Template_2008_1.htm: HTML Template that gives needed structure and
allows for designer to focus on presentation elements. Form has above mentioned file
links included; startup, save, and versioning routines with defined areas to add form
specific code; cluster of buttons to draft save, final save, print, reset, and close form; and
form disclaimer. By simply adding desired fields and layout, you will have a functional
form that can be used within the Pro-Filer™ system.

usiUDD.vbs: VBScript file that contains all necessary functions and procedures to load,
save, and validate a form. This file also contains other handy functions and procedures
that can be used to ease the development of HTML forms and extend functionality.

calendar.js: Provides designer with a pop-up calendar for use in HTML forms. More
detail can be found in the section “Pop-up Calendar Date Picker control”.

calendar.css: Providers necessary styles applied to calendar control for consistent
visual appearance.

uddstyles.css: Style sheet to keep visual appearance of all HTML forms consistent with
minimal effort by designer. Designer simply assigns predefined class attributes to HTML
elements as desired.

uddprintstyle.css: Print specific style sheet that allows designer to add elements to a
form that will not be on a printed version and strips out darkened areas of a form from
classes defined in the uddstyles.css style sheet for those print cost conscious

Special consideration must be taken when assigning functions and routines to HTML
element events since page contains VBScript and JavaScript. Designer must enter
“vbscript:” or “javascript:” prefixes to the function/routine name to prevent errors when
event is fired.

Content of usiUDD.vbs

The usiUDD.vbs file contains all necessary functions and routines to load, save, and
validate a form. This file also contains functions and procedures that can be used to
restrict the type of data (numeric, decimal, date, alpha, etc.) entered into text fields and
verify that data is entered in a specified format and a spell checker. A list of all current
functions and routines in the library are listed below with a description of their

UNI/CARE STATE REPORTING                           3/22/2011                     PAGE 3 OF 15
HTML Form Standarization Guide

Load functions and procedures:

    -   SetValues - Autoloader routine. Walks elements in DOM and attempts to match
        key/value pair in g_inputdata string with elements within the form. Design of this
        routine allows it to be used with forms designed with any of the 3 parsing types
        available (No type and No number, Type and No Number, and Type and

    -   SaveData – Autosaver routine. Makes use of another routine called
        GatherElements that Walks DOM picking out Input type form elements and loads
        them into an array. Array is then parsed in SaveData routine building
        g_OutputData using the AddToOutputStr routine.

    -   GatherElements – parses document.forms(0).elements and builds array of input
        type elements. By adding the attribute [nosave=”true”] to any form element will
        cause this function to skip the element and prevent it from being saved.

    -   AddToOutputStr – adds key and value parameters to g_outputdata.

    -   PutInQuotes – wraps passed value in quotes.

    -   SetSeparator – Receives either “Data” or “USI” parameters and sets the
        appropriate separator to the requested variable. Data = “@@”    USI=”|”

    -   GetValueOf – returns the value assoiciated with the requested key from the
        g_inputdata variable.

    -   GetCustomArgsList – Parses strArgs variable into 3 arrays;
        arrArgNamesWithData which is then split into arrArgNamesOnly that contains the
        name of the custom arguments, and arrArgDataOnly that contains the data of the
        custom arguments. Also replaces all escaped characters in the stored

    -   ParseCustomArgToArray – creates an array from a multi-row custom arg.
        Uses supplied row delimiter and field delimiter to parse values
                Default Row Delimiter: ^
                Default Field Delimiter: ~
        Loads following variables that can be used to run other functions/routines (i.e.
            o numRows – total rows (dimension 1) in array
            o numCols – total columns (dimension 2) in array
            o arrTable – multi-dimensional array of values

    -   BuildList – uses variables loaded in ParseCustomArgToArray routine to build an
        option list for supplied <select> element (by id). Also accepts 2nd parameter to
        set as selected option.

    -   GetAge – Returns USI_CLIENT_AGE value. Can be run at any time as
        separator is set to USI separator and then returned to previous once complete.

UNI/CARE STATE REPORTING                          3/22/2011                    PAGE 4 OF 15
HTML Form Standarization Guide

    -   ParseCustomArgToString – Returns value of a custom argument to a string
        variable. Accepts 3 parameters, 1st- key, 2nd- Row Delimiter, 3rd- Field Delimiter.

    -   RadioValue – Returns value of checked radio button from supplied element ID.
        If no radio button is checked, returns “-1”.

    -   IIF – gives VBScript same function as VBA. Accepts 3 parameters; 1st condition
        to be evaluated, 2nd. Value to return if true, 3rd. Value to return if false.

    -   Validate_Form – Auto-validation routine. By assigning a custom attributes to
        HTML input elements, routine validates these elements on save and builds error
        message string with appropriate message. Routine is used for required/not
        required validation and is not meant to be used for value validation. More on this
        routine in section “General Form Validation”

    -   Validate_Mask – Input mask for HTML. Routine assigned to run on elements
        onBlur event. Looks for custom attribute “editmask” and for predefined formats.
        Validation prevents user from leaving field until values is removed or corrected.
        Current mask formats:
            o MMYYYY – month year date format with no separator
            o HH:MM – time format
            o YYYY – Year check
            o Date – date format (mm/dd/yyyy)
            o User Defined Regular Expression

    -   BuildMSG – Accepts 1 parameters of a string that is appended to the variable
        emsg. Save and close routine can display this variable if validation fails to give
        full list off errors on form.

    -   Key_Filter – Restricts field input to limited range of characters. Routine is
        assigned to elements onKeyPress event and looks for custom attribute
        “inputtype”. Current InputTypes:
            o Numeric – allows only characters 0 – 9
            o Decimal – allows only characters 0 – 9 and 1 decimal character (.)
            o Date – allows only characters 0 – 9 and 2 forward slash characters (/)
            o Alpha – allows only a – Z, [space], comma (,), hyphen (-) and apostrophe
        Routine also looks for a custom attribute of altinput that accepts a comma
        delimited string of characters outside the above inputtypes that will also be
        allowed in the field.

        In addition this routine can apply a maxlength to a <textarea> element by adding
        the attribute maxlength=”?” with the length desired and assigning this routine to
        the onKeyPress event.

    -   GetVersion – sets the getversion variable to the current form and vbscript library

    -   Win_Cancel – Assigned to onClick event of forms Cancel button.

UNI/CARE STATE REPORTING                          3/22/2011                    PAGE 5 OF 15
HTML Form Standarization Guide

    -   Window_OnBeforeUnload – Checks for use of form button and displays proper
        use message if form closed by other means. Restores original IE Header/Footer,
        page margins, and background color/images print settings if CleanPrint function

    -   EnableSpellCheck – Passed either True or False argument. Turns on/off button
        on form in standard template. Makes use of PolarSpellCheck.

    -   USI_Version_Control_Check – Passed the minimum version of the
        USIUDD.VBS file. Verifies that version of script file has minimum necessary
        methods and functions for form to work correctly.

    -   LPAD – Arguments: 1)string to pad, 2)character to pad string with, and 3) length
        of result. Adds leading characters to string and returns a string the length

    -   RPAD – Same as LPAD except adds trailing characters.

    -   AlertField – Accepts 2 parameters (Element, TRUE/FALSE). Marks field with
        red background if fails during Validate_Form method. Can also be used in
        extended validation during the VandC routine in the HTML form.

    -   LoadSigCtrl - Creates ePad signature control on HTML form. When reloading
        form that has been signed, will automatically redisplay signature and disable
        capture and clear buttons.
        1. CNTR - Container ID where control will be created.
        2. StoreIn - Number of 751+ to define CAD column to store signature data.
        3. PrintName - Name or label to be displayed below control (can be blank)
        4. NameFld - Number of <749 to define CAD column where PrintName value will
        be stored (can be blank)
        5. PrintDate - Value to appear on right side below signature control (can be
        6. DateFld - Number of <749 to define CAD column where PrintDate value will
        be stored (can be blank)
        7. B_Footer - Boolean value to display PrintName and PrintDate values below
        signature control.

    -   CleanPrint - Used to remove Internet Explorer Header and Footer, reduce page
        margin to 0.25", and enable "Print Background Color and Images". Calls
        Window.Print command after settings have been modified. Stores current
        settings for these items and sets b_IE_Was_Cleaned variable to TRUE.

    -   SpellChecker - Assigned to a form button. Scans form for fields with an attribute
        spellcheck="true". Makes use of MS Word Automation. MS Word is required to
        use this function.

    -   Window_OnBeforePrint - Shift content from input element to container
        elements for printing.

UNI/CARE STATE REPORTING                        3/22/2011                    PAGE 6 OF 15
HTML Form Standarization Guide

Control Naming Methods

Pro-Filer offers 3 control naming methods for HTML.
   1. No Type or Number – Controls will have just a general name and ID. This
        method give little to no control to the form designer on how the data is saved to
        the database.
        Example: <input type=”text” name=”TextboxA” id=”TextboxA” value=”” />

    2. Type and No Number – Controls are given a name beginning with “T_” or “S_” for
       fields that contain less than 255 characters and “M_” or “L_” for fields that can
       contain more than 255 characters. Controls typically given “T_” or “S_” types are
       Textboxes, Radio buttons, Checkboxes, Hidden, and Select list. Controls
       typically given “M_” or “L_” types are Textarea boxes. This naming and parsing
       method give a little more control on which columns data is written to in the
        Example: <input type=”text” name=”T_TextboxA” id=”T_TextboxA” value=”” />

    3. Type and Number – Controls are given the same beginning as option 2 but
       include a number. This number will coincide with the CAD columns in the
       User_Defined_Data and Client_Assessment tables in the database. This naming
       and parsing method gives complete control to the designer on where data is
       written into the database. This is the method used in all UNI/Care designed
       forms and is the recommended method of design. Any HTML form that will be
       used in conjunction with a report needs to use this method to ensure consistent
       function of the report. As in the example, the contents of this field will be written
       to CAD2 of either the User_Defined_Data or Client_Assessment tables
       depending on configuration. The number is not required to be 3 digits. At
       minimum control name just contain “Type_Number_”.
        Example: <input type=”text” name=”T_002_TextboxA” id=”T_002” value=”” />

UNI/CARE STATE REPORTING                          3/22/2011                     PAGE 7 OF 15
HTML Form Standarization Guide

Pop-up Datepicker

With the inclusion of the Calendar.js and Calendar.css file a pop-up calendar datepicker
is available. To add this control, create a text field and add the following immediately
<a onclick="javascript:displayDatePicker('<field name>', false, 'mdy', '/');" class="btndown">6</a>
1st parameter is the name of the field you want the date returned to. (case sensitive)
2nd parameter must always be false.
3rd parameter is format to return date. m = month; d = day; y = year. This format can
be in any combination.
4th parameter is date separator. If left out, no separator is used. Any character can be
used as a separator.

Resulting control       

Calendar control open 

This calendar control also has a built-in call to a function or sub routine called
“datePickerClosed”. You can create a function in your vbscript with this name that
accepts 1 argument because the calendar script will send a reference to the linked
control to this routine (i.e. Sub datePickerClosed(byval e)). In this routine, you can
create any additional checks or calls to other functions based on a date field being set.
In addition, because the linked control is sent, you can have different date controls
perform different action when they are set.

UNI/CARE STATE REPORTING                                    3/22/2011                          PAGE 8 OF 15
HTML Form Standarization Guide

Accessing data sent to HTML form

During the Startup routine of any HTML form, it is often necessary to access parameters
sent to the form through the “window.dialogargument”. Using the command
“GetValueOf(<parameter name>), variables and field elements can be assigned the
value of the requested parameter. To distinguish between Pro-Filer supplied data and
form data, a separator must be set. All Pro-Filer supplied data is separated by the pipe
(|) character. The default form data separator is a double at (@@) symbol. These can
be set using the command “SetSepartor(“USI”)” or “SetSeparator(“DATA”)”.

General Form Validation and Input Restriction

Included in the script library are 3 methods used to validate user input and/or restrict
user input to limited characters; key_filter, validate_mask, and validate_form.

Key_Filter is assigned to an elements OnKeyPress event
(onkeypress=”vbscript:key_filter”) . Event will look for an attribute of “inputtype” with a
value listed above. Event will also check for an attribute of “altinput” that contains a
comma delimited string of additional characters allowed.

Validate_Mask is assigned to an elements OnBlur event
(onblur=”vbscript:Validate_Mask”). This event looks for an attribute of “editmask” with a
value listed above. If the validation fails, the event will look for an attribute of "maskerr"
that contains a more descriptive error message (very useful when validating regular

Validate_Form is run during the Form Save routine. Event looks for all elements that
have an attribute of:
       Required=”true” – checks if field has a value or selected index is not 0
       Required-if=”condition” – if condition is true does field have a value or selected
index not 0
       Required-array=”string of pipe delimited ids” – does at least one of these fields
have a value or is checked
       Required-array-if=”condition~string of pipe delimited ids” – if condition is true,
does at least one of these fields have a value or is checked.

At the time the validation attribute fails, the event looks for the attribute “errormsg” that
contains a string telling the user what‟s expected. The Validate_Form routine is meant
as a way to require fields and not to validate content. Content and format validation not
done by the Validate_Mask and/or Key_filter will still need to be coded manually.

UNI/CARE STATE REPORTING                           3/22/2011                      PAGE 9 OF 15
HTML Form Standarization Guide

Custom Form Validation

For validating field content that goes beyond the methods described above, add needed
VBScript code to the VandC subroutine between the following lines:
        'Form specific validation that could not be handled by General validation rules/methods
        <your code will go here>
        'Finalize, show errors if any or save the form

Custom form validation can make use of 2 functions included in the VBScript library.
   1. BuildMSG - Used to build an error message string that will be displayed on save.
   2. AlertField - Marks field that failed validation with red background or turns marking

Examples of possible custom form validation:
      Date field cannot be in the future:
                 Example assumes field has been restricted to date input.
                 if form.datefield.value <> "" then
                           if cdate(form.datefield.value) > date then
                                     buildmsg "INVALID: Date cannot be in future"
                                     alertfield form.datefield, true
                                     alertfield form.datefield, false
                           end if
                 end if

        Value set in dropdown1 limits valid selection in dropdown2.
                 if form.dropdown1.value = "A" then
                            If instr("ABC",form.dropdown2.value) = 0 then
                                      buildmsg "INVALID: Field 2 must be A, B, or C when Field 1 is A"
                                      alertfield form.dropdown2, true
                                      alertfield form.dropdown2, false
                            end if
                 End if

Form Versioning

It is standard practice by UNI/CARE to track form versions to ensure the latest version is
being used and to keep track of expected behavior at different versions. The UNI/CARE
versioning method is using the current date in y.m.d format and to add an instance
number to the end (ie. 2009.02.12.1 would indicate for was completed/edited on
2/12/2009 and this is the first change made that day.) In addition to the form version, the
script library is versioned. Setting the variable “Version” to the form version, the
developer can call the function GetVersion that will combine the form version and script
version to be displayed in a message box or anywhere else on the form. Standard
practice at UNI/CARE is to include this GetVersion string in the document.title property.

UNI/CARE STATE REPORTING                                  3/22/2011                          PAGE 10 OF 15
HTML Form Standarization Guide

Spell Check Options

Script Library contains 2 methods of providing Spell Check to an HTML form. Both
methods rely on a custom attribute spellcheck with a value of true (i.e.,
spellcheck="true"). With either method, ONLY fields with this attribute will have its
content checked. The 2 options available are described below.

Option 1: MS Word

        eForm will use MS Word Automation. MS Word is REQUIRED for this option.
        During the process, the content of each form field with the attribute described
        above will be sent to a MS Word document and the MS Word spell check
        function is fired. If items are found, MS Word will display dialog for correction.
        Once complete, content is sent back to form and process continued until all fields
        have been completed.

Option 2: PolarSpellCheck

        eForm will use PolarSpellCheck controls built into Pro-Filer and is built into new
        HTML Templates. To enable the method “EnableSpellCheck True” is called
        during the StartUp routine. This enables the Spell Check button on the form.
        During the Spellcheck process, if the field being checked has misspelled words
        according to the PolarSpellCheck dictionaries, a dialog will appear showing the
        content of the field and the misspelled words highlighted. Instructions are
        provided in the dialog to assist the user with correcting these words.

Signature Control

Using the function "LoadSigCtrl" and passing values for all arguments will create a
functional signature capture control on any eForm. When developing the form, designer
will specify the location of the control by creating an empty <DIV> or <SPAN> container
and assigning a value to the ID attribute (i.e., <DIV id="client_sig"></DIV>). During the
StartUp routine, after setting the g_separator to the form data separator (g_separator =
SetSeparator("DATA")), designer can call "LoadSigCtrl" to add the control to the
designated location. Arguments for this function are defined in the Content of
usiUDD.vbs section of this document.

LoadSigCtrl container, signature data field, printed name/label (left), printed name/label
data field, printed date/label (right), printed date/label data field, display printed values

LoadSigCtrl client_sig, "751","Client Signature","700",Date,"701",True

With the above command, a signature control is created inside the <DIV> or <SPAN>
container with an ID of "Client_Sig", a hidden element will be created with a name of
"M_751_" to store signature data upon save, a label of "Client Signature" will be created
to appear on the left below the control and this value will be stored in a hidden element
created with a name of "T_700_", a label with the current date will be created to appear
on the right below the control and this value will be stored in a hidden element created
with a name of "T_701_". With a final argument of TRUE, both the printed name/label

UNI/CARE STATE REPORTING                           3/22/2011                     PAGE 11 OF 15
HTML Form Standarization Guide

(left) and printed date/label (right) will be displayed on the form. See Signature Control
Sample for more examples.

The default size of the signature control is 260px wide by 80px high. The designer can
override these settings by assigning their own values to "USI_Sig_Ctrl_Width" and
"USI_Sig_Ctrl_Height" variables. These variables can be assigned once for all controls
needed on a form or prior to calling the LoadSigCtrl function for each control being
created to give each a different size. If the default size is desired, to not use these
variables in your form.

Clean Printing

Since Pro-Filer uses an Internet Explorer object to display eForms within the Pro-Filer
interface, any time a form is printed, the settings in Internet Explorer are used. By
default, this means the form Title will appear in the top left corner, a page number in the
top right corner, the URL in the bottom left and date in the bottom right corners. In
addition to Internet Explorer has turned off the printing of background colors and images.
To improve the quality of a printed eForm, a method called "CleanPrint" was created.
This method removes the Internet Explorer header and footer, enables printing of
background colors and images, and adjusts the page margins prior to calling the
window.print command that will display the print dialog. To ensure that none of these
settings are lost, the original values are held temporarily and are restored when the form
is closed.

Print as Report

Often a eForm will need to be printed in such a way that it appears to be a report. This
would include displaying all data entered into textboxes and textarea fields as well as not
printing items such as buttons and calendar controls. In addition there may be items
such as images, headers, footers, or instructions that a printed version would need to
have that are not wanted on the display.

Using the stylesheets included with the templates, this is possible. UDDstyles.css
contains classes for displaying items on screen while the UDDPrintStyles.css contains
classes for printing. The two primary classes for controlling printing are "noscreen" and
"noprint". Example, by giving an image a class of "noscreen" will prevent the image form
appearing while displayed by Pro-Filer but will allow the image to appear when the
eForm is printed. The class "noprint" does the exact opposite. It allows an element to
be shown on screen but prevents it from appearing on a printed version. These classes
can be applied to any HTML element.

When printing an eForm where textbox and textarea content must be displayed in full,
the use of <span> and <div> tags can be used to shift the content prior to printing.

<textarea name="M_751_" id="M_751" class="noprint" cols="50"
rows="3"></textarea><div class="noscreen" id="d751"></div>

UNI/CARE STATE REPORTING                         3/22/2011                    PAGE 12 OF 15
HTML Form Standarization Guide

The example above will display a textarea field with 50 columns and 3 rows on screen.
This element will not be printed. The div container will not be shown on the screen but
will print with the content of the textarea.

The technique is to create the <span> or <div> container directly following the input
element it will replace in a printed version. The ID attribute of the container will be
"s###" for all elements with less than 255 characters (all fields that will be stored in
CAD1-750) and "d###" for all elements with more than 255 characters (all fields that will
be stored in CAD751-950) where "###" in both IDs is the number assigned to the input
element as shown in the example above. In addition by assigning the appropriate class
of "noprint" to the onscreen element and "noscreen" to the print element, the shift of
contents is not seen by the user.

The shift of the content will happen automatically when the usiudd.vbs script library is
attached to the eForm by use of the Window_OnBeforePrint event. This event will fire
with all eForms and only make changes where it finds the rules above

UNI/CARE STATE REPORTING                         3/22/2011                   PAGE 13 OF 15
HTML Form Standarization Guide

Appendix A: Standard Pro-Filer HTML Parameters

Available to all UDD forms (even if all Parameter checkboxes are unchecked)

Parameter Name                                Definition
CURRENT_ACTIVE_OID                            OID of parent form record
USI_NEW_RECORD                                Value of 1 for True
SERVERNAME                                    Active SQL Server Name
DATABASENAME                                  Active Database Name
LOGGED_IN_USER_PROVIDER_OID                   Current Provider record OID
LOGGED_IN_USER_PROVIDER_DOMAIN                Users Login Domain
LOGGED_IN_USER_PROVIDER_USERNAME              Users Login Name

Situational Parameters (Availability determined by location)
Parameter Name                                 Location
                                               When form is opened from UDD button at bottom of
USER_DEFINED_DATA_OID                          Pro-Filer forms
CLIENT_ASSESSMENT_OID                          When form is opened from End User Assessment
USINEWLYCLONED                                 When form is cloned. Value of 1 for True.
USI_CLIENT_ASSESSMENT_PROVIDER                 End User Assessment
CLIENT_OID                                     Available at ALL levels of the Client Record
CLIENTAGENCY_OID                               Available from Client Agency down
EPISODE_OID                                    Available from Client Episode down
COSTCTRGRP_OID                                 Available from Cost Center Location down
TREATMENTPLAN_OID                              Available from Treatment Plan down

Parameters available by checkboxes on Assessment Form

Assessment (Basics)

Assessment Category

Assessment Type

Client (Basics)

Client Ethnicity

UNI/CARE STATE REPORTING                         3/22/2011                      PAGE 14 OF 15
HTML Form Standarization Guide

Client Race

Client Language

Client Gender

Client Address

Client Telephone

Logged in User (Basics)

Logged in User Type

UNI/CARE STATE REPORTING                 3/22/2011   PAGE 15 OF 15

Shared By: