Title: Tester: Product: Focus: Revisions: Test Assumptions:
BENCHMARK REPORTS Acceptance Criteria Dong Tran OCS Oasis Benchmark Reports Do reports and all apps perform the minimum necessary criteria.
Windows 95 and Windows 98 only.
Functional Area
Switchboard, General
ID SBGRL01 SBGRL02 SBGRL03 SBGRL04 SBGRL05 SBGRL06 SBGRL07 SBGRL08 SBGRL09 SBGRL10 SBGRL11 SBGRL12 SBGRL13 SBGRL14 SBGRL15 SBVER01 SBVER02 SBVER03 SBVER04 SBVER05 SBVER06 SBVER07 SBVER08
Spec ID
Business Rule Verify clicking Start Polling button forces selected tasks to startup Verify clicking Stop Polling button forces all processes to stop Verify "PollingPauseInSeconds" Verify "PollingQueuLogEveryOther" Verify "DateStartPer" and "DateEndPer" date range to verify and upload. Verify MDB File In - Verification at "…\OasisIncomingFiles\1_Raw" dir Verify MDB File In - Renamed source files to Batchnnnnnn Verify MDB File In - Fail verification, left in the "...\X_Errors" directory. Verify MDB File In - Pass verification, put in the "…\2_Verified" dir. Verify MDB File In - Upload at "…\OasisIncomingFiles\2_Verified" dir. Verify MDB File In - Fail upload, left in the "…\X_Errors" directory. Verify MDB File In - Pass upload, put in the "…\3_Completed" directory. Verify property 'MachineID' used to distinguish switchboard clients. Verify ability to process multiple files Verify multiple switchboards running simultaneously Verify depressed verification button forces verification to occur Verify un-depressed verification button forces verification not to occur Verify Missing Field Structure Verification Verify New Field Structure Verification Verify Changed Field Type Structure Verification Verify Changed Field Size Structure Verification Verify Checks which Tables Structure Verification Verify New Agency Structure Verification P/F P P P
P P P P P P P P P P P P P P P P P
Switchboard Verification
Functional Area
ID SBUP01 SBUP02 SBUP03 SBUP04 SBUP05 SBUP06 SBUP07 SBUP08 SBUP09 SBUP10
Spec ID
Business Rule Verify depressed upload button forces upload to occur Verify un-depressed upload button forces upload not to occur Verify forced logging upload results Verify *no* forced logging upload results Verify upload of recent update *inside* submittal period of recs outside submittal period. Verify upload of recent update *outside* submittal period of recs outside submittal period. Verify record count "# Submitted: Total Records Submitted" Verify record count "# Fail [NV]: Not Verified Records" Verify record count "# Fail [BD]: Bad Dates" Verify record count "# Fail [NM]: No Matching Dischrg Rec This Period" Verify record count "# Fail [SP]: Discharge Rec Outside Subm`l Period" Verify record count "# Fail [DD]: Complete Records w/o Discharge Date" Verify record count "# Fail [DA]: Complete Records w/ Duplicate Assessment`s" Verify record count "# Pass [All]: Complete Records" P P P P P P P P P/F P P
Switchboard Upload
SBUP11 SBUP12 SBUP13 SBUP14
SBUP15 SBUP16 SBUP17 SBUP18 SBUP19 SBUP20 SBUP21 DAUPL01 DAUPL02 DAUPL03 Data Analyst Tool, Upload Wizard DAUPL04 DAUPL05 DAUPL06 DAUPL07 DAUPL08 DAUPL09
Verify record count "--># Pass [##A8]: Old, but Recently Modified Recs" Verify episode counts for Outlier record counts above (SWBD21-29) Verify identifiers removed Verify data uploaded to WareHouse & reccounts match Verify overwrite existing data Verify no *truncation* (fields clipped) in tables Assess1-8, Assessment_Verification, and Demographics Verify no *omissions* in tables Assess1-8, Assessment_Verification, and Demographics Verify cancel operation Verify ODBC DSN check Verify missing Medicare Provider Number check Verify REF_Agency can be loaded Verify REF_AgencyChar can be loaded Verify REF_AgencyContact can be loaded Verify REF_Agency can be updated Verify REF_AgencyChar can be updated Verify REF_AgencyContact can be updated
P F P P P
P P F P F F
Functional Area
ID DABMD001 DABMD002 DABMD003 DABMD004 DABMD005 DABMD006 DABMD007 DABMD008 DABMD009 DABMD010 DABMD011 DABMD012 DABMD013 DABMD014 DABMD015 DABMD016 DABMD017 DABMD018 DABMD019 DABMD020
Spec ID
Business Rule Verify Calculate Norms Now! button works on single BM_ID Verify Calculate Norms Now! button works on all BM_Ids Verify cancel operation Verify All National Norm domain (all agencies included) Verify All System Norm domain (correct agencies included) Verify All Region Norm domains (correct agencies included) Verify All Agency Aggregate Calc domains (single agencies only included) Verify Specific System Norm domain (correct agencies included) Verify Specific Region Norm domain (correct agencies included) Verify Specific Agency Aggregate Calc domains (single agencies only included) Verify Date Range - Year Verify Date Range - Year Quarter Verify Date Range - Year Month Verify Date Range - Start/End Date Verify Calculate Norms Now! Checkbox Verify table "BM_Batch", field "Name" Verify table "BM_Batch", fields "DateStartPer" and "DateEndPer" are appropriate for quarter, month, etc. selected Verify table "BM_Batch", field "NbrBMDefinitions" count Verify table "BM_Definition", field "BM_Type" Verify repeat run of benchmark batches over the top of existing runs P/F P P P P P P P P P P P P P P P P P P P
Data Analyst, Benchmark Definition Wizard
DABMD021 DABMD022 DABMD023
Verify table "BM_Definition", fields "BM_Batch_ID", "DateStartPer", and "DateEndPer" Verify table "BM_Definition", fields "Name", and "ShortName" Verify table "BM_Definition", fields "National", "OCSSystemID", "OCSRegion", and "ServiceLine_ID"
P P P
DABMD024 DABMD025 DABMD026
Verify table "BM_Definition", fields "M0010" Verify table "BM_Definition", field "DateLastCalculated" Verify table "BM_Definition", field "CalcProcessingTime"
P P P
Functional Area
ID DABMD027
Spec ID
Business Rule Verify table "BM_Definition", field "NumberMeasuresCalculated" P/F P
Functional Area
ID DABMD028 DABMD029
Spec ID
Business Rule Verify table "BM_Definition", field "NumberAgenciesCalculated" Verify table "BM_Definition", field "NumberEpisodesCalculated" P/F P P
DABMD030
Verify table "BM_Definition", field "FlagStatus"
P
DABMD031 DABMD032 DABMD033 DABMD034 DABMD035 DABMD036 DABMD037 DABMD038 DABMD039 DABMD040 DABMD041 DABMD042 DABMD043 DABMD044 DABMD045 DABMD046 DABMD047 DABMD048 DABMD049 DABMD050 DABMD051 DABMD052 DABMD053 DABMD054 DABMD055
Verify table "BM_Definition", field "FlagActive" is not used at this time Verify table "BM_Definition", field "FlagCalcStdRpt" Verify table "BM_Definition", field "FlagDBSummary" Verify table "BM_Definition", fields "FlagCalcOther1" and "FlagCalcOther2" are not used at this time Verify table "BM_MeasureArea" field "Name" spelling Verify table "BM_MeasureArea" field "MeasureArea_Code" M0xxx areas matchup with OASIS questions Verify table "BM_MeasureArea" field "MeasureArea_Code" DBxxxx areas matchup with Agency Characteristic questions Verify table "BM_Measure" field "Name" spelling Verify table "BM_Measure" field "Measure_ID" M0xxx areas matchup with OASIS questions Verify table "BM_Measure" field "Measure_ID" DBxxxx areas matchup with Agency Characteristic questions Verify table "BM_AgencyConstraintList" filters agencies used in norm calcs Verify table "BM_Norm" field "Measure_ID" codes all exist in the "BM_Measure" table Verify table "BM_Norm" field "NumberCases" Verify table "BM_Norm" field "Denominator" Verify table "BM_Norm" field "Numerator" Verify table "BM_Norm" field "ObservedRate" Verify table "BM_Norm" fields "RiskAdjRate", … Verify additive synchronization of multiple Norm calculation runs Verify Measure ID DS1000.01 - Rural Verify Measure ID DS1000.02 - Urban Verify Measure ID DS1000.03 - Suburban Verify Measure ID DS1100.01 - 100,000 visits P P P P P P P P P P P P P P F P P P P P P P
Data Analyst, Benchmark Definition Wizard (Cont)
Functional Area
Data Analyst, Benchmark Definition Wizard (Cont)
ID DABMD056 DABMD057 DABMD058 DABMD059 DABMD060 DABMD061 DABMD062 DABMD063 DABMD064 DABMD065 DABMD066 DABMD067 DABMD068 DABMD069 DABMD070 DABMD071 DABMD072 DABMD073 DABMD074 DABMD075 DABMD076 DABMD077 DABMD078 DABMD079 DABMD080 DABMD081 DABMD082 DABMD083 DABMD084 DABMD085 DABMD086 DABMD087 DABMD088 DABMD089 DABMD090 DABMD091 DABMD092 DABMD093 DABMD094 DABMD095
Spec ID
Business Rule P/F Verify Measure ID DS1110.01 - =50 employees Verify Measure ID DS1120.01 - 1 only Verify Measure ID DS1120.02 - 2-5 Verify Measure ID DS1120.03 - > 5 Verify Measure ID DS1200.01 - Voluntary Verify Measure ID DS1200.02 - Private Verify Measure ID DS1200.03 - Government Verify Measure ID DS1200.04 - Gov/Voluntary Verify Measure ID DS1200.05 - Publicly-Held Verify Measure ID DS1210.01 - No controlling org Verify Measure ID DS1210.02 - Hospital Verify Measure ID DS1210.03 - National company Verify Measure ID DS1210.04 - Nursing home Verify Measure ID DS1210.05 - Other institution Verify Measure ID DS1210.06 - Health department Verify Measure ID DS1210.07 - Health plan Verify Measure ID DS1210.08 - Health system Verify Measure ID DS1210.09 - Other Verify Measure ID DS1220.01 - Not-for-profit Verify Measure ID DS1220.02 - Proprietary Verify Measure ID DS1300.01 - Medicare-certified Verify Measure ID DS1300.02 - Medicaid-certified Verify Measure ID DS1310.01 - CHAP Verify Measure ID DS1310.02 - JCAHO Verify Measure ID DS1310.03 - National HomeCaring Verify Measure ID DS1310.04 - ACHC Verify Measure ID DS1320.01 - Home care license Verify Measure ID DS1320.02 - Hospice license Verify Measure ID DS1320.03 - Other license Verify Measure ID DS1320.04 - Not required Verify Measure ID DS1400.01 - Nursing Verify Measure ID DS1400.02 - Home Care Aide Verify Measure ID DS1400.03 - Physical Therapy Verify Measure ID DS1400.04 - Occupational Therapy Verify Measure ID DS1400.05 - Speech-Language Verify Measure ID DS1400.06 - Social Service Verify Measure ID DS1400.07 - Respiratory Therapy P P P P P P P P P P P P
P P P P P P P P P P P P P P P P P P P
Functional Area
Data Analyst, Benchmark Definition Wizard (Cont)
ID DABMD096 DABMD097 DABMD098 DABMD099 DABMD100 DABMD101 DABMD102 DABMD103 DABMD104 DABMD105 DABMD106 DABMD107 DABMD108 DABMD109 DABMD110 DABMD111 DABMD112 DABMD113 DABMD114 DABMD115 DABMD116 DABMD117 DABMD118 DABMD119 DABMD120 DABMD121 DABMD122 DABMD123 DABMD124 DABMD125 DABMD126 DABMD127 DABMD128 DABMD129 DABMD130 DABMD131 DABMD132 DABMD133 DABMD134 DABMD135
Spec ID
Business Rule Verify Measure ID DS1400.08 - Dietician Service Verify Measure ID DS1400.09 - Pastoral Care Verify Measure ID DS1400.10 - Volunteer Verify Measure ID DS1400.11 - Physician Care Verify Measure ID DS1400.12 - Dental Care Verify Measure ID DS1400.13 - Pharmacy Verify Measure ID DS1400.14 - Expressive Therapy Verify Measure ID DS1400.15 - Other Verify Measure ID DS1400.16 - Private Duty Nurse Verify Measure ID DS1400.17 - Interpreter Verify Measure ID DS1400.18 - Security Verify Measure ID DS1400.19 - Long Term Care Verify Measure ID DS1500.01 - AIDS Verify Measure ID DS1500.02 - Cardiopulmonary Verify Measure ID DS1500.03 - Case Management Verify Measure ID DS1500.04 - Diabetic Verify Measure ID DS1500.05 - Enterostomal Therapy Verify Measure ID DS1500.06 - Geriatrics Verify Measure ID DS1500.07 - Hospice Verify Measure ID DS1500.08 - Infusion Therapy Verify Measure ID DS1500.09 - Maternal/Child Verify Measure ID DS1500.10 - Oncology Verify Measure ID DS1500.11 - Pediatric Verify Measure ID DS1500.12 - Psych/Mental Health Verify Measure ID DS1500.13 - Rehab Verify Measure ID DS1500.14 - Respite Care Verify Measure ID DS1500.15 - Other Verify Measure ID M0150.01 - Medicare, Traditional Verify Measure ID M0150.02 - Medicare, HMO Verify Measure ID M0150.03 - Medicaid, Traditional Verify Measure ID M0150.04 - Medicaid, HMO Verify Measure ID M0150.05 - Other Verify Measure ID M0150.06 - Private Insurance Verify Measure ID M0150.07 - Private HMO/Mgmt Care Verify Measure ID M0230.01 - Circulatory Verify Measure ID M0230.02 - Endocrine Disease Verify Measure ID M0230.03 - Gastrointestinal Verify Measure ID M0230.04 - Injury/Poisoning Verify Measure ID M0230.05 - MusculoSkeletal Verify Measure ID M0230.06 - Neoplasm P/F P P P P P P P P P P P
P P P P P P P P P P P P P P P P P P P P P
Functional Area
Data Analyst, Benchmark Definition Wizard (Cont)
ID DABMD136 DABMD137 DABMD138 DABMD139 DABMD140 DABMD141 DABMD142 DABMD143 DABMD144 DABMD145 DABMD146 DABMD147 DABMD148 DABMD149 DABMD150 DABMD151 DABMD152 DABMD153 DABMD154 DABMD155 DABMD156 DABMD157 DABMD158 DABMD159 DABMD160 DABMD161 DABMD162 DABMD163 DABMD164 DABMD165 DABMD166 DABMD167 DABMD168 DABMD169 DABMD170 DABMD171 DABMD172 DABMD173 DABMD174 DABMD175
Spec ID Verify Measure ID M0230.07 - Respiratory Verify Measure ID M0230.99 - Other Verify Measure ID M0260.01 - Poor Verify Measure ID M0260.02 - Good/Fair Verify Measure ID M0260.03 - Unknown Verify Measure ID M0410.01 - Improved Verify Measure ID M0410.02 - Stabilized Verify Measure ID M0420.01 - Improved Verify Measure ID M0420.02 - Stabilized Verify Measure ID M0464.01 - Improved Verify Measure ID M0464.02 - Stabilized Verify Measure ID M0488.01 - Improved Verify Measure ID M0488.02 - Stabilized Verify Measure ID M0490.01 - Improved Verify Measure ID M0490.02 - Stabilized Verify Measure ID M0520.01 - Improved Verify Measure ID M0520.02 - Stabilized Verify Measure ID M0540.01 - Improved Verify Measure ID M0540.02 - Stabilized Verify Measure ID M0560.01 - Improved Verify Measure ID M0560.02 - Stabilized Verify Measure ID M0570.01 - Improved Verify Measure ID M0570.02 - Stabilized Verify Measure ID M0640.01 - Improved Verify Measure ID M0640.02 - Stabilized Verify Measure ID M0650.01 - Improved Verify Measure ID M0650.02 - Stabilized Verify Measure ID M0660.01 - Improved Verify Measure ID M0660.02 - Stabilized Verify Measure ID M0670.01 - Improved Verify Measure ID M0670.02 - Stabilized Verify Measure ID M0680.01 - Improved Verify Measure ID M0680.02 - Stabilized Verify Measure ID M0690.01 - Improved Verify Measure ID M0690.02 - Stabilized Verify Measure ID M0700.01 - Improved Verify Measure ID M0700.02 - Stabilized Verify Measure ID M0710.01 - Improved Verify Measure ID M0710.02 - Stabilized Verify Measure ID M0720.01 - Improved
Business Rule P/F
P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P
Functional Area
Data Analyst, Benchmark Definition Wizard (Cont)
ID DABMD176 DABMD177 DABMD178 DABMD179 DABMD180 DABMD181 DABMD182 DABMD183 DABMD184 DABMD185 DABMD186 DABMD187 DABMD188 DABMD189 DABMD190 DABMD191 DABMD192 DABMD193 DABMD194 DABMD195 DABMD196 DABMD197 DABMD198 DABMD199 DABMD200 DABMD201 DABMD202 DABMD203 DABMD204 DABMD205 DABMD206 DABMD207 DABMD208 DABMD209
Spec ID
Business Rule Verify Measure ID M0720.02 - Stabilized Verify Measure ID M0740.01 - Improved Verify Measure ID M0740.02 - Stabilized Verify Measure ID M0750.01 - Improved Verify Measure ID M0750.02 - Stabilized Verify Measure ID M0760.01 - Improved Verify Measure ID M0760.02 - Stabilized Verify Measure ID M0770.01 - Improved Verify Measure ID M0770.02 - Stabilized Verify Measure ID M0780.01 - Improved Verify Measure ID M0780.02 - Stabilized Verify Measure ID M0810.01 - Improved Verify Measure ID M0810.02 - Stabilized Verify Measure ID M0830.01 - Yes Verify Measure ID M0830.02 - No Verify Measure ID M0855.01 - Hospital Verify Measure ID M0855.02 - Rehab Facility Verify Measure ID M0855.03 - Nursing Home Verify Measure ID M0855.04 - Hospice Verify Measure ID M0855.05 - NA Verify Measure ID M0870.01 - In Community Verify Measure ID M0870.02 - To Hospice Verify Measure ID M0870.03 - Unknown Verify Measure ID M0870.04 - Other Verify Measure ID O0040 - Health (O0040) Verify Measure ID O0050 - Knowledge (O0050) Verify Measure ID O0060 - Skill (O0060) Verify Measure ID O0070 - Psychosocial (O0070) Verify Measure ID RH1000 - Number of Agencies (sample size) Verify Measure ID RH1010 - Number of Patients (sample size) Verify Measure ID RH2000 - Discharges per Agency Verify Measure ID RH2010 - LOS in Home Care Verify Measure ID RH2020 - Visits per Case Verify "REF_Properties" table, "BMCalcMinAgenciesRequired" field P/F P P P P P P P F F P P P P P P P P P P P P P P P P F F F P P P P P
Functional Area
ID BMRPT001 BMRPT002 BMRPT003 BMRPT004 BMRPT005 BMRPT006 BMRPT007 BMRPT008 BMRPT009 BMRPT010 BMRPT011 BMRPT012 BMRPT013 BMRPT014 BMRPT015 BMRPT016 BMRPT017 BMRPT018 BMRPT019 BMRPT020 BMRPT021 BMRPT022 BMRPT023 BMRPT024 BMRPT025 BMRPT026 BMRPT027 BMRPT028 BMRPT029 BMRPT030 BMRPT031 BMRPT032 BMRPT033 BMRPT034 BMRPT035
Spec ID
Business Rule Verify "Standard" batch report type Verify "Run Reports Only" batch report type Verify ability to setup RPT_Definition rec and print report "Title Page" Verify ability to setup RPT_Definition rec and print report "JCAHO Reports" Verify ability to setup RPT_Definition rec and print report "Data Integrity Reports" Verify ability to setup RPT_Definition rec and print report "Benchmark Utilitization Reports" Verify ability to setup RPT_Definition rec and print report "Clinical Indicators Reports" Verify ability to setup RPT_Definition rec and print report "Service Line Reports" Verify ability to setup RPT_Definition rec and print report "Database Summary Reports" Verify ability to setup RPT_Definition rec and print report "Case Mix Reports" Verify batch selection filter Verify agency selection list filter Verify "Output Reports Now" checkbox feature Verify "Continuous Loop for Testing" checkbox feature Verify ability to email reports to override address Verify ability to set message body text of email from app Verify that email default is sent to contact target Verify that emails can be automatically sent to multiple contact targets Verify that reports can be printed as output type Verify that reports can be previewed as output type Verify that reports can be built as html files Verify that html reports are put into correct directories Verify that html reports have index.html files added that function as starting point for viewing Verify report creation performance for printed output Verify report creation performance for html files Verify stress test of html files (48-72 hour runs) Verify stress test of print (print to file, NOT to paper) (48-72 hour runs) Verify stress test of emailed reports (48-72 hour runs) Verify table "RPT_Definition" field "WH_Batch_ID" Verify table "RPT_Definition" field "RPT_Type_ID" Verify table "RPT_Definition" field "Name" Verify table "RPT_Definition" field "ServiceLine_ID" Verify table "RPT_Definition" field "Org_BM_ID" Verify table "RPT_Definition" field "CG1_BM_ID" Verify table "RPT_Definition" field "CG2_BM_ID" P/F P P P P P P P P P P P P P X X X X P P X X X P X X X P P P P P P
Benchmark Report Execution Wizard
Functional Area
ID BMRPT036 BMRPT037
Spec ID Verify table "RPT_Definition" field "CG3_BM_ID"
Business Rule P/F
Verify table "RPT_Definition" field "CG4_BM_ID" - "CG9_BM_ID"
BMRPT038 BMRPT039 BMRPT040 BMRPT041 BMRPT042 Benchmark Report Execution Wizard (Cont) BMRPT043 BMRPT044
Verify table "RPT_Definition" field "DateLastPrinted" Verify table "RPT_Definition" field "PrintProcessingTime" Verify table "RPT_Definition" field "FlagStatus" Verify table "RPT_Definition" field "FlagActive" Verify columns on reports to be: MeasureID, JCAHOID, MeasureName, AgencyValue, National, System, and Region Verify System and Region columns have identifiers indicating System Name and Region Name Verify 10% Statistical Significance flag (* note on the reports)
P P P P P
BMRPT045 BMRPT046 BMRPT047 BMRPT048 BMRPT049 BMRPT050 BMRPT051 BMRPT052 BMRPT053 BMRPT054 Pass: Fail: Removed: Not Tested: Total: 246 10 11 49 316
Verify 5% Statistical Significance flag (** note on the reports) Verify that % values are all rounded accurately up or down Verify that printed reports and print preview reports have fancy formatting with lines, boxes and shading, logo… Verify that emailed reports and html reports are plain (no logos, etc.) but look good Verify random sample of Measure_Ids that Measure_Name is correct Verify random sample of JCAHO_Ids that Measure_Name is correct Verify Page Number field Verify Report Date field Verify subtitles in MeasureName field are all in bold (and have dividing line for printed and preview output modes) Verify that standard reports (except database summary, and now service line reports) all fit on single page
78% 3% 3% 16%
P X P P P P P
ID
SBGRL01 SBGRL02 SBGRL03 SBGRL04 SBGRL05 SBGRL06 SBGRL07 SBGRL08 SBGRL09 SBGRL10 SBGRL11 SBGRL12 SBGRL13 SBGRL14 SBGRL15 SBVER01 SBVER02 SBVER03 SBVER04 SBVER05 SBVER06 SBVER07 SBVER08 *but* only after current process has completed
Details
"PollingPauseInSeconds" property of table "tbl_Properties_Local" sets pause in seconds that polling events wait between subsequent iterations. (Default = 1, try setting to 30 seconds.) "PollingQueuLogEveryOther" property of table "tbl_Properties_Local" sets number of polling attempts that are *not* logged for every one that is logged. "DateStartPer" and "DateEndPer" property of table "tbl_Properties" specifies the date range to upload. Be sure to set this every time you run the switchboard. (Buggit…should be text boxes on form.) Incoming source mdb files are manually (or via other application) placed in the "…\OasisIncomingFiles\1_Raw" directory and are only picked up if the Verification button is depressed when Swbd is run. Incoming source mdb files are renamed Batchnnnnnn where nnnnnn is the next sequential batch number as looked up in the WH_Batch table. Source mdb files that fail verification are left in the "…\OasisIncomingFiles\X_Errors" directory. Source mdb files that pass verification are put in the "…\OasisIncomingFiles\2_Verified" directory. If the Upload button is depressed when Swbd is run, then files in the "…\OasisIncomingFiles\2_Verified" directory are uploaded to the SQL Server warehouse (one at a time). Source mdb files that have errors during upload are left in the "…\OasisIncomingFiles\X_Errors" directory. Source mdb files that have no errors during upload are put in the "…\OasisIncomingFiles\3_Completed" directory. Check switchboard machine id in Options. Name should be used to stamp MachineID in Event Log. Switchboard should be able to process multiple files in a row (from same 1_Raw directory all the way through system). Switchboard should be able to handle multiple switchboards running Verification, but only one at a time running the Upload process. Property 'AssignedTaskOASIS_01_Verification' forces Switchboard to perform post verification checks on incoming Oasis.mdb. (Be sure that Upload option is set to No.) If set to Yes in Options, then app should pickup mdb's from the 1_Raw folder, work on them in the X_Errors folder, and when finished verifying move them to the 2_Verified folder. Structural post verification check should identify missing fields from incoming mdb and flag results in table: '_ERROR: Missing or Incorrect Fields' Structural post verification check should identify new fields from incoming mdb and flag results in table: '_ERROR: Fields Unrecognized' Structural post verification check should identify field type changes from incoming mdb and flag results in table: '_ERROR: Missing or Incorrect Fields' Structural post verification check should identify field size changes from incoming mdb and flag results in table: '_ERROR: Missing or Incorrect Fields' Post verification should spot the field issues above for the following tables: Assess1, Assess2, Assess3, Assess4, Assess6, Assess7, Assess8, Demographics, and Assessment_Verify. Post verification should spot new agencies that have not yet been entered into the table AgencyChar. This check precludes a failure in SQL Server stored proc execution.
ID
SBUP01 SBUP02 SBUP03 SBUP04 SBUP05 SBUP06 SBUP07 SBUP08 SBUP09 SBUP10 SBUP11 SBUP12 SBUP13 SBUP14
Details Property 'AssignedTaskOASIS_02_Upload' forces Switchboard to perform upload of post-verified data. (Execute this after executing Issue #2 above.) If set to Yes in Options, then app should pickup mdb's from the 2_Verified folder, work on them in the X_Errors folder, and when finished uploading to SQL Server and processing; then move the files to the 3_Completed folder. Property 'DebugOASISImportVerify' when set to Yes will post multiple temp tables into the incoming oasis.mdb for debugging purposes. App should add _##outliers table, _##DataReport, _##Incomplete_Recs, and _##RecentUpdatesWithDischarge tables. "DebugOASISImportVerify" property of table "tbl_Properties_Local" set to "no" will force upload process to *not* log anything back to source .mdb. Verify recently updated records are uploaded for completed episodes (set of M0010/M0020/M0030 with one rec M0100 = 6 or 8)."__##RecentUpdatesWithDischarge" debug table rec keys match test rec in Assess8 with DateChange field set within the pull-date for Swbd. Verify that updated recs outside of pull date are *not* uploaded (see SWBD19). Verify record count "# Submitted: Total Records Submitted" (code 1000 of _##DataReport) -- lookup # recs in Assessment_Verification Verify record count "# Fail [NV]: Not Verified Records" (code 1100 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'NV' vs. query count of Assessment_Verification Verified field flag not set. Verify record count "# Fail [BD]: Bad Dates" (code 1110 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'BD' vs. query count of M0030, M0090, and M0906_1 that are not dates but also are not null. Verify record count "# Fail [NM]: No Matching Discharge Rec This Period" (code 1120 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'NM' vs. query count of recs inside of non-discharged episodes (so if soc rec + 2 recerts, but no discharge rec, then know that 3 recs flagged NM). Verify record count "# Fail [SP]: Discharge Rec Outside Subm`l Period" (code 1130 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'SP' vs. query count of recs whose discharge rec M0090 is outside of submittal period. Note that if [Assess8].[DateChange] is modified, that fact overrides this check. Verify record count "# Fail [DD]: Complete Records w/o Discharge Date" (code 1140 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'DD' vs. Assess4 recs where M0906_1 discharge date is null and record is M0100 type 6 or 8 (discharge). Verify record count "# Fail [DA]: Complete Records w/ Duplicate Asst`s" (code 1150 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'DA' vs. query count of recs with matching M0010, M0020, M0030, and M0100, but different M0090 (these multiple soc's should have a second, newer M0030 to start a new episode, or be a recert or and edit to an existing soc a few days later) Verify record count "# Pass [All]: Complete Records" (code 1200 of _##DataReport) -- query count of "__##Outlier" where Outlier field = 'IL' Everything remaining that has not been flagged an outlier above is now flagged as an inlier. Also, if previously flagged as SP but the record has recent updates then those recs are marked IL and pulled forward. (Note, if discharge is pulled, then all SOC and interim recs associated are also pulled at this time since chances are were ommitted last quarter as NM.) Verify record count "--># Pass [##A8]: Old, but Recently Modified Recs" (code 1260 of _##DataReport) -- query count of "__##Outlier" where Outlier field = IL, but Assess8 Change Date was inside of submittal per. Verify episode counts for Outliers done above by cross-checking _##DataReport codes 1400-1499 against distinct count of _##Outlier table results with only fields M0010/M0020/M0030 so get one episode per count and group by Outlier code (e.g.: IL, SP, etc.) Resulting counts should exactly match. Be sure that all M0020 codes (patient ids), M0063, M0064, M0065, and M0040_x have been scrambled or encrypted in final NDR tables (all Assess and Demographics tables). Be sure that upon completion, all data is moved out of temp tables and into final tables. Be sure that old data that is re-processed is written over the top of by the newer incoming data. Be sure that all field values from the source database are copied up to their corresponding fields in SQL Server and were not truncated in length. Be sure that all field values from the source database are copied up to their corresponding fields in SQL Server and were not omitted or left blank. Be sure that user can cancel out of wizard any time prior to hitting Finish and exit without altering anything. Check REF_Agency, REF_AgencyChar, and REF_AgencyContact to be sure no records have changed (rec counts the same, values unchanged, etc.) Temporarily rename your ODBC DSN's (both of them, then one at a time) to be sure that the DSN check accurately detects the missing DSN (goto ODBC32 bit Administrator to setup the test). All clients must have a medicare provider number to be used as the M0010 portion of the primary key. This check ensures that the incoming internal application data for agencies isn't missing M0010 codes (new customers, non-paying customers, etc.) Just look at what happens to recs missing M0010 codes and see how they are handled...should get warning, and if agency exists, but no M0010, then OCSID with prefix of 'X' is stamped in as temporary default M0010...then, when record finally gets an M0010, re-running the wizard will pull across the correct M0010 code. First time run will populate REF_Agency. Be sure values in all columns exactly match corresponding values in linked input table 'Agency_Characteristics' First time run will populate REF_AgencyChar. Be sure that new recs per agency exactly match what used to be columns in the input table 'Agency_Characteristics'. To cross-reference the old column names to the new values in the field Measure_ID (e.g.: "DS1000.01"), lookup the values in RPT_Measure table which is *not* attached...you need to goto SQL Server to look it up, or temporarily link in the table. Spend lots of time here thoroughly checking all Measure_IDs to be sure they are correct. Should take 4-8 hours. First time run will populate REF_AgencyContact. Be sure that all contacts from the 'Prospect_Contacts' table (linked in from internal application) that are of a contact_type of 8 (BM_Oasis) are uploaded to the table. Other contact persons must be ignored and not uploaded. Subsequent runs (re-run after first) should update existing values in REF_Agency. Put in a few new values and be sure they are uploaded…then immediately undo the changes since you are working on live data. Subsequent runs (re-run after first) should update existing values in REF_AgencyChar. Put in a few new values and be sure they are uploaded…then immediately undo the changes since you are working on live data. Subsequent runs (re-run after first) should update existing values in REF_AgencyContact. Put in a few new values and be sure they are uploaded…then immediately undo the changes since you are working on live data.
SBUP15 SBUP16 SBUP17 SBUP18 SBUP19 SBUP20 SBUP21 DAUPL01 DAUPL02 DAUPL03
DAUPL04 DAUPL05
DAUPL06 DAUPL07 DAUPL08 DAUPL09
ID
DABMD001 DABMD002 DABMD003 DABMD004 DABMD005 Lookup single ID in BM_Definition table, then run norms calculations on it alone.
Details Note that the Calc Engine is fired off only for all BM_Definition records having a FlagStatus = 1 (or ready for calculation). All recs that have error out (-number), or are already calculated (3), or are not yet flagged for calculation (status = 0) will be ignored. Be sure that user can cancel out of wizard any time prior to hitting Finish and exit without altering anything. Check rec counts on BM_Norms, and last BM_ID before and after start wizard then hit cancel. All records for all agencies within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value with actual number you find in SQL from WH_Assess tables. All records for all agencies for specific SystemID within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value with actual number you find in SQL from WH_Assess tables *AND* REF_System table SystemID field (filter as needed in your SQL). Also run a distinct query of agency id's using the System Norm (BM_Definition) vs. agencies having that system (REF_Agency) All records for all agencies for specific RegionID within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value with actual number you find in SQL from WH_Assess tables *AND* REF_Region table RegionID field (filter as needed in your SQL). Also run a distinct query of agency id's using the Regional Norm (BM_Definition) vs. agencies having that region (REF_Agency) All records for inidividual agencies for specific M0010 within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value which should always be 1. Select one System at dropdown box. All records for all agencies for specific SystemID within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value with actual number you find in SQL from WH_Assess tables *AND* REF_System table SystemID field (filter as needed in your SQL). Also run a distinct query of agency id's using the System Norm (BM_Definition) vs. agencies having that system (REF_Agency) Select one Region at dropdown box. All records for all agencies for specific RegionID within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value with actual number you find in SQL from WH_Assess tables *AND* REF_Region table RegionID field (filter as needed in your SQL). Also run a distinct query of agency id's using the Regional Norm (BM_Definition) vs. agencies having that region (REF_Agency) Select one agency at dropdown box. All records for inidividual agencies for specific M0010 within the date range should be included. Goto table 'BM_Definition' and cross-reference NbrAgenciesCalculated field value which should always be 1. Select date range of a specific year. Be sure that all norms calculated have a discharge rec M0906_1 that is between January 1 and December 31 of the year specified. Select date range of a specific year and quarter. Be sure that all norms calculated have a discharge rec M0906_1 that is between the first and last day of the year/quarter specified. Select date range of a specific year and month. Be sure that all norms calculated have a discharge rec M0906_1 that is between the first and last day of the month specified. Select date range of a start and stop date. Be sure that all norms calculated have a discharge rec M0906_1 that is between these two dates specified. If left blank, then only BM_Definition recs are created, *BUT* not the BM_Norms records. If it is checked, then the BM_Norms table is also populated. "Name" should be: "AutoBatch: - " if created by the Benchmark Definition Wizard.
DABMD006
DABMD007 DABMD008
DABMD009
DABMD010 DABMD011 DABMD012 DABMD013 DABMD014 DABMD015 DABMD016 DABMD017
DABMD018 DABMD019 DABMD020
Cross compare to select count of BM_ID's in BM_Definition table after calcs completed. Should = the field value count in BM_Batch. For all Agency Aggregate Values (where M0010 is not null), this field should be = "ORG"; for all Compare Groups (where M0010 is null) this field should be "CG" Very important test. Pick an existing batch from BM_Batch table. Note the start and stop date range. Goto BM_Definition table and note the first and last BM_Ids for the Batch_ID you selected. Also, goto the BM_Norm table and note the count of norm recs for the BM_IDs linking back to the Batch_ID you selected. Now, go run the BM Definition Wizard using the same start and stop dates (pick same quarter or whatever) as the previous batch. After run is finished, go make sure that a new batch has not been added to the BM_Batch table, but the old record has been updated. Next, goto the BM_Definition table and make sure that all the old records from the first and last BM_ID you noted have been deleted and brand new ones added (using the largest BM_ID values to date). Finally, go take a count of BM_Norm records whose BM_ID links back up to the Batch_ID you chose...the count should be equal to the original count you took before indicating that the original records were deleted, and new records added. All DateStartPer and DateEndPer field values should be identical throughout a dataset where BM_Batch_ID is the same. These two dates should also exactly match their corresponding dates in the BM_Batch table. The Name and ShortName fields should be appropriate for the data in the record they represent. For example, if the National field is checked (value = -1) then the title should contain the work National. Another example would be if the ServiceLine_ID field contains a value, then a quick cross-check to the REF_ServiceLine table should show the ServiceLine description that should appear in the Name and ShortName fields. The wizard should build all permutations of these fields so that for example there is one norm for National with no service line, and one norm for each National with each ServiceLine. There should also be records built for every System with and one without ServiceLines. There should also be records built for every Region with and one without ServiceLines. However, note that where the dataset doesn't contain sersvice lines, then those sets will not have a serviceline BM_Definition record (e.g.: if the incoming data for a System has no data for Cardiology service line because their agencies do not provide those service) If you choose only a single Agency to build Norms on, then it will belong to the same Batch_ID as for previously run batch for same date range. Also note that this agency will be given an M0010 code to go with its "ORG" BM_Type field value. Field should always be set and reset at start when run a batch of norms through calculation. When performing actual calculations, use stopwatch to time first few norms being calculated. Watch bottom of screen as it changes BM_Definition record numbers to know when calculation of one set of norms has ended and next has begun.
DABMD021 DABMD022
DABMD023
DABMD024 DABMD025 DABMD026
ID
DABMD027
Details After norms calculated, setup query to count BM_Norm table recs and group by BM_ID. Then cross compare to the values in the BM_Definition table for field being tested.
ID
DABMD028 DABMD029
Details If national norm, distinct count of M0010 codes in WH_Assess tables for given date range and service line and *all* agencies. If System norm, distinct count of M0010 codes in WH_Assess table for given date range and service line, but further constrained by SystemID type. Ditto Region. Your counts in your test queries should match this field value. Same as previous acceptance criteria, except that distinct count is on more than just M0010…also add M0020 and M0030 to form a unique patient episode count.
DABMD030
DABMD031 DABMD032 DABMD033
DABMD034 DABMD035 DABMD036 DABMD037
Set to 0 if brand new, and user didn't set default to 1 for ready for calculation. When stored procedures are actually calculating the norms, the BM_Definition record Flag Status is set to 2. When all measures have been calculated, the rec's FlagStatus is set to 3 (completed). At any time, a failure will flip the flag to a negative value indicating failure at the given step (e.g.: failure furing phases 2 is denoted as -2). If there is a failure, review the data and look for typical errors such as a BM_Type_ID of "CG" where there are fewer than 5 agencies so the norms cannot be calculated. If you cannot find a cause, come check with me so we can determine why failure occurred. Future apps may make use of this flag. If a BM_Definition and set of norms is active, then it is set to -1. If archived or old and not to be recalculated, it will be marked 0. Don't test right now, it is a useless feature that is never used or mentioned in the code. Feature indicates that standard norms to be built (M0xxx, Oxxxx, and RHxxxx Measures). At this time, all report types have this value checked (or set to -1 for true). When set, all M0xx Measures must be calculated (cross check against the BM_Measure table) Feature indicates that DBSummary norms be built (DSxxxx Measures). Only BM_Definition records (norm sets) that are not constrained by a service line are flagged for DBSummary norms calculation. The reason is that the DBSummary measures apply to the entire population of patient assessments and the reports are not done to the detail of service lines. So, be sure that all non-service line BM_Definitions have this flag set (-1) and that anything with a ServiceLine has the flag cleared (0). They should be cleared (0); and should impact anything if you test a few by setting them to -1. All measure area names & codes should be spelled correctly. All measure area names & codes should be included or a part of the OASIS question set. BUG #76 All measure area names & codes should be included or a part of the OCS Characteristic question sheet.
DABMD038 DABMD039 DABMD040 DABMD041
All measure names and ids should be spelled correctly. All measure names and ids should be included or a part of the OASIS question set. All measure names and ids should be included or a part of the OCS Characteristic question sheet. Setup a dummy record in BM_Definition. Add multiple records to BM_AgencyConstraintList with that dummy record's BM_ID and a valid M0010 code. Run the stored procedure BM_CalcBenchmark_Wrapper from SQL Server with the dummy record's BM_ID. Confirm that temp table used to build norms contains those agency ids...or look at the AgencyCount field. Also, you can run cross check queries on a few of the measures to ensure that the proper agencies were picked. Cross check against queries you build for BM_Definition table criteria (e.g.: if National norm, then count should =all agencies in date range and service line; if system then constrain appropriately, etc.) Denominator should always be equal to or less than NumberCases field value. Denominator is less than only when there are exceptions for the given measure that are not included in the count (for example, nulls for a particular field value, etc. Do distinct queries on those Measure fields (M0xxx, etc.) in the WH_AssessN tables to see what the problems are. Start with a query returning a set of Primary Keys where the NumberCases and Denominator are unequal. Then further investigate a random sample of those hits to see why they are unequal. This will take a while to thoroughly test. Denominator should always be equal to or less than NumberCases and Denominator field value (typically always less than both). Do distinct queries on those Measure fields (M0xxx, etc.) in the WH_AssessN tables to see where the values come from (be sure to set proper constraints for date, M0010 agency(s), etc.). This will take a while to thoroughly test. Observed Rate = Numerator / Denominator and should always equal this value (see me when you find exceptions. All other fields in the table are not used at this time. Run the BM_Definition wizard multiple times for subsets of data and make sure do not overrun each other. For example, run once for National norm and check it. Then run once for each system and each region individually. This will result in dozens of individual runs after which you can check to see if all BM_Definition records added and not delete each other, etc. All DS codes can be cross checked with a query linking REF_AgencyChar to REF_Agency and WH_AssessVerify filtering to just the date range selected, M0010's or System, etc. selected. " " " " " "
DABMD042 DABMD043 DABMD044
DABMD045 DABMD046 DABMD047 DABMD048 DABMD049 DABMD050 DABMD051 DABMD052 DABMD053 DABMD054 DABMD055
ID
DABMD056 DABMD057 DABMD058 DABMD059 DABMD060 DABMD061 DABMD062 DABMD063 DABMD064 DABMD065 DABMD066 DABMD067 DABMD068 DABMD069 DABMD070 DABMD071 DABMD072 DABMD073 DABMD074 DABMD075 DABMD076 DABMD077 DABMD078 DABMD079 DABMD080 DABMD081 DABMD082 DABMD083 DABMD084 DABMD085 DABMD086 DABMD087 DABMD088 DABMD089 DABMD090 DABMD091 DABMD092 DABMD093 DABMD094 DABMD095 " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
Details
ID
DABMD096 DABMD097 DABMD098 DABMD099 DABMD100 DABMD101 DABMD102 DABMD103 DABMD104 DABMD105 DABMD106 DABMD107 DABMD108 DABMD109 DABMD110 DABMD111 DABMD112 DABMD113 DABMD114 DABMD115 DABMD116 DABMD117 DABMD118 DABMD119 DABMD120 DABMD121 DABMD122 DABMD123 DABMD124 DABMD125 DABMD126 DABMD127 DABMD128 DABMD129 DABMD130 DABMD131 DABMD132 DABMD133 DABMD134 DABMD135 " " " " " " " " " " " " " " " " " " " " " " " " " " "
Details
Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct?
ID
DABMD136 DABMD137 DABMD138 DABMD139 DABMD140 DABMD141 DABMD142 DABMD143 DABMD144 DABMD145 DABMD146 DABMD147 DABMD148 DABMD149 DABMD150 DABMD151 DABMD152 DABMD153 DABMD154 DABMD155 DABMD156 DABMD157 DABMD158 DABMD159 DABMD160 DABMD161 DABMD162 DABMD163 DABMD164 DABMD165 DABMD166 DABMD167 DABMD168 DABMD169 DABMD170 DABMD171 DABMD172 DABMD173 DABMD174 DABMD175
Details Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct?
ID
DABMD176 DABMD177 DABMD178 DABMD179 DABMD180 DABMD181 DABMD182 DABMD183 DABMD184 DABMD185 DABMD186 DABMD187 DABMD188 DABMD189 DABMD190 DABMD191 DABMD192 DABMD193 DABMD194 DABMD195 DABMD196 DABMD197 DABMD198 DABMD199 DABMD200 DABMD201 DABMD202 DABMD203 DABMD204 DABMD205 DABMD206 DABMD207 DABMD208 DABMD209
Details Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Query AssessN and get denominator and numerator counts then divide to get observed rate. Is benchmark value correct? Default is currently 5. Play with changing this and re-running the norms calculation wizard. Try 3 and be sure that now all norms comprised of 3 or more agencies are built whereas before only those with 5 or more agencies were built. Before, norms with a count of 3 or 4 agencies would error out and return 0 norm recs built.
ID
BMRPT001 BMRPT002 BMRPT003 BMRPT004 BMRPT005 BMRPT006 BMRPT007 BMRPT008 BMRPT009 BMRPT010 BMRPT011 BMRPT012 BMRPT013 BMRPT014 BMRPT015 BMRPT016 BMRPT017 BMRPT018 BMRPT019 BMRPT020 BMRPT021 BMRPT022 BMRPT023 BMRPT024 BMRPT025 BMRPT026 BMRPT027 BMRPT028 BMRPT029 BMRPT030 BMRPT031 BMRPT032 BMRPT033
Details Click Standard button at first step of Batch Reports, run all the way through and be sure RPT_Definition records created, and reports are printed (if you selected checkbox) Previously created RPT_Definition records, now use this option to print the previously built reports (using existing RPT_Definition records)
Run cross check queries for selected BM_ID and Measure Ids. Look at RPT_Definition records and be sure that all new recs added belong to just the BM_Batch_ID you selected. Run cross check queries for selected BM_ID and Measure Ids. Look at RPT_Definition records and be sure that all new recs added belong to just the set of M0010s you selected. If set, then reports are outputted; if clear then only recs are built If set, then reports are endlessly printed (testing). If clear, then the batch is printed once (production). Set override address and email report to yourself Type in some text and make sure it appears identically in the email sent out Set override address to "" (nothing) so that default is pulled from database table REF_AgencyContacts. Setup test records in that table so emails are sent to you WITHOUT using the override. This will prove that when we use email distribution, the reports will go to the correct person. Setup test as with previous acceptance criteria…except build multiple ficititious contact persons (with each using your email address for testing purposes).
HTML reports are put into specified directory (text box in app) and then into subdirectories grouped by agency M0010 id. Index.html files have links to all of an agency's reports. All links should work. Links to reports that could not be built should display a stub page (saying report could not be built). How long does it take to print reports (average time per report for 100 reports)…is it too slow or acceptable (say 2-5 seconds per report). How long does it take to build html reports (average time per report for 100 reports)…is it too slow or acceptable (say 2-5 seconds per report). Be sure to run a test over the weekend with the "Continuous Loop for Testing" flag checked at the wizard's output to step. Be sure to run a test over the weekend with the "Continuous Loop for Testing" flag checked at the wizard's output to step. Be sure to run a test over the weekend with the "Continuous Loop for Testing" flag checked at the wizard's output to step. The Warehouse Batch ID should match up to the date range you selected for the BM_Batch_ID date range. Every agency set of reports built (M0010s the same) should have one type of every report. However, the service line reports can occur multiple time per agency, but only once per service line. Cross check name of report with RPT_Type_ID via the RPT_Type table ServiceLine_ID should be null for non-service line reports at this time (biz rule may change). The ID should contain a service line id that you can cross check and lookup in the REF_ServiceLines table and compare to the name field of this table. Very important to test. Lookup the BM_ID listed here in the BM_Definition table. Cross check all BM_Definition fields to be sure you are looking at exactly the subset of data desired. For example, the M0010 code in the BM_Definition record must match the M0010 code in this table. Another example is that the ServiceLine_ID constraint in both tables must match. Finally, the BM_Batch_ID must match so that the date ranges are in synch (report date range and norm date range from BM_Definition). The BM_Type should be "ORG". Very important test. At this time, this field is used for the National norm values. Cross check all BM_Definition fields to be sure you are looking at the exact subset of data desired. There should be no M0010 (agency) id in BM_Definition, and no Region_ID, and no System_ID. The National true false field should be set to true (-1). The BM_Type should be "CG". If a service line is set in the RPT_Definition record, then it should match in the BM_Definition record. Very important test. At this time, this field is used for the System norm values. Cross check all BM_Definition fields to be sure you are looking at the exact subset of data desired. There should be no M0010 (agency) id in BM_Definition, and no Region_ID, and the National true false field should be null. The BM_Type should be "CG". The SystemID field should have a value that exactly matches the REF_Agency SystemID field for the M0010 you are viewing. If a service line is set in the RPT_Definition record, then it should match in the BM_Definition record.
BMRPT034
BMRPT035
ID
BMRPT036
Details Very important test. At this time, this field is used for the Regional norm values. Cross check all BM_Definition fields to be sure you are looking at the exact subset of data desired. There should be no M0010 (agency) id in BM_Definition, and no System_ID, and the National true false field should be null. The BM_Type should be "CG". The RegionID field should have a value that exactly matches the REF_Agency RegionID field for the M0010 you are viewing. If a service line is set in the RPT_Definition record, then it should match in the BM_Definition record. Are not currently in use, so they shouldn't break anything. However, if you dummy up a RPT_Definition record with BM_Ids in all 9 CGx_BM_ID fields, then all 9 should be calculated. Confirm it.
BMRPT037
BMRPT038 BMRPT039 BMRPT040 BMRPT041 BMRPT042
Be sure after a test run print batch that this field shows the proper date and time for all records in the batch printed. Be sure that the print time recorded here approximately matches reality (double check with stopwatch). Status flag values are: 0/New, 1/ReadyPrep, 2/InPrep, 3/ReadyPrint, 4/InPrintBatch, 5/InPrintSingle, 6/Printed, 7/Cleared, -Val/Err at Loc n. Be sure that all are used. If flag is set to true (-1) then report should be run. If flag is clear or false (0) then it should not be run. Only these columns should be visible on the report output.
BMRPT043 BMRPT044
Somewhere on the page, the full System name, and full Region name should be added. VERY IMPORTANT Test. Talk to Lisa about how to calculate the zscore right from the report page using the Agency Value vs. National, then vs. System, then vs. Regional Compare Groups. (To see what I used, lookup the property "ZScore 10% Threshold" the table "REF_Properties". You will also have to go to the RPT_Results table to lookup additional fields not displayed on the report (denominator and numerator values are two). We will also have to temporarily modify your version of the Report Wizard so that it doesn't clear athis table after the report is run...first try a print preview, and leave the preview up so that the app is paused, then go look at the temp table via second instance of Access. VERY IMPORTANT Test. Similar to the 10% test above. Use the RPT_Results table (fix app so not empty results after report run…OR run in print preview, leave report up then open second instance Access to check). Look at raw Observed value, then compare to Formatted Observed value. If .454 then round down to 45%. If .456 then round up to 46%, etc.
BMRPT045 BMRPT046 BMRPT047
BMRPT048 BMRPT049 BMRPT050 BMRPT051 BMRPT052 BMRPT053 BMRPT054 RANDOM SAMPLE 2-5%: Lookup MeasureIDs and MeasureNames in the BM_Measure table to cross-check. Also cross-check against the OASIS questionnaire form to be sure wrong data isn't here. RANDOM SAMPLE 2-5%: Lookup JCAHO_ID vs. MeasureIDs and MeasureNames in the BM_Measure table to cross-check. Also cross-check against the list of JCAHO indicators. Does it exist? Confirm page numbers start on 1. Page of x of N confirm N is really the last page. Is today's date stamped on report footer? Is it mm/dd/yyyy format (be sure 4-digit year).