|
As of December 11, there are 113 projects within the ISDS portfolio, with 52 active projects, 61 projects in queue or on hold. The ISDS project list includes both Advanced Planning Document (APD) projects (enhanced federal funding) and non-APD (not enhanced federal funding) projects. Visit the DHS Business Solutions Office (BSO) APD Education and Resources page or contact mat.dhs@state.mn.us for more information about APDs.
DHS, MNIT, counties, tribes, community partners and other
stakeholders are creating a person-centered human
services delivery system. The following are answers to questions about modernization
efforts as well as legacy work underway to integrate our legacy systems and improve
human service delivery.
There’s a governance structure for the ISDS portfolio.
How does it work?
The ISDS governance team furthers the enterprise-wide
vision of developing modern and adaptive technology solutions to support an
integrated, person-centered human services delivery system. Consisting of
representatives from the DHS business lines, MNIT and counties, there are two
groups that make up the ISDS governance team:
-
Executive Steering Committee (ESC) establishes the strategic direction for project work needed to support the ongoing program administration within, as well as the development of a modernized ISDS.
-
Program Management Team (PMT) oversees program management for the ISDS portfolio projects; identifies priorities, resource needs and timelines; and communicates and gathers input from all impacted business areas.
I’ve heard that there’s a group looking at legacy project
work. How do they fit into the picture?
In addition to the IT modernization projects that are
covered by the recently-approved IAPDU, there are many additional projects —
also known as non-APD projects — in the ISDS portfolio that touch our legacy
systems and impact overall modernization work. A separate work group was formed
to prioritize these non-APD projects.
Does the non-APD group report to another group in the
governance structure?
The ISDS PMT formed the non-APD work group to help
provide a balance between the modernization and legacy work in the ISDS
portfolio. The non-APD group works closely with the PMT to ensure that IT and
business resources align with modernization goals and priorities.
What kind of things does the non-APD work group do?
The non-APD group identifies and tracks implementation of
non-APD projects related to the ISDS legacy systems. They also connect with and
gather input from all business areas impacted by decisions of the ISDS PMT
regarding legacy projects and identify priorities, resource needs and timelines
for legacy projects.
When the group identifies critical issues, they provide
strategic recommendations to the ISDS PMT regarding policy, program and project
issues related to the ISDS legacy project portfolio. They also develop overall
risk mitigation strategies for ISDS legacy projects to ensure the success of
the ISDS delivery system.
The following was reported to the Centers for Medicare and Medicaid Services (CMS) on Dec. 13:
- The Identity and Access Management (IAM) team is working on the final round of testing in the systems test environment (STST) for the Minnesota Information
Transfer System MN-ITS; investigating and correcting a Windows Process Activation Service (WAS) configuration issue to move forward on the shared master index (SMI); completing use-case review and requirements gathering sessions for Business
Objects\SMRT ISDS.
- For MnCHOICES 1.0 the team has distributed MnCHOICES Assessment: Windows
10 helper document to counties and is continuing the 7.3 pilot. They are also fixing and testing logout functionality in offline mode and have begun quality assurance (QA) testing of copyright content changes and field trim script. For 2.0 they are continuing development for 18.1.1 - specifically the Proof of Concept for Web Services
Rewrite. The team has also completed QA testing of copyright
content changes and field trim script. For MnSPA the team has completed development on release 17.4 and is on schedule for production on Dec. 15. Development for release 18.1 is underway and four change requests have been added to 18.1 scope. They are also planning for releases 18.2 and 18.3.
- The Triage and Referral team has deployed the Cúram Geocoding Mapping Service
Adaptor as part of the METS 17.4.1 release. They are also preparing requirements and design for the scope planned for the METS
18.1.1 and 18.2 releases, including the provider database upload and services
definition.
- The Data Management team is continuing work on the OIG pilot project and correspondence for Adobe Experience Manager (AEM). Web
services for the exchange of information between AEM and NetStudy2 are
underway. A survey has been distributed
to county contacts to gather data to understand current state and needs around
electronic forms. For BI Tableau validation of
desktop solution has been approved, and they are expecting that master key will be complete by mid-December. The team has also presented how county users access BOBI/webi
reports and completed
an initial draft of the BI Non-standard Tool approval process. For Data
Sharing: Geocoding/Mapping Services production servers have been received. The team has started
performing QA testing of Geocoding/Mapping services. For Address Verification/Standardization Services they've finalized the Architecture Diagram for ordering of the development servers.
- The Appeals team has conducted JAD sessions
for the following topics: Document
Upload, Communication and Citizen Account Access. A Functional Specification Document (FSD)
is targeted for completion for: Exhibits,
Hearings. Interfaces: Appeals Maintenance Request. Architecture/Infrastructure: Citizen Portal Strategy, IAM and Appeals
integration. Development/Development
Quality: Sprint 1 Development in
progress
- The Cúram Instance Alignment (CIA) team is re-drawing the project schedule to allow IT and business to work out the issues around business process impacts related to Participant Identification Management, Evidence Management, Organization/Location Structure, Users and Security.
- The Infrastructure Environments and Integration (IEI) team is working on the following for Continuous Delivery: DNG - Requirements are in final approval and training plans are being drafted. Pilot configuration is also in progress. RTC - Training and Rollouts continued for SMI and AEM and project manager training is. Minnesota Provider Screening and Enrollment (MPSE) is complete. Cloud/Sys Automation for Deployment - Setup/Rollout planning for Jenkins/CloudBee, a solution for automating software development and delivery, continues.
- The State Medical Review Team's (SMRT) project plan is on hold pending changes based
on the CIA project evaluation. Work has started
on updating access permissions for users in production. Work is scheduled to be completed in
Q4 2017. A production deployment date is TBD for an upgrade to Datacap software, and UAT testing is moving forward.
- The Incident Reporting team is working
on requirements gathering and ramping up the project team.
- The Licensing team is revisiting the requirements to
determine what work can be completed as the technical team works through the
Provider Portal Minnesota Enterprise
Identity and Access Management (MNEIAM) issues.
Remember to submit items such as staff updates, individual and team accomplishments, kudos and content ideas on the DHS IT Update SharePoint site.
This update is intended to provide information on the ISDS portfolio to MNIT and DHS staff. Please contact Connie Kuhn, ISDS Program Communications Manager, if you have questions about this email. Current and previous editions of the ISDS Update are available on SharePoint. Click on ISDS Update if you'd like to be added to the distribution list for future editions.
|
