Download:
pdf |
pdfSpecWriter Data
Form Version:
10/20/2023 3:16:38 PM
Report Type:
Full Detail
Project Database:
Language:
English
WESSQL300.MEPSSpring2024
Spec Label:
This is the cover page. Additional contents currently project specific.
ED - Page 1 of 18
MEPSSpring2024
Event Driver (ED) Section
(Rout
Full Detail Spec
BOX_00
Route Details:
(ED1000)
Item Type: Route
Type Class: If Then
01 Box = BOX_00, BOX_10, BOX_20, BOX_30, BOX_40, BOX_50
02 Loop = LOOP_10, LOOP_20
03 End Loop = END_LP10, END_LP20
06 Single Select with Fill in Answer Text = ED30_03
31 Date Item Single Field = ED20, ED30_01, ED30_02
99 Uncategorized = ED10
Grid 2 = ED10
BOX_10
(ED1005)
Item Type: Route
Type Class: If Then
Route Details:
Context header display instructions: SEE CONTEXT HEADER SPEC
Programmer
Instructions:
Context header display instructions: SEE CONTEXT HEADER SPEC
BOX_20
Programmer
Instructions:
(ED1010)
Item Type: Route
Type Class: If Then
If this instance of ED was launched through the F2, Add/Review Overview button, continue
with LOOP_10.
ED - Page 2 of 18
MEPSSpring2024
Event Driver (ED) Section
(Rout
Full Detail Spec
LOOP_10
Route Details:
(ED1015)
Item Type: Route
Type Class: Begin Loop
For each element in person’s-medical-events- roster, ask LOOP_20 – END_LP10.
Loop definition: LOOP_10 cycles on all persons with at least one medical event to be
reviewed. This loop cycles on persons that meet the following conditions:
-RU member with reported events in the current round or with open events in the prior
round, that now need to be followed up on (Preload.xxx).
The loop should start with the respondent, and then move to the RU member with the
lowest PersID that hasn’t been looped on yet with reported events.
LOOP_20
Route Details:
(ED1020)
Item Type: Route
Type Class: If Then
Loop Definition: LOOP_20 corrects event information, if necessary, and calls the
appropriate utilization section for each event. LOOP_20 cycles on RU members' events
within each provider in reverse chronological order (i.e. starting with the most recent event
within the provider displayed first).
The loop cycles on events that meet the following conditions:
-event type is not OM
-event type is not HH Volunteered: Meal delivery service
-event is not yet flagged as processed in utilization
-event is not yet flagged as processed in charge payment
-event is not yet flagged as processed in the Event Follow-up (EF) section
Ask ED10 to END_LP20.
ED - Page 3 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
ED10
Item Type:
Type Class:
Answer Type:
Help Available (
Context Header:
(ED1025)
Question
Enumerated
TContinue
BLAISE NAME: EvntGrid
Field kind: Datafield
ArrayMin:
Min value:
Field Size:
Answers allowed: 1
ArrayMax:
Max value:
)
Show Card (
)
Look Up File (
{PERSON'S FIRST MIDDLE AND LAST NAME} {EVN-DT} {EV}
{NAME OF MEDICAL CARE PROVIDER......}-{DOC or DEPT}
Question Text:
{{The next few questions ask detail about each of the times {you/{PERSON}} received medical or dental care.}
{Before continuing with the interview, let’s/Let’s} {first} talk about {the hospital stay for {you/{PERSON}} at
{PROVIDER} that began on {ADMIT DATE}/ when {you/{PERSON}} visited the emergency room at
{PROVIDER} on {VISIT DATE}/when {you/{PERSON}} received medical care from {an outpatient department/{DOC OR
DEPT}} at {PROVIDER} on {VISIT DATE}/ when{you/{PERSON}} received medical care from {{DOC OR DEPT} at}
{PROVIDER} on {VISIT DATE}/ when{you/{PERSON}} received telehealth care from {{DOC OR DEPT} at}
{PROVIDER} on {VISIT DATE}/ when {you/{PERSON}} received dental care from {PROVIDER} on {VISIT DATE}/the
services {you/{PERSON}} received at home from
{PROVIDER} during {MONTH}/{your/{PERSON}’S} stay at {PROVIDER} that began on {ADMIT DATE}}
{that we just added for {you/him/her}}.
{We will not be asking questions about {your/{PERSON}’s}{ hospital stay/care received at home} {that began on {ADMIT
DATE}/ for the month of {VISIT MONTH}} until the next interview. }
PRESS 1 AND ENTER TO CONTINUE WITH EVENT.
{CTRL-A: ADD NEW EVENT FOR ANYONE}
CTRL-E: EDIT DATE FOR SELECTED EVENT
CTRL-D: DELETE SELECTED EVENT
{CTRL-S: SWITCH TO EVENTS FOR A DIFFERENT RU MEMBER}
THERE ARE {NUMBER} REMAINING EVENTS TO PROCESS FOR {PERSON}.
{{number of events displayed} out of {total number of events} events shown - scroll for more}
Responses:
CONTINUE
1
ED - Page 4 of 18
)
MEPSSpring2024
Full Detail Spec
Programmer
Instructions:
Event Driver (ED) Section
(Ques
Preloaded Grid type 2- Flexible navigation, allow empty.
Once all the events show a status of complete in both the utilization and charge payment
columns, go to END_LP20.
Hard check: All cells in the column for ED10 are allowed to display empty, however, if FI tries
to move off of this page and go to the next person and there is still at least one event that
does not have a status of “DONE”, display the following message: “YOU MUST COMPLETE
ALL EVENTS FOR THIS PERSON BEFORE CONTINUING. {IF YOU WOULD LIKE TO TALK ABOUT A
DIFFERENT PERSON, SELECT CTRL-S.}” Display the sentence “IF YOU WOULD LIKE TO TALK
ABOUT A DIFFERENT PERSON…,” if
there is more than one RU member with events that haven’t been completed.
If coded 1, immediately go to appropriate utilization section: If event is coded HS, go to HS
utilization section.
If event is coded ER, go to ER utilization section. If event is coded OP, go to OP utilization
section.
If event is coded MV, go to MV utilization section. If event is coded TH, go to TH utilization
section. If event is coded DN, go to DN utilization section. If event is coded HH, go to HH
utilization section. If event is coded IC, go to IC utilization section.
If event type is HS, and discharge date is ‘95’ (STILL IN HOSPITAL) [or if current round is the
final round of the panel (RndType=Final), coded ‘95’ indicates ‘STILL IN HOSPITAL’ and
‘RELEASED IN ’], do not ask the Hospital Stay (HS) section or the Charge/Payment
(CP) section for this event. (We will follow up with these events next round. If current round
is the final round of the panel (RndType=Final), we will obtain necessary information during
the MPC follow- up.)
If event type is IC, and discharge date is ‘95’ STILL IN INSTITUTION’ [or if current round is the
final round of the panel (RndType=Final), code ‘95’ indicates ‘STILL IN INSTITUTION’ and
‘RELEASED IN ’], do not ask the Institutional Care Stay (IC) section for this event (We
will follow up with these events next round. If current round is the final round of the panel
(RndType=Final), we will obtain necessary information during the MPC follow-up.)
If event type is HH, and the HH event was coded as occurring in the current interview
month, CAPI will not ask the HH utilization section for this event, except for when current
round is the final round of the panel (RndType=Final) (We will follow up with these events
next round. If current round is the final round of the panel (RndType=Final), all home health
care events should go through the utilization section because the reference period ends in
December and the interview month is always the next calendar year.)
If CTRL-A is selected, go to Event Roster (EV) section. Once the EV section is complete, return
to ED10. Display added event in chronological order within provider, but the cursor should
go back to where it was before adding the event.
If CTRL-D is selected, display the message: “ARE YOU SURE YOU WANT TO DELETE THIS
EVENT FOR THIS PERSON?” And CAPI provides the options: YES, DELETE or NO. On the popup manipula, CAPI should display the context header information for the event selected.
Once “YES, DELETE” is selected CAPI shows a pop-up dialogue box where a selection must be
made before this deletion is taking place:
WHY ARE YOU DELETING THIS EVENT?
ED - Page 5 of 18
MEPSSpring2024
Full Detail Spec
Event Driver (ED) Section
(Ques
-Need to change event type
-Event is for a different RU member
-Event did not occur
-Need to change the provider
FI’s must select a reason for deleting the event before continuing with
the interview. This data is stored at Event.Event.WhyResponse. If FI
tries to continue without selecting a reason, display the following
error message: “MUST SELECT REASON FOR DELETING EVENT”
If one of the following reasons is selected “Need to change event type,
Event type is for a different RU member, or Need to change the
provider, display the following pop-up manipula box with the
message: “To {change event type/link event to different RU
member/change provider} you must enter the event as new with this
correction. Press 1 to Add event with this update, 2 if new event
already added with update or press 3 to cancel.”
1. Add new event with the update
2. New event already added with update
3. Keep original event as is, nothing deleted
Display “change event” if selected “Need to change event type” at the
Reason for deletion pop-up manipula.
Display “link event to different RU member” if selected ‘Event type is
for a different RU member” at Reason for deletion pop-up manipula.
Display “change provider” if selected “Need to change the provider” at
the Reason for Deletion pop-up manipula.
If coded ‘1’”Add new event with the update” option is selected, go to
BOX_30. If coded 2 ‘New event already added with update’ is selected,
return to ED10.
If code 3 “Keep original event as is, nothing deleted” is selected here,
return to ED10.
This data is stored at Event.Event.HowResponse.
CAPI will not allow the deletion of an event that is linked to a Flat Fee
group. If FI tries to delete a linked event, display the following hard
error message: "THIS EVENT IS LINKED TO A FLAT FEE GROUP AND
CANNOT BE DELETED. IF YOU ENTERED THIS EVENT IN ERROR,
COMPLETE THE UTILIZATION SECTION AND ADD A COMMENT." CAPI
should return to ED10.
If CTRL-E is selected, go to BOX_40. If event type is HH, display the
following error message: “THIS CODE IS NOT AVAILABLE FOR HH
EVENTS. IF CORRECTION NECESSARY, DELETE AND RE-ADD THIS HH
EVENT” And return to ED10.
If CTRL-S is selected, display a pop-up: "INTERVIEWER: SELECT THE RU MEMBER
RESPONDENT WANTS TO DISCUSS NEXT." With an option to cancel to return to the screen
they came from. CTRL-S allows the FI to select another RU member to talk about. Display the
RU members for selection. Next to their name, display the number of events
completed/total number of events for person. For example:
ED - Page 6 of 18
MEPSSpring2024
Full Detail Spec
Event Driver (ED) Section
(Ques
RU MEMBER 1 (5/5 events completed) RU MEMBER 2 (0/5 events completed)
If all events for an RU member have a DONE status, the RU member cannot be selected at
the CTRL-S pop-up. CAPI can display that person, but they should displayed as inactive.
They should have all events completed/total events for that person next to their name and
they should not be selectable. The only way this person can be selected again is if an event is
added for them at ED10. If cycling on the last RU member, and all other RU members’ events
are completed and have a status of DONE, pressing CTRL-S would display all RU members
and they should display as inactive and FI cannot select them.
The completion status of the Event Follow-Up (EF) and Flat Fee (FF) sections, if applicable,
supersedes the “Done” status of C/P. That is, if the EF or FF sections are required and not
completed, set the status of C/P to “Started” or “Not Completed,” whichever is applicable.
CAPI will not allow FI to proceed with interview until these required sections (EF and/or FF)
are completed.
The cursor should display on the first event listed, as described in the loop definition, but FI
can select any event in any order. Once the utilization and charge payment columns have
been completed and display as “Done” in the column, the row should automatically be
grayed out, and the cursor should move to the next event on the grid that needs to be
completed.
For open HS, IC, and HH events, and repeat visit group "leaves" that do not require a
utilization or charge/payment section, once ‘1’ is selected for that event, the event row is
grayed out and the cursor moves to the next event.
Whenever a change is made, Add, delete, edit, the cursor should go back to where it
previously was. When adding an event for a different RU member, CAPI should go back to
the ED screen it was prior to adding the event.
Display
Instructions:
Display "The next few questions...care" if first event to be asked about for this person.
Display “Before continuing with the interview, let’s” if this instance of ED was launched through the
F2, Add/Review Overview button (i.e., launched from OF Section). Otherwise, display “Let’s”.
Display “first” if this instance of ED was launched through the F2, Add/Review Overview button (i.e.,
launched from OF Section). Otherwise, use a null display.
Display “the hospital stay for…” if event type is HS.
Display “when {you/{PERSON}} visited the emergency room…” if event type is ER.
Display “when {you/{PERSON}} received medical care…” if event type is MV.
Display “when {you/{PERSON}} received telehealth care...” if event type is TH.
ED - Page 7 of 18
MEPSSpring2024
Full Detail Spec
Event Driver (ED) Section
(Ques
Display “{DOC OR DEPT} at” if PV70 has a value of 1-N for this person-provider pair and display the
doctor or department selected or added at PV70. Otherwise, use null display.
Display “when {you/{PERSON}} received medical care from {an outpatient department/{DOC OR
DEPT}}…” if event type is OP. Display “{DOC OR DEPT}” if PV70 has a value of 1-N for this
person-provider pair and display the doctor or department selected or added at PV70. Otherwise,
display “an outpatient department”.
Display “when {you/{PERSON}} received dental care…” if event type is DN. Display “the services
{you/{PERSON}} received at home…” if event type is HH. Display “your/{PERSON}’S stay at
{PROVIDER} that began… if event type is IC.
If event type is HS or IC and the discharge date is coded ‘95’ STILL IN HOSPITAL/FACILITY, OR if
event type is HH and the care received was coded during the current interview month display “We will
not ask questions about…” Display “hospital stay” if event type is HS or IC. Display “care received at
home” if event type is HH. Display “that began on {VISIT DATE}” if event type is HS or IC. Display
“for the month of {VISIT MONTH}” if event type is HH.
Display “that we just added for {you/him/her}” if this instance of ED was launched through the F2,
Add/Review Overview button (i.e., launched from OF Section). Otherwise, use a null display.
Display “CTRL-A: ADD NEW EVENT FOR ANYONE” and “CTRL-S: SWITCH TO EVENTS FOR
A DIFFERENT RU MEMBER” if this instance of ED was NOT launched through the F2, Add/Review
Overview button (i.e., not launched through OF Section). Otherwise, use a null display (if this instance
of ED was launched through the F2, Add/Review Overview button).
Format form pane with the following headers:
ED10, RU Member, Event Type, Provider, Date, Repeat Visits, Util, C/P. ED10 is the selection cell; all
other columns are protected and uneditable.
Display RU member’s full name in RU Member column.
Display the abbreviation for the corresponding event type for Event Type column.
For the Provider column, display the provider added or selected at PV20LU. Display “{- DOC OR
DEPT}” if PV70 has a value of 1-N for this person-provider pair and display the doctor or department
selected or added at PV70. If PV70 does not have a value, use a null display.
For the date column, display the event date for MV, DN, OP, and ER events. For HH events, display the
event month. For HS and IC stays, display the start date.
ED - Page 8 of 18
MEPSSpring2024
Full Detail Spec
Event Driver (ED) Section
(Ques
For the Repeat Visit column, display a letter starting with the letter “A” for each repeat visit group.
Allow empty. Set these display rules across the entire RU. These labels will not be retained across
rounds. Note: This field could display one letter, or in a few instance, it could display several variable
pulled from different sources. The column width needs to account for this and should be concatenated.
For repeat visits created in EV (for events where person-provider pairs exceed TBD number of events)
display the range of dates starting with the first date selected to the most recent date selected. Display
the three-letter month abbreviation, the two digit day, and the four digit year with a comma after the
day. For example: Jan 01, 2016 – Dec 12, 2016 with the total number of events shown in parenthesis
after the most recent date displayed, for example Jan 01, 2016 – Dec 12, 2016 (40).
Display status of appropriate utilization section: Not started, Started, Done, and N/A.
Display status of charge payment section: Not started, Started, Done, N/A where, Not started= the
section has not been started
Started= the section has been started but not completed. Display this status if a break-off occurs before
the completion of a section. Done=the section has been completed, flagged as processed and no edits
can be made to the data.
N/A: this section does not apply for this event; such is
the case for OM’s, open HS, IC, and HH events, as
well as HH events where the HH provider's
(HHType=1 or 2) are agency or informal (friends,
relatives, or volunteers)
Display an N/A in the utilization and charge payment
columns on the grid for open HS, IC, and HH events.
Display N/A in the charge payment columns on the
grid for HH events where HHType=1 (agency) or
HHtype=2 (informal). Only HHtype=3 (paid
independent) will go to charge payment as specified
in the CP section.
Display row grayed out and uneditable after C/P
column shows as “Done” or as ‘N/A” as applicable.
For the interviewer instruction “THERE ARE {NUMBER} REMAINING…” display the number of
events that have yet to be completed. By completed, we mean that the utilization and charge payment
sections have been processed and completed and display “Done” in the corresponding columns.
ED - Page 9 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
Display "{{number of events displayed} OUT OF {total number of events} EVENTS SHOWN SCROLL TO SEE MORE}" in red text only when there are more than 8 events for person being looped
on.
Testing/Editing
Notes:
BOX_30
Variable collected at MEPS(Fall/Spring)YYYY.ED_Main.ED_LOOP_20
_TABLE.ED_LOOP_20[1..500]
Variable stored at MEPS(Fall/Spring)YYYY_Event.Event
(ED1026)
Item Type: Route
Type Class: If Then
Route Details:
Ask the Event Roster (EV) section.
At completion of EV section, return to ED10.
Programmer
Instructions:
The EV section, as well as all sections called within EV should present the traditional Blaise
items with the green (instead of beige) background. Any Manipula or other special items
within these sections can remain the original color scheme.
BOX_40
Route Details:
(ED1030)
Item Type: Route
Type Class: If Then
If event type is MV, TH, OP, DN, ER go to ED20.
If event type is HS or IC and event was created in this round (OrigRnd = RoundNumber, go
to ED30_01. If event type is HS or IC and event was created in a prior round (OrigRnd
< RoundNumber), go to ED30_02. The response to ED30_01 will display as grayed out and
uneditable.
ED - Page 10 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
ED20
Item Type:
Type Class:
Answer Type:
(ED1035)
Question
Date
BLAISE NAME: EvntDate
Field kind: Datafield
Field Size:
{Continuous Answer.} Answers allowed: 1
Help Available (EvntDateHelp)
Context Header:
ArrayMin:
Min value:
ArrayMax:
Max value:
Show Card (
)
Look Up File (
)
{PERSON'S FIRST MIDDLE AND LAST NAME} {EVN-DT} {EV} {NAME OF
MEDICAL CARE PROVIDER......} {DOC or DEPT}
Question Text:
DATE ENTERED: {VISIT DATE}
Please tell me the correct date.
SELECT VISIT DATE.
IF RESPONDENT DOESN’T KNOW THE DATES, PRESS F1 FOR A LIST OF PROBES.
HELP: F1
1
Responses:
Programmer
Instructions:
REFUSED (RF) and DON’T KNOW (DK) are not allowed.
Return to ED10 with the date updated for this event.
Hard check: Date entered must be between the person’s reference period begin date
(BegRefM, BegRefD, BegRefY) and the person’s reference period end date (EndRefM,
EndRefD, EndRefY). If a date outside of this range is entered, display the following message:
DATE CANNOT BE AFTER PERSON’S REFERENCE PERIOD END DATE OR BEFORE PERSON’S
REFERENCE PERIOD BEGIN DATE. VERIFY WITH RESPONDENT AND RE-ENTER.”
Display
Instructions:
Testing/Editing
Notes:
Display the date field for visit date.
Variable collected at MEPS(Fall/Spring)YYYY.ED_Main
Variable stored at MEPS(Fall/Spring)YYYY.ED_Main
ED - Page 11 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
ED30_01
Item Type:
Type Class:
Answer Type:
Help Available (
Context Header:
(ED1040)
Question
Date
BLAISE NAME: EvntBegDate
Field kind: Datafield
Field Size:
{Continuous Answer.} Answers allowed: 1
)
Show Card (
ArrayMin:
Min value:
ArrayMax:
Max value:
)
Look Up File (
{PERSON'S FIRST MIDDLE AND LAST NAME} {EV}
Question Text:
DATE ENTERED: {ADMIT DATE}-{DISCHARGE DATE}
Please tell me the correct date, starting with the date {you/{PERSON}} {were/was} admitted to the {hospital/facility}.
SELECT ADMIT DATE.
Responses:
1
ED - Page 12 of 18
)
MEPSSpring2024
Full Detail Spec
Programmer
Instructions:
Event Driver (ED) Section
(Ques
Hard check:
If round 1 only, allow an admit date of one year prior to the start of the person’s reference
period begin date (BegRefM, BegRefD, BegRefY). If a date outside of this range is entered,
display the following message: “UNLIKELY RESPONSE. DATE CANNOT BE MORE THAN A YEAR
PRIOR TO THE PERSON’S REFERENCE PERIOD START DATE. VERIFY WITH RESPONSENT AND
RE-ENTER.”
Admit date cannot be after the person’s reference period end date (EndRefM, EndRefD,
EndRefY). If a date outside of this range is entered, display the following message: “DATE
CANNOT BE AFTER PERSON’S REFERENCE PERIOD END DATE. VERIFY WITH RESPONDENT
AND RE-ENTER.”
Hard check:
If current round is not the first round of the panel (RndType<>First), date entered must be
between person’s reference period begin date (BegRefM, BegRefD, BegRefY) and the
person’s reference period end date (EndRefM, EndRefD, EndRefY). If a date outside of this
range is entered, display the following message: “DATE CANNOT BE AFTER PERSON’S
REFERENCE PERIOD END DATE OR BEFORE PERSON’S REFERENCE PERIOD BEGIN DATE.
VERIFY WITH REPONDENT AND RE-ENTER.”
Display
Instructions:
Testing/Editing
Notes:
Display ED30_01, ED30_02 and ED30_03 on the same form pane. Display the date field for
admittance date. If event was created in a prior round (OrigRnd < RoundNumber), admittance date
should be grayed out and uneditable, with CAPI automatically routing to ED30_02.
Display “hospital” if event type is HS.
For {ADMIT DATE}-{DISCHARGE DATE} display the event date that was entered at EV30
associated with this event.
Variable collected at MEPS(Fall/Spring)YYYY.ED_Main
Variable stored at MEPS(Fall/Spring)YYYY.ED_Main
ED - Page 13 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
ED30_02
Item Type:
Type Class:
Answer Type:
Help Available (
Context Header:
(ED1045)
Question
Date
BLAISE NAME: EvntEndDate
Field kind: Datafield
Field Size:
{Continuous Answer.} Answers allowed: 1
)
Show Card (
ArrayMin:
Min value:
ArrayMax:
Max value:
)
Look Up File (
{PERSON’S FIRST MIDDLE AND LAST NAME} {EV}
Question Text:
DATE ENTERED: {ADMIT DATE}{DISCHARGE DATE}
Please tell me the date {you/{PERSON}} {were/was} discharged from the {hospital/facility}.
SELECT DISCHARGE DATE.IF RU MEMBER IS STILL IN THE HOSPITAL OR FACILITY, PRESS ENTER TO
CONTINUE TO NEXT QUESTION.
1
Responses:
EMPTY
Empty ED30_03
ED - Page 14 of 18
(ED1050)
)
MEPSSpring2024
Full Detail Spec
Programmer
Instructions:
Display
Instructions:
Event Driver (ED) Section
(Ques
Hard check:
If round 1, admit date allowed to be 1 year prior to the start of the person’s reference period.
The discharge date must be after the admit date. If a date outside of this range is entered,
display the following message: “UNLIKELY RESPONSE. DATE MUST BE ON OR
AFTER ADMITTANCE DATE. CONFIRM DATES WITH RESPONDENT.”
The discharge date cannot be after the person’s reference period end date. If a date outside of
this range is entered, display the following message: “DATE CANNOT BE AFTER
PERSON’S REFERENCE PERIOD END DATE. VERIFY WITH RESPONDENT AND
RE-ENTER.”
Hard check:
If current round is not the first round of the panel (RndType<>First), date entered must be
between person’s reference period begin date (BegRefM, BegRefD, BegRefY) and the
person’s reference period end date (EndRefM, EndRefD, EndRefY). If a date outside of this
range is entered, display the following message: “DATE CANNOT BE AFTER PERSON’S
REFERENCE PERIOD END DATE OR BEFORE PERSON’S REFERENCE PERIOD
BEGIN DATE. VERIFY WITH RESPONDENT AND RE-ENTER.
IF DISCHARGED FROM HOSPITAL/FACILITY BEFORE THE REFERENCE PERIOD
START DATE, ENTER THE FIRST DAY OF THE REFERENCE PERIOD AND LEAVE
A COMMENT.”
Hard check: Beginning in Spring 2019, MEPS does not allow the entry of a zero night stay for
any HS or IC event. Only stays of at least one night are allowed. If the discharge date entered
is the same date as the admission date (EvntEndDate=EvntBegDate), display the following
message in black text: “You have entered a stay with the same admit and discharge date.
MEPS defines hospital and institutional stays as requiring at least one night in the facility.”
Verify dates with respondent.
If the person stayed in the hospital/facility overnight:
1. Correct the admit/discharge dates.
If the person was seen on this day for outpatient treatment or did not stay at least one night:
1. Back-up to ED20.
2. Delete this event.
3. Re-add event as an OP event.
Display ED30_01, ED30_02, and ED30_03 on the same form pane.
Display the empty date field for entry.
Display the current admit and discharge date for the HS/IC event for “DATE ENTERED…”
Display “hospital” if event type is HS.
Display “facility” if event type is IC.
Testing/Editing
Notes:
Variable collected at MEPS(Fall/Spring)YYYY.ED_Main
Variable stored at MEPS(Fall/Spring)YYYY.ED_Main
ED - Page 15 of 18
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
ED30_03
Item Type:
Type Class:
Answer Type:
Help Available (
Context Header:
(ED1050)
Question
Enumerated
TSTILLHOSPFAC
)
BLAISE NAME: StillInHSIC
Field kind: Datafield
ArrayMin:
Min value:
Field Size:
Answers allowed: 1
ArrayMax:
Max value:
Show Card (
)
Look Up File (
{PERSON’S FIRST MIDDLE AND LAST NAME} {EV}
Question Text:
DATE ENTERED: {ADMIT DATE}{DISCHARGE DATE}
Please tell me the date {you/{PERSON}} {were/was} discharged from the {hospital/facility}.
ENTER DISCHARGE DATE.
Responses:
STILL IN {HOSPITAL/FACILITY}
EMPTY
1
Empty
ED - Page 16 of 18
)
MEPSSpring2024
Event Driver (ED) Section
(Ques
Full Detail Spec
Programmer
Instructions:
REFUSED (RF) and DON’T KNOW (DK) are not allowed. If FI tries to code RF or DK,
display the following message: “THAT CODE IS NOT ALLOWED AT THIS SCREEN.
BACK UP TO ENTER DISCHARGE DATE.”
Allow empty. ED30_02 is optional, but either ED30_02 or ED30_03 must be coded to move
on. If both are empty, display the following message: “YOU MUST MAKE A SELECTION.
TO ENTER A DISCHARGE DATE BACK UP TO ED30_02 (EvntEndDate). TO SELECT
STILL IN {HOSPITAL/FACILITY} PRESS 1 AND ENTER TO CONTINUE.”
Go back to ED10.
If coded ‘1’ (STILL IN HOSPITAL/FACILITY), event is not closed in the current round.
Flag event as processed and flag charge payment as processed. Write correction to the
person’s-medical-events-roster.
Display
Instructions:
Display ED30_01, ED30_02, and ED30_03 on the same form pane.
Display the date field for discharge date. Pressing the ALT + down arrow key, will bring up
the pop- up calendar defaulted to display the month the interview is taking place. The
interviewer may also manually enter the date.
Pressing enter to continue will take the FI to the next screen.
Display the current admit and discharge date for the HS/IC event for “DATE ENTERED…”
Display “hospital” if event type is HS.
Display “facility” if event type is IC.
Display HOSPITAL in response pane if event type is HS.
Display FACILITY in response pane if event type is IC.
For {ADMIT DATE}-{DISCHARGE DATE} display the event date that was entered at EV30
associated with this event.
Testing/Editing
Notes:
END_LP20
Route Details:
Variable collected at MEPS(Fall/Spring)YYYY.ED_Main
Variable stored at MEPS(Fall/Spring)YYYY.ED_Main
(ED1055)
Item Type: Route
Type Class: End Loop
Go to the next event for this person that meets the criteria as stated in LOOP_20.
Once the statuses of the utilization and charge payment section for each event has been
completed, end loop and go to END_LP10.
ED - Page 17 of 18
MEPSSpring2024
Event Driver (ED) Section
(Rout
Full Detail Spec
END_LP10
Route Details:
(ED1060)
Item Type: Route
Type Class: End Loop
Go to the next RU member that meet the criteria as stated in LOOP_10.
Once all the RU members that meet the criteria in the loop definition, end loop and go to
BOX_50.
BOX_50
Route Details:
(ED1065)
Item Type: Route
Type Class: If Then
End of Event Driver (ED) section. If ED launched from Off Path section, return to OF
section. Otherwise, go to Prescribed Medicines (PM) section.
[End of ED]
ED - Page 18 of 18
File Type | application/pdf |
File Title | rptFullDetail_Item |
Author | Rebecca Hughes |
File Modified | 2023-10-20 |
File Created | 2023-10-20 |