PL 006.pdf

PMO Template v1.0

© IBM Corporation Data Classification: Confidential Distribution

South Carolina Department of Health and Human Services (SCDHHS)

Database Design Document

Member Management Replacement Program (MMRP)

Version 4.0

May 25, 2021

PL 006

IBM PMO Template v.0

Data Classification: Confidential Distribution Page 2 of 24

SCDHHS MMRP Database Design Document

Table of Contents

1. Revision History

1.1 Review History

2. Review and Approval

3. Introduction

3.1 Scope

3.2 Audience

3.3 Objectives

4. Assumptions, Constraints and Risks

4.1 Assumptions

4.2 Constraints

4.3 Risks

5. Design Decisions

5.1 Key Factors Influencing Design

5.2 Database Management System Decisions

5.3 Security and Privacy Design Decisions

5.4 Performance and Maintenance Planning and Scheduling

6. Detailed Database Design

6.1 Content Management

6.2 Database Management System Files

7. Database Administration and Monitoring

7.1 Roles and Responsibilities

7.2 System Information

7.2.1 Database Management System Configuration

7.2.2 Database Support Software

7.2.3 Security and Privacy

7.2.4 Backup and Recovery

8. MMRP Database Diagrams

9. Terms

9.1 Acronyms

9.2 Glossary

Data Classification: Confidential Distribution Page 3 of 24

1. Revision History

Date Author Version Change Description

04/21/2017 Don Olivier 0.1 First draft

04/23/2017 Stasey Tackett 0.2 Edits and additional content per Jeff Leyh

04/25/2017 Don Olivier 0.3 Import to new template and make suggested edits

04/26/2017 Stasey Tackett 0.4 Edits

05/11/2017 Stasey Tackett 0.5 Post-business review edits, responses to questions / comments;

Eric Mittnight edits

05/30/2017 Stasey Tackett 1.0 Final edits per Lisa Carlyle. Saved doc as final version.

09/06/2017 Stasey Tackett 2.0 Edits reflect August 2017 POD and Oracle 12c upgrades; all tracked changes accepted, comments removed & approvals documented

10/25/2018 Eric Mittnight (IBM)

Vishal Rajagopal

(IBM)

2.1 Updated MMRS database

diagrams, to include new CGIS environments; comprehensive IBM MMRP O&M review

1/10/2019 Eric Mittnight (IBM)

Mahmoud Al Taher

(IBM)

2.2 Updated MMRS database

diagrams, included database monitoring/alerting thresholds and addressed CGIS data conversion

2/15/2019 Erin Coleman 3.0 Removed resolved comments, updated version number on title page and footer, and changed DRAFT watermark to APPROVED.

Saved document on SharePoint with an Approved status.

Data Classification: Confidential Distribution Page 4 of 24

Date Author Version Change Description

4/9/2021 Mahmoud Al Taher

(IBM)

Vishal Rajagopal

(IBM)

Deepak Chandra

(IBM)

3.1 Updated MMS Database System

Configuration table, MMS Data Dictionary Summary links, Database support software table

5/7/2021 Mahmoud Al Taher

(IBM)

3.2 Updates to address comments from

SCDHHS Technical staff

5/25/2021 Erin Coleman 4.0 Removed resolved comments, updated version number on title page and footer, and changed DRAFT watermark to APPROVED.

Saved document on SharePoint with an Approved status.

1.1 Review History

Version Date Author(s) Comments

2.1 11/02/2018 Erin Coleman Requested technical editing updates and updates to document references

2.1 11/14/2018 Eric Henrichsen Requested clarification on the data masking scope and database monitoring alerts

2.1 11/20/2018 Renjan Bhasi Requested additional details on the CGIS Data Conversion database management approach and structure

2.2 2/4/2019 Renjan Bhasi Closed all comments, except one.

3.1 4/20/2021 Erin Coleman Reviewed

3.1 4/27/2021 Tim Cozine Reviewed

3.2 5/11/2021 Renjan Bhasi Reviewed

Data Classification: Confidential Distribution Page 5 of 24

2. Review and Approval

Role Name Date Approval

Member Management Replacement Program (MMRP) Director, SCDHHS

Rhonda Morrison 5/11/2021 Rhonda Morrison

MMRP Cúram Technical Lead, SCDHHS

Renjan Bhasi

5/11/2021

Renjan Bhasi

MMRP Operations and Maintenance Manager, IBM

Jeff Leyh 5/25/2021 Jeff Leyh

3. Introduction

The purpose of the South Carolina Department of Health and Human Services (SCDHHS)

Database Design Document is to explain the database design pertaining to the Member

Management System (MMS).

The centerpiece of the MMS is IBM’s Cúram software, which contains a built-in data model.

The Database Design Document introduces the system context and design approach, including dependencies on other systems. This document identifies how MMS production database interfaces with other databases and contains diagrams of all databases in each of the MMS environments. (See Section 8, MMS Database Diagrams.)

3.1 Scope

The scope of this version of the MMRP Database Design document reflects the recent POD upgrade migration in the MMS Production environment. The POD refers to the bank of virtual servers (VMs) that provide the MMS production infrastructure. The SCDHHS POD contains high-density infrastructure racks (secured in a locked rack) and are supported by the Clemson University Infrastructure Services & Operations (ISO) Healthcare Infrastructure

Services (HCIS) team. HCIS is the core team within the ISO that specifically supports MMS.

This update addresses the addition of new Development, Quality Assurance (QA) and

Training environments required to support development and testing for the integration of the

Cúram Global Income Support (CGIS) module into MMS. This update references the approved CGIS Data Conversion Plan which details the database design approach for the

CGIS data conversion for the legacy Medicaid Eligibility Determination System (MEDS) to

Cúram / MMS.

https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/MMRP%20CGIS%20Data%20Conversion%20Plan.pdf

Data Classification: Confidential Distribution Page 6 of 24

3.2 Audience

The intended audience for the document is:

• MMRP Data Services, Security and Information Assurance, and the Clemson HCIS Network Architecture and Application Hosting teams

• MMRP Change Advisory Board (CAB)

• MMRP Design, Development and Implementation (DDI) and Operations & Maintenance (O&M) teams

• SCDHHS Data Owners, Stewards and Data Officers

3.3 Objectives

The objectives of the MMRP Database Design Document are to:

• Define key constraints of the database system

• Define key business factors influencing design

• Provide a high-level overview of key architectural decisions

• Provide a summary of backup and recovery options

4. Assumptions, Constraints and Risks

4.1 Assumptions

It is assumed that the hosting provider contracted by SCDHHS manages the maintenance and licensing of the hardware and operating system of the database environment.

It is further assumed that the Oracle licensing required for MMS will be made available by

SCDHHS when requested and approved as appropriate.

4.2 Constraints

MMS is currently hosted and managed in a data center that only offers virtualized services.

VMWare products are used for individual servers and NetApp products are used for storage arrays.

As a result, database design and architecture decisions must be made without the option of physical, dedicated hardware for a given node or instance.

4.3 Risks

The Out of the Box (OOTB) Cúram data model stores a significant amount of Extensible

Markup Language (XML) data in the Binary Large Object (BLOB) and Character Large

Data Classification: Confidential Distribution Page 7 of 24

Object (CLOB) fields directly in the database. This design decision greatly hinders any effort to automatically generate masked test data.

The Cúram data model, specifically the portions that store XML in LOB format, largely precludes the ability to automatically mask data and to generate masked test data at scale.

The majority of off-the-shelf products available for data masking require directly mappable fields and cannot process the hierarchies embedded within the stored XML files. The

SCDHHS UAT team, as part of their testing requirements, must complete test case execution in environments with the XML history available.

There have been extensive efforts by other states utilizing Cúram to create test data sets of sufficient quality (i.e., valid, complete, consistent, accurate, verifiable) from masked Cúram production data to support user acceptance and integration testing. Unfortunately, these efforts have not yielded the test results required before upgrades and enhancements can be confidently deployed to production.

5. Design Decisions

5.1 Key Factors Influencing Design

The recommendations accompanying the commercial IBM Cúram product were the single largest factors influencing the design of the MMS database. Given IBM’s experience with an established system in multiple states, recommendations made by the onsite MMS implementation team at initial go-live were critical in selecting support software versions.

In addition, the upgrade path and maintenance schedule of the backend databases supporting MMS are regularly aligned with the recommended upgrade path of the IBM

Cúram product to ensure future compatibility and system stability.

5.2 Database Management System Decisions

In August 2017, MMS upgraded to the Oracle Database 12c release, to include a transition to Solid State Drives for primary database storage. The upgrade from Oracle 11.2g to

Oracle 12c was driven, in part, by technical guidance from the IBM Cúram Product Delivery team.

In addition to storage changes, the Production database cluster was transitioned away from the Oracle RAC architecture model and the application WebSphere clusters were rebalanced. The diminishing performance of the previous SILO disk architecture led to the decision to move away from SILO storage and into the POD.

Data Classification: Confidential Distribution Page 8 of 24

5.3 Security and Privacy Design Decisions

Oracle offers broad levels of security and privacy for most of the industry standards enterprise applications. It offers security levels at the system level, database object level

(i.e., tables, etc.), and user level.

• System privileges: These privileges allow the grantees to perform standard administrator tasks in the database, restricting them only to trusted users.

• Object privileges: Each type of object has privileges associated with it.

• User roles: A “role” groups several privileges and roles, so that they can be granted to and revoked from users simultaneously. Roles must be enabled in order for a user to be able to perform tasks associated with that role. MMRP uses two different roles in the current environment: Read Only and Read Write.

All of the above access privileges must undergo an approval process defined by Clemson

Security, IBM MMRP Program Management Office (PMO), and the SCDHHS Office of

Information Assurance (OIA).

To enforce more security for Protected Health Information (PHI) data, MMRP is implementing encryption methods within database tablespaces, through Oracle Wallet.

Oracle Wallet requires a password to decrypt the encrypted tablespaces. The wallet is only accessible by the Database Administrators group.

• Database security patches will be applied as released by Oracle every quarter.

• Individual database user account passwords expire every 60 days, per SCDHHS security guidelines.

• Application service accounts will expire every 365 days per SCDHHS security guidelines.

5.4 Performance and Maintenance Planning and

Scheduling

Production application code releases are scheduled for every second and fourth Thursday nights from 11:00 PM to 2:00 AM Friday morning. Within the SCDHHS environment, there is an online calendar of events for these scheduled releases. IBM MMRP O&M Database

Administrators (DBAs) are involved for data retention and database infrastructure requirements.

• Each week, there is a scheduled maintenance window for database patching and maintenance.

https://devtools.scdhhs.gov/confluence/display/ProdSupp/2017-2018+Release+Calendar

Data Classification: Confidential Distribution Page 9 of 24

• Table level statistics are computed online every day at 8:59 PM EST to ensure that the Oracle optimizer has information to provide optimum results.

The amount of database space consumed is routinely evaluated by the IBM MMRP O&M

DBAs in order to project future growth and expansion needs. Capacity alerts are sent to

DBAs as needed. When additional storage to a server is needed, approval is required from the SCDHHS MMRP Program Director only if the storage added is more than 50% of the server’s capacity. Adding additional data files is done online with no disruption to application or database.

• Database archive logs are always available and backed up on a daily basis.

The IBM MMRP O&M team along with Clemson NOC determine application data archival and retention rates in conjunction with SCDHHS MMRP leadership. All data retention requests originate from the MMRP DDI and Quality Assurance (QA) teams via JIRA, the

MMRP tool for bug and issue tracking.

6. Detailed Database Design

6.1 Content Management

The design of all DBMS files consists of the following models and diagrams:

• Logical Data Model (LDM) and LDM Entity Relationship Diagram (ERD)

• Physical Data Model (PDM) and PDM ERD

The above models and diagrams are contained in the Data Dictionary Summary document, available in the MMRP SharePoint Consolidated Deliverables Management List (CDML) library.

Currently, MMS relies on the Cúram Health Care Reform (HCR) module and the Cúram framework. The enhancements of MMS include the introduction of the Cúram Global

Income Support (CGIS) module, will utilize that same Cúram Data Dictionary as the current

MMS Health Care Reform (HCR) module. In addition to existing data dictionaries, a new data dictionary for Community Engagement Waiver (CEW) will be built from the CEW code base.

The data objects and data structures are provided by Cúram and are available via the

Cúram documentation. The links to the Curam Data Dictionary are listed below:

http://hhs-mem-i-ddt01.clemson.edu:9081/curamanalysisdocumentation/index.html (O&M

Code Base) http://hhs-mem-i-ddt01.clemson.edu:9082/curamanalysisdocumentation/index.html (CGIS

R2 Code Base) https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/Forms/Project%20Management%20by%20Doc%20Type.aspx https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/Forms/Project%20Management%20by%20Doc%20Type.aspx http://hhs-mem-i-ddt01.clemson.edu:9081/curamanalysisdocumentation/index.html http://hhs-mem-i-ddt01.clemson.edu:9082/curamanalysisdocumentation/index.html

Data Classification: Confidential Distribution Page 10 of 24

The application model, including tables, indexes, constraints, and other objects, are maintained by the IBM MMRP DDI team.

6.2 Database Management System Files

The MMRP design focuses on developing a clear boundary between the Cúram framework and its database and additional databases that SCDHHS may want to manage for its own purposes.

In order to minimize the changes to the core Cúram framework and to increase the speed and decrease the effort required to update from one version of Cúram to the next, the

SCDHHS strategy has been to use an additional database to support MMS. For example, the State of South Carolina Department of Employment and Workforce (DEW) wage data is loaded into the Supporting Data Storage (SDS) and programming within the Enterprise

Service Bus (ESB) allows the Cúram framework to access this data.

The database manage approach for the conversion of selected legacy MEDS data into

Cúram / MMS is defined in the CGIS Data Conversion Plan. The plan details the conversion data flow (in Section 5.2.2) from MEDS source data extraction through the conversion database schemas and into the Cúram target database schema. The CGIS Data

Conversion Plan is located in Project Management Planning Documents library on the

MMRP SharePoint site.

7. Database Administration and Monitoring

The MMS production database is monitored to provide 24x7 uptime except for scheduled maintenance and application releases and is replicated to the Disaster Recovery (DR) site using Oracle Data Guard technology.

Monitoring tools include Oracle Enterprise Manager (OEM), Zabbix and Nagios. Alerts received from these tools trigger alarms within the Clemson Network Operations Center

(NOC). In the event of an alarm, the NOC contacts the IBM MMRP O&M team member on call.

Alerts are also signaled for abnormal performance and user activity, based on thresholds set by IBM MMRP O&M DBAs. OEM monitors the data stores 24x7. Proactive alerts are sent once the data stores reach a level where maintenance is needed. The table below provides the OEM thresholds setup by the IBM MMRP O&M DBAs:

Metric Warning Threshold Critical Threshold Schedule

Archive Area Used (%) >80% >95% Every 15 Minutes

Broken Job Count >0 N/A Every 30 Minutes https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/MMRP%20CGIS%20Data%20Conversion%20Plan.pdf https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/MMRP%20CGIS%20Data%20Conversion%20Plan.pdf https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/MMRP%20CGIS%20Data%20Conversion%20Plan.pdf https://schhs.sharepoint.com/sites/1211207/Project%20Management%20Planning%20Documents/Forms/Project%20Management%20by%20Doc%20Type.aspx

Data Classification: Confidential Distribution Page 11 of 24

Metric Warning Threshold Critical Threshold Schedule

Failed Job Count >0 N/A Every 30 Minutes

Data Failure Detected N/A All Every 5 Minutes

Dump Area Used (%) >95% N/A Every 30 Minutes

Exadata Module Version Failure (Error Count)

>0 N/A Every 24 Hours

Failed Logins (Count) >=100 >=300 Every 30 Minutes

Access Violation Incident N/A All Every 5 Minutes

Cluster Error Incident N/A All Every 5 Minutes

Deadlock Incident N/A All Every 5 Minutes

File Access Error Incident N/A All Every 5 Minutes

Generic Incident N/A All Every 5 Minutes

Inconsistent DB State Incident N/A All Every 5 Minutes

Internal SQL Error Incident N/A All Every 5 Minutes

Oracle Data Block Corruption Incident

N/A All Every 5 Minutes

Out of Memory Incident N/A All Every 5 Minutes

Redo Log Corruption Incident N/A All Every 5 Minutes

Session Terminated Incident N/A All Every 5 Minutes

Monitoring User Connectivity Issue (Password Invalid)

.*ORA-.* .*ORA-.* Every 30 Minutes

Monitoring User Expiry (Account Expiry in Hours)

<72 N/A Every 24 Hours

OCM Instrumentation (Need to Instrument with OCM)

1 N/A Every 24 Hours

Archiver Hung Error N/A All Every 5 Minutes

Data Block Corruption Error N/A All Every 5 Minutes

Generic Operational Error N/A All Every 5 Minutes

Media Failure Error N/A All Every 5 Minutes

Response State Mounted Down or Unknown

Every 15 Seconds

Response Status N/A Down Every 15 Seconds

SCN Grown Statistics (SCN Health)

<=62 <=10 Every 1 Hour

Data Classification: Confidential Distribution Page 12 of 24

Metric Warning Threshold Critical Threshold Schedule

Streams Process Errors >0 N/A Every 30 Minutes

Streams Process Status Disabled Aborted Every 30 Minutes

Tablespace Space Used (%) >=85 >=97 Every 30 Minutes

Tablespace Space Used (%) (dictionary managed)

>=85 >=97 Every 30 Minutes

Tablespace Segments Approaching Maximum Extents Count

>0 N/A Every 24 Hours

Tablespace Segments Not Able to Extent Count

>0 N/A Every 24 Hours

Temporary File Status Offline N/A Every 30 Minutes

Audited User SYS N/A Every 15 Minutes

Table 1: OEM Alerts and Thresholds

7.1 Roles and Responsibilities

The table below defines IBM, Clemson HCIS, and SCDHHS roles and responsibilities:

Role Client Responsibilities

Database Administrator

IBM The IBM MMRP teams perform installation, management, monitoring, and administration of the Oracle database instances.

System Administrator

Clemson HCIS The Clemson HCIS team provides server and hardware support. This includes OS- and Hardware-based monitoring and alerts.

Security Administrator

Clemson & SCDHHS Security

The Clemson and SCDHHS security teams provide security monitoring of network traffic and configuration.

Table 2: Roles and Responsibilities

7.2 System Information

Database storage configuration is shown below:

Tablespace Bytes(GB) curp1A

Auto Total

TABLESPACE (GB) --> Allocated Used Free Extend Available

CÚRAM_DATA 3.9 2.3 1.6 21.1 22.7

Data Classification: Confidential Distribution Page 13 of 24

CÚRAM_DATA_32K .5 .0 .5 24.5 25.0

CÚRAM_DATA_E 2621.4 2435.2 186.2 41.8 228.0

CÚRAM_INDEX .5 .0 .5 24.5 25.0

CÚRAM_INDEX_E 426.7 420.6 6.2 42.0 48.2

GG_DATA 1.9 1.8 .1 29.4 29.5

TOOLS .5 .4 .1 24.5 24.6

UNDOTBS1 26.0 15.5 10.4 3.3 13.8

UNDOTBS2 9.8 9.3 .5 19.5 20.0

3091.2 2885.1 206.1 230.6 436.8

Database memory segments are shown below:

SGA VALUE (Bytes)

Fixed Size 2,262,656

Variable Size 11,744,053,632

Database Buffers 9,596,567,552

Redo Buffers 36,073,47

Back to Top

7.2.1 Database Management System Configuration

The following table lists the database names, Operating System (OS), total memory (in

MB), and number of CPUs in the MMS Production environment.

Host OS Memory

(MB)

CPU

hhs-mem-p-ora01 Oracle Linux Server 3.8.13- 118.17.5.el6uek.x86_64

80,374 12

Table 3: Production Database System Configuration

The following table lists the database names, operating systems, total memory (in MB), and number of CPUs in the MMS Staging environment.

Host OS Memory (MB) CPU hhs-mem-s-ora10 Oracle Linux Server 3.8.13- 118.17.5.el6uek.x86_64

64,247 12

Table 4: Staging Database System Configuration

7.2.2 Database Support Software

The following table lists database support software, release number, and the MMS environment in which the software is utilized.

Data Classification: Confidential Distribution Page 14 of 24

Software Release Number Environment

Oracle Database 12.1c Enterprise Edition 12.2.0.1.0 64-bit Production

PL/SQL 12.2.0.1.0 Production

CORE 12.2.0.1.0 Production

TNS for Linux 12.2.0.1.0 Production

NLSRTL 12.2.0.1.0 Production

Oracle Application Data Model 12.2.0.1.0 Production

Oracle Data Integrator 12.2.1.3.0 Production

Table 5: Database Support Software

7.2.3 Security and Privacy

The SCDHHS MMRP uses Transparent Data Encryption (TDE) in Oracle for encryption in all MMS databases. The cryptographic library that TDE uses in the Oracle Database is validated for U.S. FIPS 140-2 compliance. The encryption is done at the tablespace level.

The data files are stored in CÚRAM_DATA_E tablespace and the indexes are stored in CÚRAM_INDEX_E tablespace, both of which are encrypted.

Performance Monitoring and Database Efficiency:

• Production database is monitored 24x7 for overall performance and user activity.

• Alerts are sent for abnormal performance and user activity(See Table 1 of Section 7, Database Administration and Monitoring.)

7.2.4 Backup and Recovery

The production database is in archive log mode and has the following backup schedules:

RMAN full backup is performed on Sundays at 12:00 AM.

RMAN incremental backup is performed on Tuesdays and Thursdays at 2:00 AM.

RMAN archive log backups are performed every day at 7:00 AM, 12:00 PM and 6:00 PM.

The production database is replicated to the DR site using Oracle Data Guard technology.

8. MMRP Database Diagrams

Data Classification: Confidential Distribution Page 15 of 24

Data Classification: Confidential Distribution Page 16 of 24

Data Classification: Confidential Distribution Page 17 of 24

Data Classification: Confidential Distribution Page 18 of 24

Data Classification: Confidential Distribution Page 19 of 24

Data Classification: Confidential Distribution Page 20 of 24

9. Terms

9.1 Acronyms

Acronym Definition

BLOB Binary Large Object

CAB Change Advisory Board

CDML Consolidated Deliverables Management List

CLOB Character Large Object

CPU Computer Processing Unit

DBAs Database Administrators

DBMS Database Management System

DEW Department of Employment and Workforce

DS&P Data Security and Privacy

ERD Entity Relationship Diagram

ESB Enterprise Service Bus

HCIS Healthcare Information Services

HCR Health Care Reform

LDM Logical Data Model

MEDS Medicaid Eligibility Determination Systems

MB Megabytes

MMRP Member Management Replacement Program

NOC Network Operations Center

OOTB Out of the Box

OS Operating System

PDM Physical Data Model

PHI Protected Health Information

POD Point of Delivery

Data Classification: Confidential Distribution Page 21 of 24

Acronym Definition

QA Quality Assurance

RAC Real Application Clusters

SCDHHS South Carolina Department of Health and Human Services

SDS Supporting Data Storage

SSD Solid State Drive

TDE Transparent Data Encryption

UAT User Acceptance Testing

XML Extensible Markup Language

Data Classification: Confidential Distribution Page 22 of 24

9.2 Glossary

Term Definition

Binary Large Object (BLOB) A collection of binary data stored as a single entity in a database management system. Blobs are typically images, audio or other multimedia objects, but sometimes binary executable code is stored as a BLOB. Database support for BLOBs is not universal.

Character Large Object

(CLOB)

A collection of character data in a database management system, usually stored in a separate location that is referenced in the table itself. Oracle and IBM DB2 provide a construct explicitly named CLOB, and the majority of other database systems support some form of the concept, often labeled as text, memo or long character fields.

Cúram An IBM Commercial-Off-The-Shelf (COTS) product customized to meet SCDHHS requirements. Cúram is the primary application used for MMRP.

Database Management System (DBMS)

System software for creating and managing databases. The DBMS provides users and programmers with a systematic way to create, retrieve, update and manage data.

Department of Employment and Workforce (DEW)

Responsible for paying unemployment insurance benefits, collecting unemployment taxes, helping people find jobs, matching businesses with qualified candidates, and collecting and disseminating state/federal employment statistics. Local offices are referred to as Employment Security Commission (ESC).

Enterprise Service Bus

(ESB)

Enterprise Service Bus for interoperability between Cúram framework and other systems including MMIS, MEDS, Federal HUB, and Federal Exchange.

Extensible Markup Language

(XML)

A markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.

Health Care Reform (HCR) Supports the Affordable Care Act (ACA) legislation requirements.

JIRA Part of the Atlassian product suite. JIRA provides bug and issue tracking for MMRP. Note: JIRA is not an acronym but rather a truncation of "Gojira," the Japanese name for “Godzilla.”

Logical Data Model (LDM) In data architecture, a logical data model (LDM) is a type of data model showing a detailed representation of an organization's data, independent of any particular technology, and described in business language.

Data Classification: Confidential Distribution Page 23 of 24

Term Definition

Nagios An open source computer-software application that monitors systems, networks and infrastructure. Nagios offers monitoring and alerting services for servers, switches, applications and services. It alerts users when things go wrong and alerts them a second time when the problem has been resolved.

NetApp An American multi-national storage and data management company that offers software, systems and services to manage and store data, including its proprietary Data ONTAP operating system.

Network Operations Center

(NOC)

Clemson’s network monitoring center located in Anderson, SC.

Out of the Box (OOTB) Computer software products that are purchased and used "as is" or “off the shelf.”

Physical Data Model (PDM) A physical data model (or database design) is a representation of a data design that takes into account the facilities and constraints of a given database management system. In the lifecycle of a project, it typically derives from a logical data model, though it may be reverse-engineered from a given database implementation.

Point of Delivery (POD) Application components that work together to deliver networking services.

Protected Health Information

(PHI)

Under the U.S. Health Insurance Portability and Accountability Act (HIPAA), health information that is associated directly with any PII identifiers, such as name, phone number, or medical record numbers, represents PHI and therefore must be treated with special care.

Real Application Clusters

(RAC)

A clustered version of Oracle Database based on a comprehensive high-availability stack that can be used as the foundation of a database cloud system as well as a shared infrastructure, ensuring high availability, scalability, and agility.

South Carolina Department of Health and Human Services (SCDHHS)

Single state Medicaid agency for the State of South of Carolina.

Splunk A leading Security Event Information Management (SEIM) platform for Operational Intelligence that allows users to search, monitor, analyze and visualize machine data.

Data Classification: Confidential Distribution Page 24 of 24

Term Definition

Structured Query Language

(SQL)

Domain-specific language used in programming, designed for managing data held in a Relational Database Management System (RDBMS), or for stream processing in a Relational Data Stream Management system (RDSMS).

User Acceptance Testing

(UAT)

Testing performed by the customer, SCDHHS. UAT also serves as the JIRA prefix for issues in the “Member Management” JIRA project.

VMWare A subsidiary of Dell Technologies that provides cloud and virtualization software and services.

Zabbix Enterprise-class open source monitoring software for networks and applications, designed to monitor and track the status of network services, servers, and other network hardware.

Back to Top