Download:
pdf |
pdf]MCBS MAIN STUDY
R55 General Specifications for Blaise/WVS
Version 07.01.0001
8/14/2009
SCREEN TYPES
TABLE OF CONTENTS
1. WVS Page Layout for Questions
2. Screen Type specifications
* Specifications still in progress. Need to include
ADDRESS and PHONE screen types. May also add actual
WVS screen shots.
1. WVS PAGE LAYOUT FOR QUESTIONS
Each question is displayed as a separate “Page” in the WVS CAPI instrument. The
following describes the different elements of the WVS Page in the order the item appears
on the screen, from top to bottom.
1. Case Information Line
Displays case ID, item tag, block, field name, etc.
Currently, content defined by programming team.
2. System Functions
Displays System Options:
HELP
Invokes a pop-up window that displays additional
information to help interviewer administer question.
NOTE: No long implemented in MCBS WVS
instrument. Disregard HELP specifications.
COMMENTS
Invokes a pop-up window, allowing the interviewer to enter
a comment to data editing staff. Often used by interviewer
to alert data editing of a mistake that was made during data
collection.
NOTE: Default is to always display COMMENTs link
on each screen in MCBS WVS instrument. Disregard
COMMENTs specification. Should always be set
COMMENTS = YES.
JUMPBACK
Invokes a JUMPBACK menu, allowing the interviewer to
navigate back to a previous question.
NOTE: Not currently supported in MCBS WVS
instrument. Disregard JUMPBACK specifications.
DON’T KNOW
Invokes a “Don’t Know” response.
REFUSAL
Invokes a “Refusal” response.
3. Context Header Lines
Displays additional case information.
EX: Display reference period
Display Event Date
Can be multiple lines.
Default = ALL CAPS.
Is not read to respondent.
4. Interviewer Instructions I
Instruction to interviewer.
Typically used for “SHOW CARD” instructions.
Default = ALL CAPS.
Is not read to respondent.
5. Report
Displays a list of related items that may be read to the respondent as part of
question.
EX: List of plans that the SP was covered by at the time of the previous round
interview.
List of Persons living in the household.
Can display multiple rows and columns.
Can display report and column headers.
List will scroll if # lines exceed display area.
Report cannot be updated by interviewer.
Report can be displayed above or below question text.
One report per screen.
6. Question Text
Question text read to respondent.
7. Report
Alternate location for Report.
* See Report Notes above.
8. Interviewer Instructions II
Instruction to interviewer.
Typically used for screen instructions.
EX: CHECK ALL THAT APPLY.
Default = ALL CAPS.
Is not read to respondent.
9. Response Alternatives
Displays question response alternatives.
Can be an input field, roster, or grid.
10. Screen Navigation Line
Display System Functions for navigating to previous page, next page, or next
question on route.
*Need to list these and their functions
2. SCREEN TYPE SPECIFICATIONS
INSTANCE NAVIGATOR
Screen type:
Instance Navigator
No input field display
Used to specify where Instance Navigator screen should be
displayed.
Screen Text is specified in a separate Instance Navigator
Specification.
Question Display:
Includes instruction re: what items to display in I/N screen.
If I/N screen is not to be displayed and list of items should
be processed “in the background”, specify “INVOKE NOT
TRAVEL I/N.”
Item order number:
1
Input field name:
NAVIGATOR
Cheshire Name:
N/A
Using N/A since the Input field name is a generic name and
is not used in the program.
Field Type (Item class):
Enumerated
Type Name:
TInstanceNavigator
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
Route
Response alternative 1/SelectItemInList specifies route to
1st question to be asked in detail loop for Item being asked
about in Instance Navigator.
Response alternative 2/SelectContinueInterview specifies
route when interviewer selects “CONTINUE
INTERVIEW”.
NO ENTRY
Screen type:
NO ENTRY
No input field display
Commonly used to display introduction text
Interviewer Instructions II:
Default = NO interviewer instructions
The interviewer is trained to select “NEXT PAGE” after
reading text
In Cheshire, we had an interviewer instruction “PRESS
ENTER TO CONTINUE.” However, this is no longer
applicable.
Item order number:
1
Input field name:
Need to generate a new field
In Cheshire, NO ENTRY screens did not have a variable
name
In WVS, an input field is specified in order to capture that
the screen has been displayed; however, the input field is
not displayed on screen.
Create a new field name that does not match an existing
variable name in Cheshire or WVS. The new field will not
be transformed back to the Cheshire database and can
exceed 8 characters.
Cheshire Name:
TEMP
Using TEMP for the Cheshire name flags that we do not
need this response stored in Cheshire.
Field Type (Item class):
Enumerated
Type Name:
TContinueEmpty
This type defines 1 response alternative, 1/Continue, and
EMPTY as an attribute. Empty allows the interviewer to
select NEXT PAGE without entering a response.
1/Continue is then stored in the background to indicate that
the screen has been displayed.
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
Route:
Route for 1/Continue and Empty must match
SAMPLE “NO ENTRY” SPECIFICATIONS:
YES/NO
Screen type:
YES/NO
Enumerated field
Response alternatives are always YES and NO
Only 1 response permitted
Response alternatives displayed on the screen as radio
buttons
Item order number:
1
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Field Type (Item class):
Enumerated
Type Name:
Default = TYesNoDKRF (allows DK and RF)
Other Type names.
Allows only DK:
Allows only RF:
Otherwise:
TYesNoDK
TYesNoRF
TYesNo
Answers Allowed:
1
Drop down:
Most often, this is set to NO
YES/NO screens can be displayed as a drop down. This
option is often used in a grid to minimize space
requirements.
Lookup File:
NO
SAMPLE “YES/NO” SPECIFICATIONS:
CODE 1
Screen type:
CODE 1
Enumerated field
Only 1 response permitted
Response alternatives displayed on the screen as radio
buttons
Multi Field display:
Typically, CODE 1 screens include an Other Specify field
displayed as an overlay. If Other Specify field included,
set* alignment:
Alignment = Vertical
Item order number:
Input fields are numbered in the order they appear on the
screen. If Other Specify field included, the CODE 1 field
appears 1st, followed by the OTHER SPECIFY field. If
only one field, set Item Order Number = 1.
CODE 1 field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Field Type (Item class):
Enumerated
Type Name:
In most cases, the Cheshire range name has been translated
to the WVS type name in SpecWriter. If not, a new type
needs to be generated that matches the Cheshire
specifications and is then linked to input field.
Default =
The numeric response for an Enumerated Type matches the
Cheshire input values
For each response, the English text matches the Cheshire
response text displayed on the screen
For each response, the label needs to be modified to
abbreviate response English text with no spaces
Answers Allowed:
1
Drop down:
Default = NO
CODE 1 can be displayed as a drop down list if requested
by design. This option is often used in a grid to minimize
space requirements.
Lookup File:
NO
OTHER SPECIFY field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Item text display:
Interviewer instructions are usually specified as part of the
Item Text on Other Specify text input fields. The
interviewer instructions will appear in parenthesis. When
Interviewer instructions are included in the Item Text,
specify the Interviewer Instructions to be displayed in blue.
EX: Display “(SPECIFY)” in the same blue font used for
interviewer instructions.
Item Text:
Item Text appears above the Other Specify Input field on
CODE 1/CODE ALL screen types.
EX:
OTHER (SPECIFY)
The Item Text should match the Response Text for the
CODE 1/CODE ALL enumerated field.
EX:
91. OTHER PERSON REPORTED (SPECIFY)
The Response Text
The Item Text
(SPECIFY)
= OTHER PERSON REPORTED.
= OTHER PERSON REPORTED
NOTE: The interviewer instruction is usually specified as
part of the CODE 1/CODE ALL enumerated Response
Text in the Cheshire Specifications. The interviewer
instruction, (SPECIFY), should never be specified as part
of the English Text for the enumerated field. It is only
specified as part of the Item Text.
Field Type (Item class):
String
Type Name:
Default = TOthrSpec
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
SAMPLE “CODE 1” SPECIFICATIONS:
CODE ALL
Screen type:
CODE ALL
Enumerated Field
Multiple responses permitted
Response alternatives displayed on the screen as check
boxes
Interviewer Instruction II:
Default = “CHECK ALL THAT APPLY.”
There may be screens where this instruction is expanded to
include question context.
EX: “CHECK ALL REASONS THAT APPLY”.
We will no longer be using the Cheshire terminology
“CODE ALL….”.
Multi Field display:
Typically, CODE ALL screens include an Other Specify
field displayed as an overlay. If Other Specify field
included, set alignment:
Alignment = Vertical
Item order number:
Input fields are numbered in the order they appear on the
screen. If Other Specify field included, the CODE ALL
field appears 1st, followed by the OTHER SPECIFY field.
If only one field, set Item Order Number = 1.
CODE ALL field:
Input Field Name:
Need to generate a new field name
In Cheshire, the input to CODE ALL screens is stored in
separate variables. Each response is assigned a variable
name. (See Cheshire Name below) If the response is
selected, the corresponding variable is set to 1. If the
response is not selected, the corresponding response is set
to 2. If the response to the question is DK, RF, all variables
associated with question are set to DK or RF (excluding
Other Specify variable).
In WVS, the input to CODE ALL is stored in a single
variable
Generate a new variable name for these screens that does
not match any existing variable name in Cheshire or WVS.
The new field will not be transformed directly into the
same field name in Cheshire. Instead, it will be
transformed back to the original Cheshire variables
associated with the CODE ALL screen. The new field
name in WVS is often named with a similar pattern to the
Cheshire variable names.
Cheshire Name:
When field name does not exist in Cheshire, specify
NONE. In addition, list Cheshire variables associated with
each response, specifying which variable is set based on
numeric response collected:
NONE
REPLACES THE FOLLOWING CHESHIRE
VARIABLES:
1=ACCS.ACCWRITE
2=ACCS.ACCEXPDR
3=ACCS.ACCEXPSP
91=ACCS.ACCOTHER
Field Type (Item class):
Enumerated
Type Name:
Need to build new Type to match Cheshire specifications
Type will be set up similar to CODE 1 Enumerated types
Default =
The numeric response for an Enumerated Type matches the
Cheshire input values
For each response, the English text matches the Cheshire
response text displayed on the screen
For each response, the label needs to be modified to
abbreviate response English text with no spaces
Answers Allowed:
Default = Set to maximum number of response alternatives,
excluding DK and RF.
If DK or RF selected, do not allow any other response to be
selected.
Drop down:
NO
Lookup File:
NO
OTHER SPECIFY field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Item text display:
Interviewer instructions are usually specified as part of the
Item Text on Other Specify text input fields. The
interviewer instructions will appear in parenthesis. When
Interviewer instructions are included in the Item Text,
specify the Interviewer Instructions to be displayed in blue.
EX: Display “(SPECIFY)” in the same blue font used for
interviewer instructions.
Item Text:
Item Text appears above the Other Specify Input field on
CODE 1/CODE ALL screen types.
EX:
OTHER (SPECIFY)
The Item Text should match the Response Text for the
CODE 1/CODE ALL enumerated field.
EX:
91. OTHER PERSON REPORTED (SPECIFY)
The Response Text
The Item Text
(SPECIFY)
= OTHER PERSON REPORTED.
= OTHER PERSON REPORTED
NOTE: The interviewer instruction is usually specified as
part of the CODE 1/CODE ALL enumerated Response
Text in the Cheshire Specifications. The interviewer
instruction, (SPECIFY), should never be specified as part
of the English Text for the enumerated field. It is only
specified as part of the Item Text.
Field Type (Item class):
String
Type Name:
Default = TOthrSpec
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
SAMPLE “CODE ALL”
SPECIFICATIONS:
NUMERIC
Screen type:
NUMERIC
Collects Integer or Real values
*Note: Numeric input can often be part of a different
screen type. Apply these standards to any screen type that
numeric input fields.
Item order number:
Input fields are numbered in the order they appear on the
screen. When single input field, set Item Order Number =
1.
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Label/Label position:
Most numeric fields have a label to the left or under the
input field to help define input value:
Default Month:
Default Day:
Default Year:
Default Amount/
Percentages:
“MM” under input field.
“DD” under input field.
“YY” under input field for 2-dig.
“YYYY” under input field for 4 dig.
“AMOUNT:” left of input field.
Field Type (Item class):
Collect Decimals:
Do not collect Decimals:
Real
Integer
Type Name:
In most cases, the Cheshire range name has been translated
to the WVS type name in SpecWriter. If not, a new type
needs to be generated that matches the Cheshire data
dictionary range.
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
Default=NO
Field Size:
Blank
Min Value:
Minimum value for system range
Default = Cheshire data dictionary range
Max Value:
Maximum value for system range
Default = Cheshire data dictionary range
Mask:
A mask can also be applied to further define input value:
Dollars
Displays REAL fields with decimal
Displays $ to the left of input field
Dollars No Cents
Displays REAL fields without
decimal
Displays $ to the left of input field
Percent
Displays % to right of input field.
SAMPLE “NUMERIC” SPECIFICATIONS:
TEXT
Screen type:
TEXT
Collects single line of text
*Note: Text can often be part of a different screen type.
Apply these standards to any screen type that collects text
fields.
Item order number:
Input fields are numbered in the order they appear on the
screen. When single input field, set Item Order Number =
1.
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Label/Label Position:
Text strings often have a label to the left of the input field
Default = Match Cheshire specifications
Field type (Item class):
String
Type Name:
Standard Types have been generated to define text fields
Type Naming convention = TString
Apply standard Type that matches length of input field. If
it doesn’t exist, generate a new Type using the naming
convention above.
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
Field Size:
Maximum length of input text
Default = Length defined in Cheshire data dictionary
SAMPLE “TEXT”
SPECIFICATIONS:
VERBATIM TEXT
Screen type:
VERBATIM TEXT
Collects verbatim response text
Displayed as an OPEN text box, allowing for multiple lines
of text to be entered
Allows text wrapping
Interviewer Instructions II:
Default = RECORD VERBATIM.
Item order number:
1
Input field Name:
Need to generate a new field name
In Cheshire, VERBATIM TEXT screens collect each line
of verbatim text response in a separate variable. Typically,
in the input variables are numbered by input line:
PPRVBUS1, PPRVBUS2, PPRVBUS3
In WVS, VERBATIM TEXT will be stored in a single
variable
Generate a new variable name for these screens that does
not match any existing variable name in Cheshire or WVS.
The new field will not be transformed directly into the
same field name in Cheshire. Instead, it will be
transformed back to the original Cheshire variables
associated with the VERBATIM TEXT screen. The new
field name in WVS is named using the following naming
convention:
Naming convention =
Cheshire variable name minus line #.
EX: PREVSAT is the variable name for
PREVSAT1, PREVSAT2, PREVSAT3.
If we cannot use the current naming convention because the
“NEW” name already exists, the second convention would
be:
Cheshire variable name minus line # + VB.
EX: PREVSATVB
Cheshire Name:
When field name does not exist in Cheshire, specify
NONE. In addition, list Cheshire variables associated with
each line of verbatim text collected:
NONE
REPLACES THE FOLLOWING CHESHIRE
VARIABLES:
ACCS.PREVSAT1
ACCS.PREVSAT2
ACCS.PREVSAT3
Field Type (Item class):
OPEN
Type Name:
Standard Types have been generated to define VERBATIM
TEXT fields
Type Naming convention = TOpen
Length = Product of the Length of Cheshire Variable and
number of Cheshire input fields collected
Most common Type Name = TOpen135 (3 lines of 45
character input fields)
Apply standard Type that matches length of input field. If
it doesn’t exist, generate a new Type using the naming
convention above.
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
Field Size:
Product of the Length of Cheshire Variable and number of
Cheshire input fields collected
SAMPLE “VERBATIM TEXT” SPECIFICATIONS:
QUANTITY UNIT
Screen type:
QUANTITY UNIT
Multi-field screen that collect an amount based on Unit
specified
Collects the UNIT first, followed by QUANTITY
There may be one or more QUANTITY fields depending
on the UNIT response
Multi-field display:
Default = Matches Cheshire layout
If 2 fields, set alignment = Horizontal or Vertical
If 3 or more fields, additional instructions for displaying
multiple fields may be needed:
EX:
Set Alignment=Vertical
And then add the following under Multi-field display
instructions:
Display on 1st line.
Display and
on 2nd line.
Include instruction “Display All Fields at One Time” if
applicable. If instruction not included, only fields “on the
route” will be displayed. Other fields will display as
overlays.
Default rules for displaying multiple field screens:
If not all fields are collected, only display fields “on
the route”. EX: Most Quantity Unit screens has
dependencies based on Unit field.
If all fields are collected, display all input fields at
the same time, not as overlays. EX: Address,
phone and date screens.
Item order number:
Input fields are numbered in the order they appear on the
screen. UNIT field appears 1st, followed by the
QUANTITY field(s).
UNIT field:
Input Field Name:
Default = Cheshire variable name.
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
QUANTITY field(s):
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
NOTE:
UNIT and QUANTITY field type and attributes will depend entirely on question design.
Most common Unit fields are CODE 1 Enumerated fields.
Most common Quantity field is INTEGER or REAL.
SAMPLE “QUANTITY UNIT” SPECIFICATIONS:
DATES
Screen type:
DATE
Dates are collected in 3 separate fields, MONTH, DAY and
YEAR. This allows for partial data to be collected. For
example, if the respondent knows the Month and Year but
does not know the Day, the interviewer can code the
Day=DK and still collect the remaining date.
*Note: Dates can often be part of a different screen type.
Apply these standards to any screen type that collects dates.
Multi Field display:
Default Alignment = Horizontal
If more than one date on screen, additional instructions for
displaying multiple fields may be needed:
EX:
Set Alignment=Vertical
And then add the following under Multi-field display
instructions:
EX:
Display Admission date input fields, EVBEGMM,
EVBEGDD, EVBEGYY, on 1st line.
Display discharge date input fields, EVENDMM,
EVENDDD, EVENDYY, on 2nd line.
Item order number:
Input fields are numbered in the order they appear on the
screen. MONTH is displayed 1st, followed by DAY and
then YEAR.
MONTH field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Item Text:
Item text can be specified to further define Date input
fields:
EX: ADMISSION DATE:
*Note: Item Text is displayed above input field where it is
specified.
Label/Label position:
Default = MM
Display under input field
Field Type:
Integer
Type Name:
Answers Allowed:
Default = TMonthInt (allows DK, RF)
1
Drop Down List:
NO
Lookup File:
NO
DAY field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Label/Label position:
Default = DD
Display under input field
Field Type:
Integer
Type Name:
Default = TDayDKRF (allows DK, RF)
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
YEAR field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Label/Label position:
Default 2-Digit Year: YY
Default 4-Digit Year: YYYY
Display under input field.
Field Type:
Integer
Type Name:
Default 2-Digit Year: TYear2DKRF (allows DK, RF)
Default 4-Digit Year: TYear4DKRF (allows DK, RF)
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
SAMPLE “DATE”
SPECIFICATIONS:
PHONE NUMBERS
Screen type:
PHONE
Phone numbers are collected in 3 fields, AREA CODE,
EXCHANGE and LOCAL numbers. This allows for
partial data to be collected. For example, if the respondent
knows the Exchange and Local numbers, but does not
know the Area Code, the interviewer can code the Area
Code=DK and still collect the remaining phone number.
*Note: Phone numbers can often be part of a different
screen type. Apply these standards to any screen type that
collects phone numbers.
Multi Field display:
Alignment = Horizontal
If phone number is displayed with other fields on the same
screen (like address fields or other phone numbers),
additional instructions for displaying multiple fields may be
needed:
EX:
Set Alignment=Vertical
And then add the following under Multi-field display
instructions:
EX:
Display SP’s phone number input fields on 1st line.
Display Proxy’s phone number input fields on 2nd line.
Item order number:
Input fields are numbered in the order they appear on the
screen. AREA CODE is displayed 1st, followed by
EXCHANGE and LOCAL field.
AREA CODE field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Label/Label position:
Default = PHONE NUMBER:
Display left input field
Field Type:
Integer
Type Name:
TBD
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
EXCHANGE field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Field Type:
Integer
Type Name:
TBD
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
LOCAL field:
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Field Type:
Integer
Type Name:
TBD
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
LIST
Screen type:
LIST
A LIST is used to display multiple questions with the same
response alternatives in a table format. Questions are
displayed in a list. Response alternatives are listed in
columns to the right of questions.
Multi Field display:
Alignment = Vertical
Item order number:
Input fields are numbered in the order they appear on the
screen
Question Text:
Question text that appears above individual questions in list
Displayed at top of screen
ITEM 1 in list:
• Repeat the following for each question in list.
Input Field Name:
Default = Cheshire variable name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Item Text display:
Default =
Display “a.” in front of List Item text
Repeat for each item in list, (EX: b., c., d….)
The default display =
In separate column in front of Question in LIST, display
“letter specified”.
Display fill instructions for Item Text are entered here
Item Text:
Question text for 1st item in list is specified here
Field Type:
Enumerated
Field Type will be the same for each ITEM in the list
Type Name: In most cases, the Cheshire range name has
been translated to the WVS type name in SpecWriter. If
not, a new type needs to be generated that matches the
Cheshire specifications and is then linked to input field.
Default =
The numeric response for an Enumerated Type matches the
Cheshire input values
For each response, the English text matches the Cheshire
response text displayed on the screen
For each response, the label needs to be modified to
abbreviate response English text with no spaces
Answers Allowed:
1
Drop Down List:
NO
Lookup File:
NO
SAMPLE “LIST”
SPECIFICATIONS:
ROSTERS
Screen Type:
Roster
Displays related items in a table format
Rows are automatically populated when roster is displayed
based on Roster/Grid instructions. These rows are
sometimes referenced as “items loaded” into roster.
Can display multiple rows
Can display multiple columns
Items may be added, edited and/or deleted depending on
functions enabled
You cannot add/edit/delete items directly in roster display.
These functions are handled through an additional Pop-Up
Window. The specifications that pertain to adding,
deleting and editing items in the roster are handled by
Roster Pop-Up specifications.
Row(s) SELECTED in roster is the response to the roster
question.
Roster Name:
Name of Roster Pop-Up Window that is linked to the
Roster Question display. Is activated when ADD, EDIT
and DELETE function is invoked.
EX: Event Roster Begin Date RV
Roster Type:
Single Item Select / Multiple Item Select
Single Item Select = Allow only one item to be selected
Multiple Item Select = Allow more than one item to be
selected.
Roster Functions:
YES/NO
Flag which Roster Function enabled
ADD ITEM
EDIT ITEM
DELETE ITEM
SEARCH ITEM
*Currently we are only utilizing ADD and EDIT functions.
There is a separate field in SpecWriter that specifies Roster
Function Display text
For each function enabled, specify display text
EX: Display as ‘Add a Plan’.
Roster/Grid instructions:
Roster load instructions:
Items to be displayed in roster
Each item is displayed as a separate row in roster
Order rows are to be displayed
What rows are Protected
What rows are Active
Check for duplicate items
Roster header
Include “NO SELECTION REQUIRED” if roster
should allow no selection.
* NOTE: Whether or not the ENTIRE Roster is
displayed as one column or two columns is
specified as part of the General Specifications
Global Displays. For example, the provider roster
is now specified to display as two separate roster
columns.
Roster/Grid display:
Roster column instructions:
# of columns
# of columns refers to how many columns of
data will be displayed in Roster. Each
column is linked to one or more database
fields. This is not related to the General
Specification Global displays which is now
specifying whether or not the ENTIRE
Roster is displayed as one or two columns.
Column headers – WVS only supports UPPER
CASE headers.
Data displayed in roster columns
Display fill instructions
Interviewer Instruction II:
Typically an interviewer instruction is included:
EX: SELECT OR ADD ALL PRIVATE PLAN NAMES.
Field Name:
Need to generate a new field name
In Cheshire, we set a variable on each Item that was
selected
EX: PLAN.PLANPICK=1/Yes
In WVS, the items selected at the roster will be stored in a
single input string field
The input field is specified for programming use only.
It will not be transformed back to the Cheshire database
and can exceed 8 characters.
Field naming convention =
RosterName_QuestionDescriptor
EX: PLAN_PRIVATE
Cheshire Name:
TEMP
Field Type:
String
Type Name:
Standard Type names have been generated
Type naming convention =
T + RosterName + PICK + Length of field
EX: TPlanPick135
Answers Allowed:
1
*Note: We do not use this specification field to specify
how many items can be selected from the roster.
Drop Down List:
NO
Lookup File:
Default = NO
Soft Edits:
Soft Edits are not supported by WVS at Rosters.
Hard Edits:
standard Hard Edit.
Hard Edits invoked in Pop-Up function differently from the
Need to get supporting documentation from System’s team.
There is a default DUPLICATION check at Rosters that
looks for duplicate items ADDED to roster. This
duplication check does not compare items added to Roster
against Items loaded in Roster. The Default System Check
will be invoked before any Hard Edits that have been
specified.
Background Variable
Assignments:
Specify Roster Pop-Up specification information:
EX:
If Provider added at Provider Roster, see Provider Roster
pop-up specifications for programming instructions.
Variables populated in Provider Roster Pop-Up Window:
PROV.PROVNUM Provider number
PROV.PROVRNDC Round number
PROV.PROVNAME Provider name
If Provider added, set provider type as instructed below:
Background Variable:
Specify any background variables set at roster.
EX:
PROVTYPE PROV.PROVTYPE=2/EmergencyRoom.
SAMPLE “ROSTER”
SPECIFICATIONS:
SAMPLE ROSTER POP-UP WINDOW SPECIFICATIONS:
Part 1 = Pop-Up Window specification overview WORD document.
Part 2 = Pop-Up Window Input field attributes/flow.
Event Roster Begin Date
Pop-Up Specifications
Event Roster Style B: Event Begin Date – Disallow Repeat Visit
Roster Pop-Up Window Display:
ENTER THE EVENT DATE.
_______
MM
________
DD
_________
YY
Overview of display:
Display “ENTER THE EVENT DATE.” in the same blue font used for interviewer
instructions.
Input fields:
1. EVNT.EVBEGMM
2. EVNT.EVBEGDD
3. EVNT.EVBEGYY
See attached Event Roster Begin Date Pop-Up Window Item specifications.
Background Variable Assignments:
If adding event:
Create a new Event for each visit/event added. Events are stored on EVNT:
EVNT key = EVNT.EVNTBASE + EVNT.EVNTNUM
EVNT.EVNTBASE
EVNT.EVNTNUM
EVNT.EVNTRNDC
EVNT.EVNTTYPE
=
=
=
=
EVNT.STEVTYPE
=
BASE.BASEID
Highest EVNT.EVNTNUM + 001
Current round
Specified at Question level specification.
Stores Type of Event.
Specified at Question level specification.
EVNT.EVNTPROV =
BASE.LASTEVNT
=
Stores Type of Event used in Statement Series.
N/A for all Event Roster Questions.
Specified at Question level specification.
Stores Provider number linked to event.
N/A for all Event Roster Questions.
Highest EVNT.EVNTNUM.
Set BASE.LASTEVNT = EVNT.EVNTNUM just added.
See attached All Event Roster Background Variable specification for additional variable
specifications.
GRIDS
Screen Type:
Grids
Displays related items in a table format
Rows are automatically populated when grid is displayed
based on specifications
Cannot add or delete rows in grid
Can display multiple rows
Can display multiple columns
Columns can be display only or can active input fields
Grid Functions:
No longer supported by WVS
Roster/Grid instructions:
Grid load instructions:
Items to be displayed in grid
Each item is displayed as a separate row in grid
Order rows are to be displayed
What rows are Protected
What rows are Active
Roster/Grid display:
Grid column instructions:
# of columns
Column headers
Column Display Only vs. Input column
Display fill instructions
Question Text:
Any question text that should appear above the grid and
should always remain on the screen should be specified
here.
INPUT COLUMNS:
Each Input column is specified as a separate Input field.
Repeat the following for each Input column in grid:
Field Name:
Default = Cheshire field name
Cheshire Name:
Cheshire SEGMENT.VARIABLE name
Item Text:
Any Question text that should only be displayed when
column is active should be specified here
Item Text display:
Display instructions for Item Text are entered here
Specify remaining specifications based on Input Field type.
EXAMPLE OF GRID SPECIFICATION:
| File Type | application/pdf |
| Author | Lisa Sweeney |
| File Modified | 2010-03-30 |
| File Created | 2010-03-30 |