Medicare Current Beneficiary Survey (MCBS):(CMS Number CMS-P-0015A)

MCBS MAIN STUDY
R55 General Specifications for Blaise/WVS
Default Specifications
Version 07.01.0001
8/14/2009

STORING FIELDS ON ROUND SPECIFIC RECORDS:
If an input field is specified that is stored on a Round specific record (i.e. Round number
is part of the record key), the default is to collect and store data on the “current round”
record unless otherwise specified.
The exception to this rule is data collected/updated in the following sections will be
written to the “previous round” record:
Health Insurance Summary
Prescription Medicine Summary
SQL FIELD NAMING CONVENTIONS:
Blaise FieldName = SQL FieldName
SQL FieldName = Cheshire VariableName.
SQL Table Name = tbl + Cheshire SegmentName
NO ENTRY SCREENS:
Input field is specified with field type = TcontinueEmpty.
Do not display response option on screen.
YES/NO SCREENS
Default Field Type Name:
TYesNoDKRF
Allows DK and RF.
Other Type names.
TYesNoDK
TYesNoRF
TYesNo

Allows only DK
Allows only RF
Disallows DK and RF.

CODE ONE SCREENS:
Default alignment if multiple fields = Vertical.
In ccases where there are multiple fields, Code One Screens typically include an Other
Specify Text field as the second field.
CODE ALL SCREENS:
Default # of response setting = Maximum number of response alternatives, excluding
DK and RF. Cannot exceed maximum number of response alternatives.

If DK or RF is selected as a response at CODE ALL screens, do not allow any other
response.
Code All Screens typically include an Other Specify Text field.
Default alignment if multiple fields = Vertical
Default Interviewer Instruction II = “CHECK ALL THAT APPLY.”
ENUMERATED RESPONSES:
Default settings Drop Down List = No
Display English Response text in ALL CAPS unless otherwise specified.
OTHER SPECIFY TEXT INPUT FIELDS:
Default Item Text display instruction:
The Item Text should match the Response Text for the “Other” enumerated response.
Display “(SPECIFY)” in the same blue font used for interviewer instructions.
Examples:
91 OTHER
The Item Text = OTHER (SPECIFY)
91 OTHER PERSON REPORTED (SPECIFY)
The Item Text = OTHER PERSON REPORTED (SPECIFY)
Default Field Type = String, Length 30
Default Field Type Name = TOthrSpec
DATE SCREENS:
Default display all fields at one time.
Default alignment = horizontal.
Default labels are specified under input fields:
DD = Day Field
MM = Month Field
YY = Year Field
PHONE SCREENS:
Default display all fields at one time.
Default alignment = horizontal.
LIST SCREENS:
Item Text display instruction:
Display “a.” in front of List Item text
Repeat for each item in list, (EX: b., c., d….)
The default is to display “letter” in separate column in front of question in LIST.
VERBATIM TEXT SCREENS:
Default Field Type = OPEN, length specified
Default Field Type Name = TOPEN

DISPLAYING SCREENS WITH MULTIPLE FIELDS:
The default is to display multiple input fields as “overlays”. However, an additional
specification may be included to “display all input fields at the same time, not as
overlays” that overrides the default. This will most often be used for the following types
of screens:
Address screens
Phone screens
Date screens
Claim Control # screens
Surgery screens
ROSTERS:
Roster Display Order:
If Display Order is not specified at roster, the default is to display the items in the roster
in the “order of entry”, matching the order the items are stored on database table.
Roster Delete function:
The default DELETE function will be enabled on all Rosters where ADD is enabled.
Will be used only to delete items JUST ADDED unless otherwise specified.
INSTANCE NAVIGATOR SCREENS:
The default is to only display items just added to the Roster prior to the Instance
Navigator screen.
The exception to this rule is if:
1) Public or Private Plans are added in HIS. If a Public or Private Plan was added in
an earlier loop, the plan name(s) will be displayed in I/N as “DONE”.
2) Discount Membership Plans are added in DM. If a DM was added in an earlier
loop, the DM name(s) will be displayed in I/N as “DONE”.
3) Events added in a utilization section. If an event of the same event type was
added for the same provider in an earlier loop, the event(s) will be displayed in
I/N as “DONE”.
4) Provider Service date events added in ST or NS. If an event was added for the
same provider in an earlier loop, the event(s) will be displayed in I/N as “DONE”.
5) Prescription Medicines added in ST or NS. If a PM is added in an earlier loop,
the PM name(s) will be displayed in the PM GRID with # of purchases prefilled.
REPORTS:
Report Display Order:
If Display Order is not specified at report, the default is to display the items in the report
in the “order of entry”, matching the order the items are stored on database table.
COMMENT FUNCTION:

The default is to always display COMMENTs link on each screen in MCBS WVS
instrument. Disregard COMMENTs specification. Should always be set COMMENTS =
YES.
CONTEXT HEADER:
Default display text in ALL CAPS.
INTERVIEWER INSTRUCTION I AND II:
Default display text in ALL CAPS.
QUESTION TEXT:
Display text in upper and lower case unless otherwise specified.
Embedded Interviewer instructions in Question Text:
Interviewer Instructions embedded in Question text appear in ALL CAPS and are often
enclosed in brackets.
Default display instructions for Interviewer Instructions embedded in Question text:
1) Display Interviewer Instructions (text in ALL CAPS) in the same blue font used for
Interviewer Instructions.
2) Display a “single space” between Open Bracket and “Interviewer Instruction”.
3) Display a “colon” after “Interviewer Instruction”.
4) Display a double space” between “colon” and additional Question Text.
5) Always display brackets that enclose the Interviewer Instruction and additional text
unless otherwise specified.
6) Always display parenthesis that enclose any text included in the Interviewer
Instruction unless otherwise specified.
Examples of embedded Interviewer Instructions in Question text:
[READ PLAN NAMES BELOW]
[READ MANAGED CARE PLAN NAME(S) BELOW]
[IF RESPONDENT HAS BOTTLE, ASK:]
[ PROBE: Addition text that can be read.]
[ EXPLAIN IF NECESSARY: Additional text can be read.]

[READ CONDITION(S) BELOW]
[READ REASONS BELOW IF NECESSARY.]
[READ MEDICINE(S) BELOW]
IF CLINIC, ASK:
IF SOME OTHER PLACE, ASK:
[IF NECESSARY, ASK:]
[IF HOUSING TYPE IS NOT OBVIOUS, ASK:]
DISPLAY TEXT IN “BOLD”:
BOLD definition: Display text in a larger font size.

DISPLAY INSTRUCTIONS IN LOOPS:
When specifying text at a question in a loop where the question will be asked for multiple
items, instructions will include “display name of item” currently being asked about. The
item referenced in the current loop should be displayed.
Examples:
Display the event date for the orthopedic item being asked about.
MASKS:
A Mask can 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
Allow interviewer to manually enter decimal.
Displays $ to the left of input field
Percent
Displays % to right of input field.
If REAL field, do not display decimal.
Allow interviewer to manually enter decimal.

HARD AND SOFT EDITS:
Hard and Soft edits are always specified to be invoked as a Blaise Hard and Soft Edit
Window.
However, for certain screen types, the programmer has some flexibility and may be able
to program Hard Edit checks as a WVS system range check. A WVS system range check
is displayed in RED directly on the input screen versus a separate Blaise Edit Window.
If approved by design, this should not be considered an error. The error message may not
necessarily match the Hard Edit error message specified. However, the logic specified
that invokes the hard edits should match the program.

DATABASE RECORDS FLAGGED AS “DELETED”
The following Database tables include flags that indicate that the database record is no
longer active and should not be included in Roster, Report or Grid displays and should
not be included as a valid record in any programming logic or checks. These records are
considered as “invalid”.
EVNT

EVNT.EVNTDFLG = 1/Yes

* Exception: If HP/HF Event exists on EVNT, and EVNT.EVNTDFLG = 1/Yes, if
Provider selected as a current round Home Health provider in the current round, we will
update the existing EVNT.EVNTDFLG = empty and reactive the original EVNT record.
See BOX HH1AA.

HERO

HERO.HERODFLG = 1/Yes

PMRO

PMRO.PMRODFLG = 1/Yes

PLAN

PLAN.PLANHIDE = 1/Yes
PLAN.PLANDFLG = 1/Yes
PLAN.MHMODFLG = 1/Yes
PLAN.LOSEPLFG ^= EMPTY

No longer used in WVS

* Exception: If Medicaid or TRICARE plan exists on PLAN, and PLAN.PLANDFLG =
1/Yes or PLAN.LOSEPLFG = 1/Yes, if Medicaid or TRICARE is added in the current
round, we will update the existing PLAN.PLANDFLG = empty and/or
PLAN.LOSEPLFG = 1/Yes and reactive the original PLAN record. See HI5, HIT1.
DMEM

DMEM.LOSEDMFG ^= EMPTY

OSOP

OSOP.OSOPHIDE = 1/Yes
OSOP.LOSEOSFG ^= EMPTY

PAYM

PAYM.PAYMDFLG = 1/Yes

XCEV

XCEV.DELLINK = 1/Yes

No longer used in WVS

DATABASE RECORDS PROGRAMMING “DONE” FLAGS
*Only Roster with I/N screen follow will have this new delete function. ( It enables
user to back from detail question to roster to delete the new added records)
*Any record with finished detail will not be able to delete from roster.
Utilization section:
DU:
Delete new added event (wvsDeleteFlag=’Yes’): 1. Roster EVENT_DU or 2. DU1( any
incomplete events)
Complete flag tblevnt.EvntDoneFlag=’Yes’
Incomplete event tblevnt.wvsDeleteFlag=’Yes’
ER:
Delete new added event (wvsDeleteFlag=’Yes’): 1. Roster EVENT_ER or 2. ER1( any
incomplete events)
Complete flag tblevnt.EvntDoneFlag=’Yes’
Incomplete event tblevnt.wvsDeleteFlag=’Yes’
OP

Delete new added event (wvsDeleteFlag=’Yes’): 1. Roster EVENT_OP or 2. OP1( any
incomplete events)
Complete flag tblevnt.EvntDoneFlag=’Yes’
Incomplete event tblevnt.wvsDeleteFlag=’Yes’

MP:
Delete new added event (wvsDeleteFlag=’Yes’) 1. Roster EVENT_MP or 2.
MP1,MP18,MP26,MP34,MP42,MP50( any incomplete events, please check the routin
when back up to the gate question.)
Complete flag tblevnt.EvntDoneFlag=’Yes’
Incomplete event tblevnt.wvsDeleteFlag=’Yes’

HIS section
1. Delete new added previous round Private plan: Roster PLAN_HISPRIVATE (HIS 20)
2. Delete new added previous round Public plan: Roster PLAN_HISPUBLIC (HIS12)
Complete plan tblPlro.PlroDoneFlag=’Yes’
Incomplete plan tblPlro.PlroDoneFlag=’No’, tblPlan.wvsDeleteFlag=’Yes’

HI section
1.Delete new added current round private plan : Roster PLAN_PRIVATE (HI20)
2.Delete new added current round public plan : Roster PLAN_PUBLIC (HI12)
Complete plan tblPlro.PlroDoneFlag=’Yes’
Incomplete plan tblPlro.PlroDoneFlag=’No’, tblPlan.wvsDeleteFlag=’Yes’
On Rosters where deleting an item just added is supported, there will be a link on the
screen displayed such as “DELETE NEW PERSON”.
Compiled list of WVS Done Flags:
The following is a compiled list of “done” flags programmed in SQL. Unless noted
above, these fields should not be used to determine whether data is complete or
incomplete.
SQL Table
Field
Type
Length
tblCOST
CPSInitDone
varchar 3
tblCOST
CPSDone
varchar 3
tblCOST
STDone
varchar 3
tblDMRo
DMRoDetailDone
varchar 3
tblEvnt
IPDone
varchar 3
tblEvnt
OMNotDone
varchar 30
tblEvnt
OMDone
varchar 3
tblEvnt
HHSDone
varchar 3
tblEvnt
STDateDone
varchar 3
tblEvnt
STOmDone
varchar 3

tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblEvnt
tblPLAN
tblPlro
tblPlro
tblPlro
tblPMRo
tblPMRo
tblPMRo
tblPMRo
tblPMRo
tblTSOP
tblTSOP
tblTSOP
tblXCev
tblXCev
tblXCev
tblXCev
tblXCev

STPMDone
STHHDone
NSPMDone
NSOMDone
NSDateDone
IPEventDriverDone
PSEventDriverDone
EREventDone
DUEventDone
MPEventDone
EvntDoneFlag
PlanDoneFlag
PubDtlDone
PrvDtlDone
PlroDoneFlag
PMSVADone
PMSHMODone
PMVADone
PMHMODone
PMPMRoDone
TSOPDone
SOPDone
REIMDone
XCevDone
XCevDone2
STPMDone
NSPMDone
NSXCevDone

varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar

3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3