SEAS IT Overview
System Census
Knowledge Management Platform
Risk Mitigation
100

What does SEAS stand for?

Support for Enterprise Architecture Services.

100

What is the primary purpose of the System Census UI?

To collect, review, and update data about various systems within CMS.

100

What does KMP stand for

Knowledge Management Platform.

100

What storage method posed a security risk in the System Census UI?

localStorage.

200

Name all of the SEAS IT workstreams?

CEDAR, OAGM, KMP

200

What coding language is the legacy System Census UI built on?

AngularJS.

200

What AI technique is used by KMP to classify and derive insights from data?

Natural Language Processing (NLP).

200

Why is webMethods being replaced?

High cost and proprietary language limitations.

300

What is AI Workspace?

Provides an environment for implementing, testing, and deploying AI and machine learning (ML) models. It is designed to support CMS's modernization initiatives by integrating AI/ML capabilities into workflows to enhance decision-making, automate processes, and extract insights from structured and unstructured data.


300

What does the CEDAR stand for?

CMS Enterprise Data Archival and Reporting

300

Name 3 KMP use cases?

EPRO, OAGM, OPOEL, OFM, ICPG

300

What kind of security compliance process is required for SEAS?

FISMA compliance.

400

Name one of the modern technologies being used to improve SEAS infrastructure?

Docker, Kubernetes, and Terraform.

400

A modeling platform that helps with IT planning, portfolio management, and enterprise architecture analysis.

Sparks EA

400

This environment within the Knowledge Management Platform (KMP) enables the development, testing, and deployment of machine learning models, integrates with CMS data sources, and supports automation for tasks like SBOM generation and natural language processing.

AI workspace

400

Name a proposed solution to mitigate System Census UI security risks.

Rebuilding the UI in React

500

What does TEA stand for?

Technical Enterprise Architecture

500

A legacy application that manages APIs and facilitates integration with other CMS systems.

WebMethods

500

This CMS use case aims to integrates data from multiple systems to provide comprehensive reporting and analysis summaries, ensuring accurate tracking of healthcare outcomes and program performance.

EPRO