HP Enterprise Services - DHHR

HPES Response to West Virginia MMIS Re-procurement RFP
4.1.10 Solution Alignment with BMS’ Business and Technical Needs
The interChange system has already been running in several states for many years. It is the most proven
next-generation MMIS solution available in the marketplace today—proven for reliability, scalability, and
configurability to meet today’s demanding challenges of the state healthcare business. HPES meets
requirement 3.1.15 and has incorporated into WV-iC BMS’ requirements of compatibility of the hardware,
software, or communications components installed for use by BMS staff members with WVOT-supported
versions of the Microsoft operating system, Microsoft Office Suite, and Internet Explorer; and current
technologies for data interchange. This highly sophisticated, feature-rich system will deliver long-lasting
value to West Virginia.
Please refer to the “Proposed Technical Architecture Design” section of our response to “3.2.1 Proposed West Virginia MMIS”
for a full description of our proposed solution.
Systems Documentation (Req. 4)
HPES places a high priority on maintaining current technical and operational documentation. Managing and maintaining
documentation by our SMEs is part of our approach to delivering quality deliverables. We appreciate that detailed, accurate
documentation helps produce the correct result the first time: the programmer codes a system change exactly, the enrollment
specialist enrolls a provider properly, and the adjudicator pays a claim accurately. The result is that time-consuming mistakes
and rework are avoided.
As the transfer system is modified and enhanced, developers and technical writers update the system documentation as part of
completing work items. Examples of system documentation include data structures, entity relationship diagrams, user manuals,
and business rules. The system documentation is available through HP Development Center—a module plug-in to HP Quality
Center that provides a user interface to the interChange solution objects—and work item documentation, including unit test
results, use cases, user manuals, and developer work pattern documentation.
User Documentation (Req. 5)
HPES will provide comprehensive, well-organized user documentation—written in a procedural, step-by-step format—that
promotes usability. We will prepare manuals for each business process major program functional area, which will help users
understand the purpose and operation of the functions, and further support documentation accessibility to process owners and
key stakeholders. Documentation is framed during design and drafted during development, along with testing and training
preparation. Our approach allows flexibility in developing and delivering content. By tying the training content to documentation,
efficiencies in time, effort, and costs can be realized. Content-sharing can be directly responsive to changes driven by
legislative, system, or user requirements.
Our documentation specialists are experienced in organizing and writing user manuals so users who are not information
processing professionals can learn to access and interpret online web pages related to their business process. We understand
the importance of accurate, current documentation to support the smooth, consistent running of an MMIS operation. We
document and define acronyms, transaction codes, terms, and field identifiers consistently with the web page, report, or data
dictionary descriptions.
User documentation covers system navigation, online help, and policies and procedures and will be used to prepare BMS users
to conduct UAT. Documentation will be the basis for creating the UAT test plan and scripts. The documentation will help testers
design and develop the test case framework and test cases during the testing task.
Our goal is to provide comprehensive training supported by user and system documentation that will prove effective as a
procedural and policy reference and an outstanding training tool. The trainer and documentation specialist is responsible for
developing training curricula, training materials, facilitating training sessions, and technical and user documentation. User
documentation will be used to prepare for training. The draft user documentation will be finalized during Phase 1d -
Implementation Readiness.
Provider Documentation (Req. 6)
We understand that a primary goal BMS has for the implementation of its MMIS Re-procurement Project is that the provider
and member communities make a smooth transition from the old to the new system. The transition to a new MMIS will present
various new expectations across a diverse and dispersed set of roles within BMS, its agencies, and its provider community. Our
documentation specialist will develop provider documentation and user documentation as the WV-iC undergoes development.
It is imperative that technical messages be communicated to stakeholders at levels they can fully understand. Our specialist will
work with the Development team to clarify technical issues and help produce clear, concise provider documentation that will be
RFP # MED11014 Page 177