|




Quick Links: ◊Projected implementation dates
◊Communications
◊Request for
Proposal (RFP)
◊Overview
DSHS Main Page
Search DSHS
Contact Us
Privacy Disclaimer
» File
Readers
If you are having trouble opening
certain files you may need to download a free file reader.
|
Stakeholder Information
The Re-procurement of the current Medicaid Management Information System
(MMIS) potentially impacts every Administration within the Department of
Social and Health Services (DSHS) as well as a diverse and varied group
outside of DSHS, such as providers and other state agencies. Listed are a
comprehensive group of stakeholders involved in the Re-procurement
process.
DSHS Administrations
Aging and Disability Services
(ADSA)
Children’s
Administration (CA)
Economic Services
(ESA)
Financial Services (FSA)
Health and Rehabilitative
Services (HRSA)
Juvenile Rehabilitation
(JRA)
Management Services Administration (MSA)
Medical Assistance
Administration (MAA)
In addition to required monthly status reports, the Project Office will
provide and keep current a paper repository of basic project documents
and key deliverables to the CMS, Region 10 office. The
Project Office will meet with Region 10 representatives regularly
to discuss timing and strategy for the APD, vendor selection,
procurement strategies, etc. and to ensure project congruence with the
Medicaid Information Technology Architecture (MITA). The project office
will ensure that interaction with the Baltimore office is conducted as
frequently as recommended by the local office.
The Project Office will establish pro-active contact with
representatives from the Governor's Office to communicate the project's
overall schedule and plans, and to provide regular updates. Interactions
with the Governor’s office will be facilitated through the Office
of Financial Management (OFM).
To date, the Project Office has made a presentation to the Legislature
and received authorization to proceed with the Requirements Phase. As
part of this authorization, the MMIS Re-procurement Project is obligated
to report regularly to the Legislature, especially after key milestones
such as completion of alternative analysis, contract awarded to the
implementation vendor, etc. Generally speaking, Legislative updates will
be given every quarter. Additionally, we anticipate responding to any
legislative requests, such as inquiries following submission of the
supplemental budget request. Briefings to the Legislature are
likely to be combined with the OFM briefings.
The Information Services Board (ISB) is a 15-member Board made up of
leadership from the Legislature, state agencies, higher education and
the private sector.
The State Information Services Board has approved the Department of
Social and Health Services’ plan to purchase an existing Medicaid
billing and payment computer and then have it modified to meet the
specific needs of Washington State. The ISB decision followed a March
18, 2004, presentation by DSHS and Medical Assistance Administration
representatives outlining the plan.
Several state agencies will be involved in the Re-procurement
Project. Interactions with these agencies will be key to obtaining
their support and input. Interactions are being planned to
facilitate “Secretary to Secretary” discussions of project
scope and interagency impacts.
The Project Office will also form a team of representatives from each of
the agencies involved in or impacted by the project. This forum will
provide discussions on project status and facilitate the implementation of
functions that affect other state agencies.
-
Attorney General’s Office (AG)
-
Department of Information Services (DIS)
-
Medicaid Fraud and Control Unit (MFCU)
-
Health Care Authority (HCA)
-
Office of Financial Management (OFM)
-
Department of Health (DOH)
-
Department of Labor and Industries (L & I)
-
Department of Corrections (DOC)
Providers depend on the MMIS to process approximately $2.6
billion in claims annually. The Project Office will build on the
lessons learned during HIPAA where the value of interacting directly with
the providers, associations, and clearinghouse proved to be critical to
the success of the project. The Project Office will work with
DSHS enterprise wide to identify and communicate with
appropriate provider associations including the Hospital Association, the
Dental Association, the Medical Association, the Pharmacy Association and
the multiple Nursing Home Associations. Stakeholders will be particular
helpful in identifying how and when to communicate with new users of the MMIS due to scoping decisions, namely Individual Providers (IP).
The Project Office intends to form provider user groups and facilitate
opportunities for input regarding system requirements, system and process
improvements and general project management.
Seven (7) private sector health plans also rely on MMIS for enrollment
and premium payments for the DSHS clients eligible for the managed care
program. In turn, managed care health plans submit reports of encounters
with managed care clients back to MAA. The Project Office will create a
forum of managed care plan representatives and interact directly with
the plans to keep them informed of project status and to receive input
and feedback regarding the project progress and implementation
impacts.
To the extent that the Mental Health Division's (MHD) interaction with
RSNs is addressed by the future MMIS, the Project Office will work with
MHD to coordinate communication with the RSNs. Fourteen (14) RSNs
currently receive monthly payments from MHD for providing mental health
services in their respective catchment area. Additionally, RSNs provide
MHD monthly reports of encounters. These two (2) business functions will
be explored with MHD for inclusion in the MMIS project. The Project
Office will coordinate with MHD regarding interaction with RSNs to keep
them informed of project status and to receive input and feedback
regarding the project progress and implementation impacts.
The Project Office will contact the Title XIX Advisory Committee and begin
interactions to define beneficial communications and opportunities for
involvement and input to the project. |
|
|