REQUIREMENTS ANALYSIS:

1
REQUIREMENTS ANALYSIS Developing a Near-term
Plan for Washingtons Statewide Immunization
Registry Janna Halverson, Sherry Riddick,
Belinda Baker
2
Intentions

• Describe the CHILD Profile system
• Describe issues with the current system
  leading to the requirements analysis work
• Describe requirements analysis process
• Describe findings
• Describe next steps
• evaluate alternatives
• develop recommendation
• initiate work
• reassessment cycle

3
Brief History and Heading Forward

• 1993
• All Kids Count (King Snohomish) with DOH
  support
• Strategic Planning early 2000
• Governing Board mid 2000
• DOH assumed responsibility on 1/1/02

4
Purpose
Provide the infrastructure to ensure Washingtons
children receive preventive health care services.
5
Whats the Infrastructure?

• Health Promotion System Parent reminders of
  well-child care and immunizations and other
  important parenting information
• Immunization Registry Central repository for
  public and private providers use in
  protecting the public through the control of
  vaccine preventable disease

6
Vision
A fully populated system which is the primary
means for communicating public health messages to
parents and fostering up-to-date immunization
status.
7
Goals

• By June 30, 2004, increase to 90 the proportion
  of parents with young children (ages birth to 6
  years, born in WA State) sent the CHILD Profile
  health promotion materials.
• By June 30, 2006, increase to 95 the proportion
  of children who participate in CHILD Profiles
  fully operational, population-based immunization
  registry.  

8
Issues with Current System

• Need a plan to meet the NIP Functional
  Standards
• Too much effort and funding is being put into
  maintaining and supporting the network
• Technology budget fluctuates
• Very costly to build our own secured,
  HIPAA-compliant environment
• Supporting many system access methods

9
Issues with Current System

• Text-based application is antiquated
• Varying functionality between the text-based
  application and the web application
• Varying provider/plan understanding of the
  functionality

10
Requirements Analysis Process

• Interviews/surveys with providers, plans, LHJs
  and DOH Immunization Program
• Evaluation of current system functionality
• What are the unmet needs?
• How are they affecting stakeholders?
• What is the priority of each need?
• Comparison of current system functionality
  with requirements and user needs

11
Findings from Requirements Analysis

• Technical findings regarding current scope
• Planning issues
• Vaccine accountability
• WIC linkage
• Bioterrorism
• Communication, training, perceptions
• Policy

12
Findings

• Fully web-functional
• Increased quantity and quality of
  immunization history
• Improved de-duplication methods
• Improved integration with health plans and
  practice management software
• Tracking of primary care provider
• Improved VFC status tracking
• Improved CASA extracts

13
Findings

• Establish vaccine inventory management
• Integration with VACMAN for orders and
  distribution
• Provider inventory management capability
• Linkage with the WIC system (CIMS)
• Establish an ongoing registry users group
• Institute a process for assessing stakeholder
  requirements on a regular basis

14
Next Steps

• Evaluate alternatives
• Recommendations
• Select approach (DOH decision making)
• Initiate work
• Evolve

15
Evaluate Alternatives

• Use the assessment of the existing system as
  a baseline for evaluating other alternatives
• Evaluate/compare three alternate strategies
• Continued modification and enhancement of
  the existing system
• Development of a new system
• Purchase off-the-shelf

16
Criteria for Evaluating Alternatives

• Ability to meet defined functional requirements
• Feasibility of infrastructure requirements
• Cost/Benefit (tangible and intangible)
• Risk
• Migration issues
• System limitations

17
Evolve