Nov
27

CMS Status Report for week ending Nov 9, 2012

Hi All: Highlights from this week include the urgent items:
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)

Full report details can be found below:

Project Status Report

Project Name: Prepared by: Period Ending:
Medicaid Provider Screening Portal Sarah Ramkissoon/Andy LaMora 09-Nov-12

Executive Summary

Item Comments
Overall
  • Projecting a Q4 Implementation though there are significant risks
Scope/Quality
  • Missed scope (smaller items) adding pressure to timeline. On track  otherwise (r7)
Schedule
  • Risks emerging – see details in Risks and Issues section (r7)
Budget/Resources
  • Project budget to be watched closely (i7)
Contest Management
  • On track – approximately  contests remaining in Oct – Dec

upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference

Complete Workflow for All Providers

November

Risk

r1, i2,r6,i6, r7

Administrative Workflow

Early November

Risk

r1,i2,r6,i6

UI wireframes (all)

Early November

Risk

r1

Prototype

November

Stable

r1


pcoming Activities

Work Required  - Sponsor (Nov 10-17)
URGENT:

  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Confirm the provider will know the LISStudyID (WDSL requirement) as per Netstudy requirements
  • Clarify DMF and PECOS files requirements (confirmation of whether UI required)

Other/Upcoming:

  • Requires client time, input and assistance to:
    • Screening rules and front-end validation (drools contests) for individual providers
    • External sources assemblies for organizational providers
    • UI prototype and wireframes
  • Monitor forums and continue discussion on open issues
Work Required – Topcoder (Nov 10-17)
URGENT:

  • Update ERD and functionality list for organizational type
  • Update miscellaneous PEPS requirements in original concepts documentation
  • Launch Miscellaneous services and Provider enrollment contests
  • Review Netstudy requirements and get confirmation whether UI required for DMF and PECOS

Other/Upcoming:

  • Create overall site design summary walk-through
  • Contest to verify charter against specification document to ensure no missed requirements
  • Work with client to resolve outstanding questions and issues.

 ISSUES and RISKs Summary


Ref #

Description

Reported Date

Action By Date

Status

i7

Issue:    Budget is projected to go over 500K due to the necessity of having more assembly contests than was originally projected, as requirements complexity increased recently (e.g. PT33-NPI requirements, dis-enrollment, etc) and known functionality (e.g. Mainframe connectivity requirement, IBM Stack port, etc) has proven to be more complex, and more expensive to build and test. 

10-25-12

11-15-12

Open

r7

Risk: Requirements on key areas still outstanding: Mainframe connectivity requirements and MNITS.  Confirmation on Netstudy, DMF and PECOS files are also outstanding and may impact the project scope and schedule

11-01-12

11-15-12

Open

r6

Risk: To satisfy PT33-NPI requirements there will likely be need to integrate with legacy systems/processes as well as perform manual processes outside of the system (e.g. sending letter cancellation requests, consolidation request fulfillment, etc)Action:  Topcoder to review and ensure nuances and requirements integrated – risk to the timeline due to complexity

10-25-12

11-15-12

Open

r5

Risk:IBM License test requires time to conduct test and review results. If the results are not as expected, a new/alternate strategy/discussions may be requiredAction:Expedite testing by using an IBM copilot to set up smart clouds, enabling POC testing on the IBM stack.Update: Issue is still unresolved – alternate strategies will be explored in addition to pursuing smart cloud set-up

09-20-12

10-21-12

Open

r1

Risk: A significant number of new provider organizations have been provided by client in mid-late September timeframe.  As a result the time to complete the UI wireframes that included these new organizational types has increased.Action:  Run required organizational wireframes contests aggressively, including in parallel where possible, or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

i6

Risk: Missed or new requirement to ensure dis-enrollment functionality is present will impact administrative workflow timelines.Action:  Topcoder will expedite inclusion of the missed functionality as best possible (consider use of bug race or other methodology to expedite inclusion)

10-25-12

11-15-12

Closed

i5

Issue: Client is experiencing difficulty downloading UI submissions, in particular wireframes due to their size.Action:  Topcoder will propose a new methodology to facilitate wireframe viewing

10-18-12

10-18-12

Closed

i3

Issue: Client is concerned that feedback to UI wireframes are not being reflected and client is having trouble tracking which wireframes reflect feedback given by Angie.Action:  Topcoder is running short bug races to make wireframe changes and Dan shown how to follow bug races in Cockpit.  Topcoder’s James will update the demo box twice weekly with wireframe updates (on a scheduled basis where possible)

09-26-12

10-21-12

Closed

i4

Issue: Death master file access: will not be available. For development purposes, it will be assumed that a file will be uploaded weekly or monthly and a webservice utilized to process the file.  A simple screen interface will be created to facilitate the upload.

10-11-12

10-15-12

CLosed

r3

Risk: Topcoder is currently experiencing technical difficulties with the software that allows for downloading of judging bundle packages. Action:Topcoder staff are working on getting the issue resovled with highest priority.Update: Judging bundles are now available for download

09-20-12

10-03-12

Closed

i2

Issue:  Strategy to address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by client.  Creation on contest to port elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

Issue:  Developers require API access to 3rdsites to check for licensing and other authorization information Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies respectively) are looking into getting API access.Alternate:  Create  well-formatted private web pages that allows for screen-scraping, and query with querystring tokens, post, etc  

 

07-26-12

08-23-12

Closed

i1

Issue:  Strategy required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world” applications) and implement open source stack version.  Client will then prioritize elements to port to the IBM stack

07-12-12

07-31-12

 Closed

Project budget update  

Ref #

Description

Comments

1

Projected outstanding contests cost: $90,000

n/a

2

Approximate contest cost to date: $490,000

Tracking Budget status closely to ensure in-line with expectations