diff --git a/.gitignore b/.gitignore index 9fd8a66ce8..ac6db2b80e 100644 --- a/.gitignore +++ b/.gitignore @@ -10,3 +10,5 @@ npm-debug.log* pgdata __files api/test-data/files +notes.md +schema.sql diff --git a/.nvmrc b/.nvmrc new file mode 100644 index 0000000000..f599e28b8a --- /dev/null +++ b/.nvmrc @@ -0,0 +1 @@ +10 diff --git a/CHANGELOG.md b/CHANGELOG.md index 3c3716eaa5..ffaf6e7af2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,10 +3,7 @@ Anticipated release: September 21st, 2020 #### 🚀 New features - -- Results of previous activities fields are missing in export view ([#2420]) -- Standards and conditions is in the wrong area on export view ([#2386]) -- Match private contractor costs section on export view to builder ([#2393]) +- Change order of fields and field/title names on Cost Allocation and Other Funding + Budget and FFP pages. ([#2322]) #### 🐛 Bugs fixed @@ -17,7 +14,4 @@ Anticipated release: September 21st, 2020 # Previous releases See our [release history](https://github.com/CMSgov/eAPD/releases) - -[#2420]: https://github.com/CMSgov/eAPD/issues/2420 -[#2386]: https://github.com/CMSgov/eAPD/issues/2386 -[#2393]: https://github.com/CMSgov/eAPD/issues/2393 +[#2322]: https://github.com/CMSgov/eAPD/issues/2322 diff --git a/api/db/knex.js b/api/db/knex.js index 36fe407245..261cebfe90 100644 --- a/api/db/knex.js +++ b/api/db/knex.js @@ -1,6 +1,13 @@ const knex = require('knex'); const config = require('../knexfile'); -const db = process.env.NODE_ENV ? knex(config[process.env.NODE_ENV]) : () => {}; +const { NODE_ENV } = process.env; +if (!NODE_ENV) { + let msg = "❌ NODE_ENV is not set, unable to determine knex configuration\n"; + msg += "Please set NODE_ENV to 'development', 'test', or 'production'\n"; + msg += "Terminating..."; + console.error(msg); /* eslint-disable-line no-console */ + process.exit(1); +} -module.exports = db; +module.exports = knex(config[NODE_ENV]); diff --git a/api/env.js b/api/env.js index 92bd88e614..4fe4192712 100644 --- a/api/env.js +++ b/api/env.js @@ -23,25 +23,8 @@ const defaults = { STORE_TYPE: 'null' // default to using the /dev/null store }; -// Check if there are any CloudFoundry user-provided services -// offering up environment variables. If there are, extract -// them and merge them into our environment. -const upsEnv = {}; -if (process.env.VCAP_SERVICES) { - try { - const vcap = JSON.parse(process.env.VCAP_SERVICES); - if (Array.isArray(vcap['user-provided'])) { - vcap['user-provided'].forEach(ups => { - Object.entries(ups.credentials).forEach(([name, value]) => { - upsEnv[name] = value; - }); - }); - } - } catch (e) {} // eslint-disable-line no-empty -} - dotenv.config(); -process.env = { ...defaults, ...upsEnv, ...process.env }; +process.env = { ...defaults, ...process.env }; // Don't require this until process.env is finished setting up, since that // defines how the logger works. diff --git a/api/env.test.js b/api/env.test.js index 56d510da9b..4101e7a704 100644 --- a/api/env.test.js +++ b/api/env.test.js @@ -36,28 +36,6 @@ tap.test('environment setup', async envTest => { } ); - envTest.test( - 'reads environment variables from CF user-provided services', - async test => { - process.env.VCAP_SERVICES = JSON.stringify({ - 'user-provided': [ - { - credentials: { - VCAP_VAR1: 'var1', - VCAP_VAR2: 'var2' - } - } - ] - }); - require('./env'); // eslint-disable-line global-require - test.match( - process.env, - { VCAP_VAR1: 'var1', VCAP_VAR2: 'var2' }, - 'sets variables from CF user-provided service' - ); - } - ); - envTest.test( 'does not override environment variables that have been set externally', async test => { diff --git a/api/knexrepl.js b/api/knexrepl.js new file mode 100644 index 0000000000..a8db4bd901 --- /dev/null +++ b/api/knexrepl.js @@ -0,0 +1,17 @@ +// https://medium.com/@sobinsunny/orm-console-with-repl-961ee264ed93 + +// usage: +// $ npm run knex-console +// knex> const rows = await knex('apds') +// knex> rows[0].document.activities +// knex> .exit + +require('dotenv').config(); +const repl = require('repl'); +const knex = require('./db/knex') + +const r = repl.start('knex> '); +const run = async () => { + r.context.knex = await knex; +}; +run(); diff --git a/api/migrations/20200918103000_add-ffy-to-other-funding-desc.js b/api/migrations/20200918103000_add-ffy-to-other-funding-desc.js new file mode 100644 index 0000000000..934a0d23a3 --- /dev/null +++ b/api/migrations/20200918103000_add-ffy-to-other-funding-desc.js @@ -0,0 +1,24 @@ +/* eslint-disable no-param-reassign */ +exports.up = async knex => { + const apdRecords = await knex('apds').select('document', 'id', 'years'); + + apdRecords.forEach(({ document, id }) => { + const years = document.years; + + document.activities.forEach(activity => { + const otherSources = activity.costAllocationNarrative.otherSources || "" + years.forEach(year => { + activity.costAllocationNarrative[year] = { + otherSources + } + }); + delete activity.costAllocationNarrative.otherSources; + }); + + knex('apds') + .where('id', id) + .update({ document }); + }); +}; + +exports.down = async () => {}; diff --git a/api/package-lock.json b/api/package-lock.json index 7bdf64da7f..3edbf7411f 100644 --- a/api/package-lock.json +++ b/api/package-lock.json @@ -8436,6 +8436,12 @@ "resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz", "integrity": "sha1-jcrkcOHIirwtYA//Sndihtp15jc=" }, + "repl": { + "version": "0.1.3", + "resolved": "https://registry.npmjs.org/repl/-/repl-0.1.3.tgz", + "integrity": "sha1-LwXUKwyItD0FzL2hDtFK7/Vpm2A=", + "dev": true + }, "request": { "version": "2.88.2", "resolved": "https://registry.npmjs.org/request/-/request-2.88.2.tgz", diff --git a/api/package.json b/api/package.json index 2e10420c75..a42cb5af0f 100644 --- a/api/package.json +++ b/api/package.json @@ -5,14 +5,18 @@ "main": "main.js", "scripts": { "audit": "npx audit-ci --config ./audit-ci.json", + "knex-console": "NODE_ENV=development node --experimental-repl-await knexrepl.js", "lint": "eslint '**/*.js'", "make-migrate": "knex migrate:make", "migrate": "knex migrate:latest", + "migrate-dev": "NODE_ENV=development DEV_DB_HOST=localhost npm run migrate", + "rollback": "knex migrate:rollback", "seed": "knex seed:run", + "seed-dev": "NODE_ENV=development DEV_DB_HOST=localhost npm run seed", "start": "node main.js", - "start-dev": "nodemon ./main.js -e js", + "start-dev": "NODE_ENV=development DEV_DB_HOST=localhost nodemon ./main.js -e js", "jest": "NODE_ENV=test jest", - "tap": "NODE_ENV=test tap -J --no-browser --no-coverage --no-timeout ${TESTS:-'{,!(node_modules)/**/}*.test.js'}", + "tap": "NODE_ENV=test tap -J --no-browser --no-coverage --no-timeout --reporter=spec ${TESTS:-'{,!(node_modules)/**/}*.test.js'}", "test": "NODE_ENV=test tap -J --cov --coverage-report=lcov --no-browser --no-timeout --reporter=spec --test-arg=--silent '{,!(node_modules)/**/}*.test.js'", "test-endpoints": "jest --detectOpenHandles --runInBand '.+\\.endpoint\\.js'", "test-specific": "NODE_ENV=test tap --cov --coverage-report=lcov --no-browser --reporter=spec", @@ -96,6 +100,7 @@ "jest": "^25.2.1", "nodemon": "^2.0.4", "prettier": "^1.19.1", + "repl": "^0.1.3", "sinon": "^8.1.1", "stream-mock": "^2.0.5", "tap": "^14.10.8" diff --git a/api/routes/apds/__snapshots__/get.endpoint.js.snap b/api/routes/apds/__snapshots__/get.endpoint.js.snap index 5827c54309..d1b3cbaba5 100644 --- a/api/routes/apds/__snapshots__/get.endpoint.js.snap +++ b/api/routes/apds/__snapshots__/get.endpoint.js.snap @@ -92,9 +92,15 @@ Object { }, }, "costAllocationNarrative": Object { - "methodology": "

No cost allocation is necessary for this activity.

+ "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

", - "otherSources": "

No other funding is provided for this activity.

+ }, + "methodology": "

No cost allocation is necessary for this activity.

", }, "description": "

III.A.1: Modifications to the State Level Repository

@@ -429,9 +435,16 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

+", + }, "methodology": "

No cost allocation is necessary for this activity.

", - "otherSources": "", }, "description": "

III.B.3 Medicaid Claims Data Feed to the HIE

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

@@ -773,8 +786,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "", + }, + "2020": Object { + "otherSources": "", + }, "methodology": "", - "otherSources": "", }, "description": "

\\"undefined\\" @@ -1066,8 +1084,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

@@ -1260,8 +1283,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.2 Public Health System Modernization

@@ -1489,8 +1517,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.B.4 HITECH MITA 3.0 Development and Implementation

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

@@ -1799,7 +1832,10 @@ Object { }, "status": "draft", "updated": "1910-06-18T09:00:00.000Z", - "years": Array [], + "years": Array [ + "2019", + "2020", + ], } `; @@ -1813,7 +1849,10 @@ Array [ "name": "MN-1921-07-11-HITECH-APD", "status": "draft", "updated": "1910-06-18T09:00:00.000Z", - "years": Array [], + "years": Array [ + "2019", + "2020", + ], }, Object { "created": "1936-08-03T00:00:00.000Z", @@ -1821,7 +1860,7 @@ Array [ "name": "MN-1936-08-03-HITECH-APD", "status": "not draft", "updated": "1947-04-10T00:00:00.000Z", - "years": null, + "years": Array [], }, ] `; diff --git a/api/routes/apds/__snapshots__/patch.endpoint.js.snap b/api/routes/apds/__snapshots__/patch.endpoint.js.snap index b8eeff49ff..d8f8f9f5aa 100644 --- a/api/routes/apds/__snapshots__/patch.endpoint.js.snap +++ b/api/routes/apds/__snapshots__/patch.endpoint.js.snap @@ -88,9 +88,15 @@ Object { }, }, "costAllocationNarrative": Object { - "methodology": "

No cost allocation is necessary for this activity.

+ "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

", - "otherSources": "

No other funding is provided for this activity.

+ }, + "methodology": "

No cost allocation is necessary for this activity.

", }, "description": "

III.A.1: Modifications to the State Level Repository

@@ -167,36 +173,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -417,9 +431,16 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

+", + }, "methodology": "

No cost allocation is necessary for this activity.

", - "otherSources": "", }, "description": "

III.B.3 Medicaid Claims Data Feed to the HIE

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

@@ -471,36 +492,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -753,8 +782,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "", + }, + "2020": Object { + "otherSources": "", + }, "methodology": "", - "otherSources": "", }, "description": "

\\"undefined\\" @@ -857,36 +891,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -1038,8 +1080,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

@@ -1078,36 +1125,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -1224,8 +1279,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.2 Public Health System Modernization

@@ -1304,36 +1364,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -1445,8 +1513,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.B.4 HITECH MITA 3.0 Development and Implementation

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

@@ -1480,36 +1553,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -1746,7 +1827,10 @@ Object { }, }, "status": "draft", - "years": Array [], + "years": Array [ + "2019", + "2020", + ], } `; @@ -1850,9 +1934,15 @@ Object { }, }, "costAllocationNarrative": Object { - "methodology": "

No cost allocation is necessary for this activity.

+ "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

", - "otherSources": "

No other funding is provided for this activity.

+ }, + "methodology": "

No cost allocation is necessary for this activity.

", }, "description": "

III.A.1: Modifications to the State Level Repository

@@ -1929,36 +2019,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -2179,9 +2277,16 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

+", + }, + "2020": Object { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

+", + }, "methodology": "

No cost allocation is necessary for this activity.

", - "otherSources": "", }, "description": "

III.B.3 Medicaid Claims Data Feed to the HIE

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

@@ -2233,36 +2338,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -2515,8 +2628,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "", + }, + "2020": Object { + "otherSources": "", + }, "methodology": "", - "otherSources": "", }, "description": "

\\"undefined\\" @@ -2619,36 +2737,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -2800,8 +2926,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

@@ -2840,36 +2971,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -2986,8 +3125,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.C.2 Public Health System Modernization

@@ -3066,36 +3210,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -3207,8 +3359,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2019": Object { + "otherSources": "none", + }, + "2020": Object { + "otherSources": "none", + }, "methodology": "", - "otherSources": "", }, "description": "

III.B.4 HITECH MITA 3.0 Development and Implementation

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

@@ -3242,36 +3399,44 @@ Object { "quarterlyFFP": Object { "2019": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, }, "2020": Object { "1": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "2": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "3": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, "4": Object { + "combined": 25, "contractors": 25, "inHouse": 25, }, @@ -3508,7 +3673,10 @@ Object { }, }, "status": "draft", - "years": Array [], + "years": Array [ + "2019", + "2020", + ], } `; diff --git a/api/routes/apds/__snapshots__/post.endpoint.js.snap b/api/routes/apds/__snapshots__/post.endpoint.js.snap index bbc58361cc..cec7c44334 100644 --- a/api/routes/apds/__snapshots__/post.endpoint.js.snap +++ b/api/routes/apds/__snapshots__/post.endpoint.js.snap @@ -7,14 +7,14 @@ Object { "alternatives": "", "contractorResources": Array [], "costAllocation": Object { - "2020": Object { + "2021": Object { "ffp": Object { "federal": 90, "state": 10, }, "other": 0, }, - "2021": Object { + "2022": Object { "ffp": Object { "federal": 90, "state": 10, @@ -23,8 +23,13 @@ Object { }, }, "costAllocationNarrative": Object { + "2021": Object { + "otherSources": "", + }, + "2022": Object { + "otherSources": "", + }, "methodology": "", - "otherSources": "", }, "description": "", "expenses": Array [], @@ -45,7 +50,7 @@ Object { "plannedEndDate": "", "plannedStartDate": "", "quarterlyFFP": Object { - "2020": Object { + "2021": Object { "1": Object { "contractors": 0, "inHouse": 0, @@ -63,7 +68,7 @@ Object { "inHouse": 0, }, }, - "2021": Object { + "2022": Object { "1": Object { "contractors": 0, "inHouse": 0, @@ -100,13 +105,13 @@ Object { "id": 1, "incentivePayments": Object { "ehAmt": Object { - "2020": Object { + "2021": Object { "1": 0, "2": 0, "3": 0, "4": 0, }, - "2021": Object { + "2022": Object { "1": 0, "2": 0, "3": 0, @@ -114,13 +119,13 @@ Object { }, }, "ehCt": Object { - "2020": Object { + "2021": Object { "1": 0, "2": 0, "3": 0, "4": 0, }, - "2021": Object { + "2022": Object { "1": 0, "2": 0, "3": 0, @@ -128,13 +133,13 @@ Object { }, }, "epAmt": Object { - "2020": Object { + "2021": Object { "1": 0, "2": 0, "3": 0, "4": 0, }, - "2021": Object { + "2022": Object { "1": 0, "2": 0, "3": 0, @@ -142,13 +147,13 @@ Object { }, }, "epCt": Object { - "2020": Object { + "2021": Object { "1": 0, "2": 0, "3": 0, "4": 0, }, - "2021": Object { + "2022": Object { "1": 0, "2": 0, "3": 0, @@ -159,13 +164,13 @@ Object { "keyPersonnel": Array [ Object { "costs": Object { - "2020": 0, "2021": 0, + "2022": 0, }, "email": "", "fte": Object { - "2020": 0, "2021": 0, + "2022": 0, }, "hasCosts": false, "isPrimary": true, @@ -178,7 +183,7 @@ Object { "narrativeHIT": "", "narrativeMMIS": "", "previousActivityExpenses": Object { - "2018": Object { + "2019": Object { "hithie": Object { "federalActual": 0, "totalApproved": 0, @@ -198,7 +203,7 @@ Object { }, }, }, - "2019": Object { + "2020": Object { "hithie": Object { "federalActual": 0, "totalApproved": 0, @@ -218,7 +223,7 @@ Object { }, }, }, - "2020": Object { + "2021": Object { "hithie": Object { "federalActual": 0, "totalApproved": 0, @@ -256,8 +261,8 @@ Object { }, }, "years": Array [ - "2020", "2021", + "2022", ], } `; diff --git a/api/routes/apds/patch.js b/api/routes/apds/patch.js index 396f4d7700..691df84ef6 100644 --- a/api/routes/apds/patch.js +++ b/api/routes/apds/patch.js @@ -1,23 +1,10 @@ -const Ajv = require('ajv'); const { apply_patch: applyPatch } = require('jsonpatch'); const jsonpointer = require('jsonpointer'); const logger = require('../../logger')('apds route put'); const { getAPDByID: ga, updateAPDDocument: ua } = require('../../db'); const { can, userCanEditAPD } = require('../../middleware'); -const apdSchema = require('../../schemas/apd.json'); - -const ajv = new Ajv({ - allErrors: true, - jsonPointers: true, - // The validator will remove any fields that aren't in the schema - removeAdditional: 'all' -}); - -const validatorFunction = ajv.compile({ - ...apdSchema, - additionalProperties: false -}); +const { validateApd } = require('../../schemas'); // This is a list of property paths that cannot be changed with this endpoint. // Any patches pointing at these paths will be ignored. @@ -29,7 +16,7 @@ module.exports = ( getAPDByID = ga, patchObject = applyPatch, updateAPDDocument = ua, - validateApd = validatorFunction + validate = validateApd } = {} ) => { logger.silly('setting up PATCH /apds/:id route'); @@ -74,13 +61,13 @@ module.exports = ( return res.status(400).end(); } - const valid = validateApd(updatedDocument); + const valid = validate(updatedDocument); if (!valid) { logger.error( req, // Rather than send back the full error from the validator, pull out just the relevant bits // and fetch the value that's causing the error. - validateApd.errors.map(({ dataPath, message }) => ({ + validate.errors.map(({ dataPath, message }) => ({ dataPath, message, value: jsonpointer.get(updatedDocument, dataPath) @@ -88,7 +75,7 @@ module.exports = ( ); return res .status(400) - .send(validateApd.errors.map(v => ({ path: v.dataPath }))) + .send(validate.errors.map(v => ({ path: v.dataPath }))) .end(); } diff --git a/api/routes/apds/patch.test.js b/api/routes/apds/patch.test.js index f95945f597..a515177f78 100644 --- a/api/routes/apds/patch.test.js +++ b/api/routes/apds/patch.test.js @@ -15,7 +15,7 @@ tap.test('apds PATCH endpoint', async tests => { const getAPDByID = sandbox.stub(); const patchObject = sandbox.stub(); const updateAPDDocument = sandbox.stub(); - const validateApd = sandbox.stub(); + const validate = sandbox.stub(); const res = { end: sandbox.spy(), @@ -30,13 +30,13 @@ tap.test('apds PATCH endpoint', async tests => { res.send.returns(res); res.status.returns(res); - validateApd.errors = []; + validate.errors = []; patchEndpoint(app, { getAPDByID, patchObject, updateAPDDocument, - validateApd + validate }); handler = app.patch.args[0][app.patch.args[0].length - 1]; }); @@ -106,8 +106,8 @@ tap.test('apds PATCH endpoint', async tests => { getAPDByID.resolves({ document: 'old document' }); patchObject.returns(patchedDocument); - validateApd.returns(false); - validateApd.errors = [ + validate.returns(false); + validate.errors = [ { dataPath: '/key1/key2/key3', message: 'validation error' } ]; @@ -117,7 +117,7 @@ tap.test('apds PATCH endpoint', async tests => { test.ok(patchObject.calledWith('old document', patches), 'applies patches'); test.ok( - validateApd.calledWith(patchedDocument), + validate.calledWith(patchedDocument), 'validates the new document' ); test.ok(res.status.calledWith(400), 'sends an HTTP 400 status'); @@ -141,7 +141,7 @@ tap.test('apds PATCH endpoint', async tests => { }); const patchedDocument = { key1: 'value 1' }; patchObject.returns(patchedDocument); - validateApd.returns(true); + validate.returns(true); updateAPDDocument.resolves('update time'); const patches = [{ path: 'path 1' }, { path: 'path 2' }]; diff --git a/api/routes/apds/post.data.js b/api/routes/apds/post.data.js index 285044ee2a..5f5889981f 100644 --- a/api/routes/apds/post.data.js +++ b/api/routes/apds/post.data.js @@ -34,7 +34,7 @@ const getNewApd = () => { }), costAllocationNarrative: { methodology: '', - otherSources: '' + ...forAllYears({ otherSources: '' }) }, description: '', expenses: [], diff --git a/api/routes/apds/post.data.test.js b/api/routes/apds/post.data.test.js index 96d33cb9ff..c942f02300 100644 --- a/api/routes/apds/post.data.test.js +++ b/api/routes/apds/post.data.test.js @@ -31,7 +31,8 @@ tap.test('APD data initializer', async test => { }, costAllocationNarrative: { methodology: '', - otherSources: '' + '1997': { otherSources: '' }, + '1998': { otherSources: '' } }, description: '', expenses: [], diff --git a/api/routes/apds/post.js b/api/routes/apds/post.js index b652bf3832..1e5dd875af 100644 --- a/api/routes/apds/post.js +++ b/api/routes/apds/post.js @@ -1,24 +1,10 @@ -const Ajv = require('ajv'); - const logger = require('../../logger')('apds route post'); const { createAPD: ga, getStateProfile: gs } = require('../../db'); const { can } = require('../../middleware'); +const { validateApd } = require('../../schemas'); const getNewApd = require('./post.data'); -const apdSchema = require('../../schemas/apd.json'); - -const ajv = new Ajv({ - allErrors: true, - jsonPointers: true, - removeAdditional: true -}); - -const validatorFunction = ajv.compile({ - ...apdSchema, - additionalProperties: false -}); - module.exports = (app, { createAPD = ga, getStateProfile = gs } = {}) => { logger.silly('setting up POST /apds/ route'); app.post('/apds', can('edit-document'), async (req, res) => { @@ -48,12 +34,12 @@ module.exports = (app, { createAPD = ga, getStateProfile = gs } = {}) => { delete apd.stateProfile.medicaidOffice.director; } - const valid = validatorFunction(apd); + const valid = validateApd(apd); if (!valid) { // This is just here to protect us from the case where the APD schema changed but the // APD creation function was not also updated logger.error(req, 'Newly-created APD fails validation'); - logger.error(req, validatorFunction.errors); + logger.error(req, validateApd.errors); return res.status(500).end(); } diff --git a/api/routes/apds/post.test.js b/api/routes/apds/post.test.js index bf3a11ef63..5f4b6d9de6 100644 --- a/api/routes/apds/post.test.js +++ b/api/routes/apds/post.test.js @@ -64,6 +64,8 @@ tap.test('apds POST endpoint', async endpointTest => { test.ok(res.end.calledOnce, 'response is terminated'); }); + // Why is a 500 status being returned when the frontend sends malformed data? + // Should this not be a 4xx status? What the heck? tests.test( 'sends a 500 if the newly-generated APD fails schema validation', async test => { @@ -87,7 +89,8 @@ tap.test('apds POST endpoint', async endpointTest => { }, costAllocationNarrative: { methodology: '', - otherSources: '' + '2004': { otherSources: '' }, + '2005': { otherSources: '' } }, description: '', expenses: [], diff --git a/api/schemas/activity.json b/api/schemas/activity.json new file mode 100644 index 0000000000..b54d761190 --- /dev/null +++ b/api/schemas/activity.json @@ -0,0 +1,109 @@ +{ + "$id": "activity.json", + "type": "object", + "required": [ + "alternatives", + "contractorResources", + "costAllocation", + "costAllocationNarrative", + "description", + "expenses", + "fundingSource", + "name", + "plannedEndDate", + "plannedStartDate", + "schedule", + "standardsAndConditions", + "statePersonnel", + "summary", + "quarterlyFFP" + ], + "properties": { + "alternatives": { "type": "string" }, + "contractorResources": { + "type": "array", + "items": { "$ref": "contractorResource.json" } + }, + "costAllocation": { "$ref": "costAllocation.json" }, + "costAllocationNarrative": { "$ref": "costAllocationNarrative.json" }, + "description": { "type": "string" }, + "expenses": { + "type": "array", + "items": { "$ref": "expense.json" } + }, + "fundingSource": { + "enum": ["HIE", "HIT", "MMIS", false] + }, + "name": { "type": "string" }, + "objectives": { + "type": "array", + "items": { "$ref": "objective.json" } + }, + "plannedEndDate": { "$ref": "definitions.json#/optionalFullDate" }, + "plannedStartDate": { "$ref": "definitions.json#/optionalFullDate" }, + "schedule": { + "type": "array", + "items": { + "$id": "#/properties/activities/items/properties/schedule/items", + "type": "object", + "required": ["endDate", "milestone"], + "properties": { + "endDate": { + "$id": "#/properties/activities/items/properties/schedule/items/properties/endDate", + "$ref": "definitions.json#/optionalFullDate" + }, + "milestone": { + "$id": "#/properties/activities/items/properties/schedule/items/properties/milestone", + "type": "string" + } + } + } + }, + "standardsAndConditions": { + "type": "object", + "required": ["doesNotSupport", "supports"], + "properties": { + "doesNotSupport": { + "$id": "#/properties/activities/items/properties/standardsAndConditions/properties/doesNotSupport", + "type": "string" + }, + "supports": { + "$id": "#/properties/activities/items/properties/standardsAndConditions/properties/supports", + "type": "string" + } + } + }, + "statePersonnel": { + "type": "array", + "items": { "$ref": "person.json" } + }, + "summary": { "type": "string" }, + "quarterlyFFP": { + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/activities/items/properties/quarterlyFFP/year", + "type": "object", + "required": ["1", "2", "3", "4"], + "patternProperties": { + "^(1|2|3|4)$": { + "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter", + "type": "object", + "required": ["contractors", "inHouse"], + "properties": { + "contractors": { + "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter/contractors", + "$ref": "definitions.json#/optionalNumber" + }, + "inHouse": { + "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter/inHouse", + "$ref": "definitions.json#/optionalNumber" + } + } + } + } + } + } + } + } +} diff --git a/api/schemas/apd.json b/api/schemas/apd.json index 7b3c262322..cfd2842983 100644 --- a/api/schemas/apd.json +++ b/api/schemas/apd.json @@ -1,16 +1,6 @@ { - "definitions": { - "optionalFullDate": { - "$id": "#/definitions/fullDate", - "type": "string" - }, - "optionalNumber": { - "$id": "#/definitions/optionalNumber", - "anyOf": [{ "type": "number" }, { "type": "string", "pattern": "\\d*" }] - } - }, "$schema": "http://json-schema.org/draft-07/schema#", - "$id": "https://eapd.cms.gov/apd.json", + "$id": "apd.json", "type": "object", "required": [ "name", @@ -28,624 +18,25 @@ "years" ], "properties": { - "name": { - "$id": "#/properties/name", - "type": "string" - }, + "name": { "type": "string" }, "activities": { - "$id": "#/properties/activities", "type": "array", - "items": { - "$id": "#/properties/activities/items", - "type": "object", - "required": [ - "alternatives", - "contractorResources", - "costAllocation", - "costAllocationNarrative", - "description", - "expenses", - "fundingSource", - "name", - "plannedEndDate", - "plannedStartDate", - "schedule", - "standardsAndConditions", - "statePersonnel", - "summary", - "quarterlyFFP" - ], - "properties": { - "alternatives": { - "$id": "#/properties/activities/items/properties/alternatives", - "type": "string" - }, - "contractorResources": { - "$id": "#/properties/activities/items/properties/contractorResources", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/contractorResources/items", - "type": "object", - "required": [ - "description", - "end", - "hourly", - "name", - "start", - "totalCost", - "years" - ], - "properties": { - "description": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/description", - "type": "string" - }, - "end": { "$ref": "#/definitions/optionalFullDate" }, - "hourly": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly", - "type": "object", - "required": ["data", "useHourly"], - "properties": { - "data": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/data", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year", - "type": "object", - "required": ["hours", "rate"], - "properties": { - "hours": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year/hours", - "$ref": "#/definitions/optionalNumber" - }, - "rate": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year/rate", - "$ref": "#/definitions/optionalNumber" - } - } - } - } - }, - "useHourly": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/useHourly", - "type": "boolean" - } - } - }, - "name": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/name", - "type": "string" - }, - "start": { "$ref": "#/definitions/optionalFullDate" }, - "totalCost": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/totalCost", - "type": "integer" - }, - "years": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/years", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/contractorResources/items/properties/years/year", - "type": "number" - } - } - } - } - } - }, - "costAllocation": { - "$id": "#/properties/activities/items/properties/costAllocation", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/costAllocation/year", - "type": "object", - "required": ["ffp", "other"], - "properties": { - "ffp": { - "$id": "#/properties/activities/items/properties/costAllocation/year/ffp", - "type": "object", - "required": ["federal", "state"], - "properties": { - "federal": { - "$id": "#/properties/activities/items/properties/costAllocation/year/ffp/federal", - "type": "number" - }, - "state": { - "$id": "#/properties/activities/items/properties/costAllocation/year/ffp/state", - "type": "number" - } - } - }, - "other": { - "$id": "#/properties/activities/items/properties/costAllocation/year/other", - "type": "number" - } - } - } - } - }, - "costAllocationNarrative": { - "$id": "#/properties/activities/items/properties/costAllocationNarrative", - "type": "object", - "required": ["methodology", "otherSources"], - "properties": { - "methodology": { - "$id": "#/properties/activities/items/properties/costAllocationNarrative/properties/methodology", - "type": "string" - }, - "otherSources": { - "$id": "#/properties/activities/items/properties/costAllocationNarrative/properties/otherSources", - "type": "string" - } - } - }, - "description": { - "$id": "#/properties/activities/items/properties/description", - "type": "string" - }, - "expenses": { - "$id": "#/properties/activities/items/properties/expenses", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/expenses/items", - "type": "object", - "required": ["description", "category", "years"], - "properties": { - "description": { - "$id": "#/properties/activities/items/properties/expenses/items/properties/description", - "type": "string" - }, - "category": { - "$id": "#/properties/activities/items/properties/expenses/items/properties/category", - "type": "string" - }, - "years": { - "$id": "#/properties/activities/items/properties/expenses/items/properties/years", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/expenses/items/properties/years/year", - "type": "number" - } - } - } - } - } - }, - "fundingSource": { - "$id": "#/properties/activities/items/properties/fundingSource", - "enum": ["HIE", "HIT", "MMIS", false] - }, - "name": { - "$id": "#/properties/activities/items/properties/name", - "type": "string" - }, - "objectives": { - "$id": "#/properties/activities/items/properties/objectives", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/objectives/items", - "type": "object", - "required": ["keyResults", "objective"], - "properties": { - "keyResults": { - "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items", - "type": "object", - "required": ["baseline", "keyResult", "target"], - "properties": { - "baseline": { - "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/baseline", - "type": "string" - }, - "keyResult": { - "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/keyResult", - "type": "string" - }, - "target": { - "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/target", - "type": "string" - } - } - } - }, - "objective": { - "$id": "#/properties/activities/items/properties/goals/items/properties/objective", - "type": "string" - } - } - } - }, - "plannedEndDate": { "$ref": "#/definitions/optionalFullDate" }, - "plannedStartDate": { "$ref": "#/definitions/optionalFullDate" }, - "schedule": { - "$id": "#/properties/activities/items/properties/schedule", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/schedule/items", - "type": "object", - "required": ["endDate", "milestone"], - "properties": { - "endDate": { - "$id": "#/properties/activities/items/properties/schedule/items/properties/endDate", - "$ref": "#/definitions/optionalFullDate" - }, - "milestone": { - "$id": "#/properties/activities/items/properties/schedule/items/properties/milestone", - "type": "string" - } - } - } - }, - "standardsAndConditions": { - "$id": "#/properties/activities/items/properties/standardsAndConditions", - "type": "object", - "required": ["doesNotSupport", "supports"], - "properties": { - "doesNotSupport": { - "$id": "#/properties/activities/items/properties/standardsAndConditions/properties/doesNotSupport", - "type": "string" - }, - "supports": { - "$id": "#/properties/activities/items/properties/standardsAndConditions/properties/supports", - "type": "string" - } - } - }, - "statePersonnel": { - "$id": "#/properties/activities/items/properties/statePersonnel", - "type": "array", - "items": { - "$id": "#/properties/activities/items/properties/statePersonnel/items", - "type": "object", - "required": ["title", "description", "years"], - "properties": { - "title": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/title", - "type": "string" - }, - "description": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/description", - "type": "string" - }, - "years": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/years", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/years/year", - "type": "object", - "required": ["amt", "perc"], - "properties": { - "amt": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/years/year/amount", - "$ref": "#/definitions/optionalNumber" - }, - "perc": { - "$id": "#/properties/activities/items/properties/statePersonnel/items/properties/years/year/fte", - "$ref": "#/definitions/optionalNumber" - } - } - } - } - } - } - } - }, - "summary": { - "$id": "#/properties/activities/items/properties/summary", - "type": "string" - }, - "quarterlyFFP": { - "$id": "#/properties/activities/items/properties/quarterlyFFP", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/activities/items/properties/quarterlyFFP/year", - "type": "object", - "required": ["1", "2", "3", "4"], - "patternProperties": { - "^(1|2|3|4)$": { - "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter", - "type": "object", - "required": ["contractors", "inHouse"], - "properties": { - "contractors": { - "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter/contractors", - "$ref": "#/definitions/optionalNumber" - }, - "inHouse": { - "$id": "#/properties/activities/items/properties/quarterlyFFP/year/quarter/inHouse", - "$ref": "#/definitions/optionalNumber" - } - } - } - } - } - } - } - } - } - }, - "federalCitations": { - "$id": "#/properties/federalCitations", - "type": "object", - "required": [], - "patternProperties": { - "^.+$": { - "$id": "#/properties/federalCitations/property", - "type": "array", - "items": { - "$id": "#/properties/federalCitations/property/items", - "type": "object", - "required": ["title", "checked", "explanation"], - "properties": { - "title": { - "$id": "#/properties/federalCitations/property/items/properties/title", - "type": "string" - }, - "checked": { - "$id": "#/properties/federalCitations/property/items/properties/checked", - "type": ["boolean", "string"], - "pattern": "^$" - }, - "explanation": { - "$id": "#/properties/federalCitations/property/items/properties/explanation", - "type": "string" - } - } - } - } - }, - "additionalProperties": false - }, - "incentivePayments": { - "$id": "#/properties/incentivePayments", - "type": "object", - "required": ["ehAmt", "ehCt", "epAmt", "epCt"], - "patternProperties": { - "^e(h|p)(Amt|Ct)$": { - "$id": "#/properties/incentivePayments/type", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/incentivePayments/type/year", - "type": "object", - "required": ["1", "2", "3", "4"], - "patternProperties": { - "^[0-9]$": { - "$id": "#/properties/incentivePayments/type/year/quarter", - "$ref": "#/definitions/optionalNumber" - } - } - } - } - } - } - }, - "keyPersonnel": { - "$id": "#/properties/keyPersonnel", - "type": "array", - "items": { - "$id": "#/properties/keyPersonnel/items", - "type": "object", - "required": [ - "name", - "position", - "email", - "isPrimary", - "fte", - "hasCosts", - "costs" - ], - "properties": { - "name": { - "$id": "#/properties/keyPersonnel/items/properties/name", - "type": "string" - }, - "position": { - "$id": "#/properties/keyPersonnel/items/properties/position", - "type": "string" - }, - "email": { - "$id": "#/properties/keyPersonnel/items/properties/email", - "type": "string" - }, - "isPrimary": { - "$id": "#/properties/keyPersonnel/items/properties/isPrimary", - "type": "boolean" - }, - "fte": { - "$id": "#/properties/keyPersonnel/items/properties/fte", - "type": "object", - "patternProperties": { - "^[0-9]{0,2}": { - "$id": "#/properties/keyPersonnel/items/properties/fte/year", - "type": "number" - } - } - }, - "hasCosts": { - "$id": "#/properties/keyPersonnel/items/properties/hasCosts", - "type": "boolean" - }, - "costs": { - "$id": "#/properties/keyPersonnel/items/properties/costs", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/keyPersonnel/items/properties/costs/year", - "type": "number" - } - } - } - } - } - }, - "narrativeHIE": { - "$id": "#/properties/narrativeHIE", - "type": "string" - }, - "narrativeHIT": { - "$id": "#/properties/narrativeHIT", - "type": "string" - }, - "narrativeMMIS": { - "$id": "#/properties/narrativeMMIS", - "type": "string" - }, - "previousActivityExpenses": { - "$id": "#/properties/previousActivityExpenses", - "type": "object", - "patternProperties": { - "^[0-9]{4}$": { - "$id": "#/properties/previousActivityExpenses/year", - "type": "object", - "required": ["hithie", "mmis"], - "properties": { - "hithie": { - "$id": "#/properties/previousActivityExpenses/year/hithie", - "type": "object", - "required": ["federalActual", "totalApproved"], - "properties": { - "federalActual": { - "$id": "#/properties/previousActivityExpenses/year/hithie/federalActual", - "type": "number" - }, - "totalApproved": { - "$id": "#/properties/previousActivityExpenses/year/hithie/totalApproved", - "type": "number" - } - } - }, - "mmis": { - "$id": "#/properties/previousActivityExpenses/year/mmis", - "type": "object", - "required": ["50", "75", "90"], - "properties": { - "50": { - "$id": "#/properties/previousActivityExpenses/year/mmis/50", - "type": "object", - "required": ["federalActual", "totalApproved"], - "properties": { - "federalActual": { - "$id": "#/properties/previousActivityExpenses/year/mmis/50/federalActaul", - "type": "number" - }, - "totalApproved": { - "$id": "#/properties/previousActivityExpenses/year/mmis/50/totalApproved", - "type": "number" - } - } - }, - "75": { - "$id": "#/properties/previousActivityExpenses/year/mmis/75", - "type": "object", - "required": ["federalActual", "totalApproved"], - "properties": { - "federalActual": { - "$id": "#/properties/previousActivityExpenses/year/mmis/75/federalActual", - "type": "number" - }, - "totalApproved": { - "$id": "#/properties/previousActivityExpenses/year/mmis/75/totalApproved", - "type": "number" - } - } - }, - "90": { - "$id": "#/properties/previousActivityExpenses/year/mmis/90", - "type": "object", - "required": ["federalActual", "totalApproved"], - "properties": { - "federalActual": { - "$id": "#/properties/previousActivityExpenses/year/mmis/90/federalActual", - "type": "number" - }, - "totalApproved": { - "$id": "#/properties/previousActivityExpenses/year/mmis/90/totalApproved", - "type": "number" - } - } - } - } - } - } - } - } - }, - "previousActivitySummary": { - "$id": "#/properties/previousActivitySummary", - "type": "string" - }, - "programOverview": { - "$id": "#/properties/programOverview", - "type": "string" - }, - "stateProfile": { - "$id": "#/properties/stateProfile", - "type": "object", - "required": ["medicaidDirector", "medicaidOffice"], - "properties": { - "medicaidDirector": { - "$id": "#/properties/stateProfile/properties/medicaidDirector", - "type": "object", - "required": ["name", "email", "phone"], - "properties": { - "name": { - "$id": "#/properties/stateProfile/properties/medicaidDirector/properties/name", - "type": "string" - }, - "email": { - "$id": "#/properties/stateProfile/properties/medicaidDirector/properties/email", - "type": "string" - }, - "phone": { - "$id": "#/properties/stateProfile/properties/medicaidDirector/properties/phone", - "type": "string" - } - } - }, - "medicaidOffice": { - "$id": "#/properties/stateProfile/properties/medicaidOffice", - "type": "object", - "required": ["address1", "address2", "city", "state", "zip"], - "properties": { - "address1": { - "$id": "#/properties/stateProfile/properties/medicaidOffice/properties/address1", - "type": "string" - }, - "address2": { - "$id": "#/properties/stateProfile/properties/medicaidOffice/properties/address2", - "type": "string" - }, - "city": { - "$id": "#/properties/stateProfile/properties/medicaidOffice/properties/city", - "type": "string" - }, - "state": { - "$id": "#/properties/stateProfile/properties/medicaidOffice/properties/state", - "type": "string" - }, - "zip": { - "$id": "#/properties/stateProfile/properties/medicaidOffice/properties/zip", - "type": "string" - } - } - } - } - }, + "items": { "$ref": "activity.json" } + }, + "federalCitations": { "$ref": "federalCitations.json" }, + "incentivePayments": { "$ref": "incentivePayments.json" }, + "keyPersonnel": { "$ref": "keyPersonnel.json" }, + "narrativeHIE": { "type": "string" }, + "narrativeHIT": { "type": "string" }, + "narrativeMMIS": { "type": "string" }, + "previousActivityExpenses": { "$ref": "previousActivityExpenses.json" }, + "previousActivitySummary": { "type": "string" }, + "programOverview": { "type": "string" }, + "stateProfile": { "$ref": "stateProfile.json" }, "years": { - "$id": "#/properties/years", "type": "array", - "items": { - "$id": "#/properties/years/items", - "type": "string" - } + "items": { "type": "string" } } - } + }, + "additionalProperties": false } diff --git a/api/schemas/contractorResource.json b/api/schemas/contractorResource.json new file mode 100644 index 0000000000..5e98747c5b --- /dev/null +++ b/api/schemas/contractorResource.json @@ -0,0 +1,70 @@ +{ + "$id": "contractorResource.json", + "type": "object", + "required": [ + "description", + "end", + "hourly", + "name", + "start", + "totalCost", + "years" + ], + "properties": { + "description": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/description", + "type": "string" + }, + "end": { "$ref": "definitions.json#/optionalFullDate" }, + "hourly": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly", + "type": "object", + "required": ["data", "useHourly"], + "properties": { + "data": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/data", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year", + "type": "object", + "required": ["hours", "rate"], + "properties": { + "hours": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year/hours", + "$ref": "definitions.json#/optionalNumber" + }, + "rate": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/year/rate", + "$ref": "definitions.json#/optionalNumber" + } + } + } + } + }, + "useHourly": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/hourly/useHourly", + "type": "boolean" + } + } + }, + "name": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/name", + "type": "string" + }, + "start": { "$ref": "definitions.json#/optionalFullDate" }, + "totalCost": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/totalCost", + "type": "integer" + }, + "years": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/years", + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/activities/items/properties/contractorResources/items/properties/years/year", + "type": "number" + } + } + } + } +} diff --git a/api/schemas/costAllocation.json b/api/schemas/costAllocation.json new file mode 100644 index 0000000000..a8f044ba5e --- /dev/null +++ b/api/schemas/costAllocation.json @@ -0,0 +1,32 @@ +{ + "$id": "costAllocation.json", + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/activities/items/properties/costAllocation/year", + "type": "object", + "required": ["ffp", "other"], + "properties": { + "ffp": { + "$id": "#/properties/activities/items/properties/costAllocation/year/ffp", + "type": "object", + "required": ["federal", "state"], + "properties": { + "federal": { + "$id": "#/properties/activities/items/properties/costAllocation/year/ffp/federal", + "type": "number" + }, + "state": { + "$id": "#/properties/activities/items/properties/costAllocation/year/ffp/state", + "type": "number" + } + } + }, + "other": { + "$id": "#/properties/activities/items/properties/costAllocation/year/other", + "type": "number" + } + } + } + } +} diff --git a/api/schemas/costAllocationNarrative.json b/api/schemas/costAllocationNarrative.json new file mode 100644 index 0000000000..d053b46346 --- /dev/null +++ b/api/schemas/costAllocationNarrative.json @@ -0,0 +1,19 @@ +{ + "$id": "costAllocationNarrative.json", + "type": "object", + "required": ["methodology"], + "properties": { + "methodology": { + "type": "string" + } + }, + "patternProperties": { + "^[0-9]{4}$": { + "required": ["otherSources"], + "type": "object", + "properties": { + "otherSources": { "type": "string" } + } + } + } +} diff --git a/api/schemas/definitions.json b/api/schemas/definitions.json new file mode 100644 index 0000000000..0401dcab55 --- /dev/null +++ b/api/schemas/definitions.json @@ -0,0 +1,12 @@ +{ + "$id": "definitions.json", + "optionalFullDate": { + "type": "string" + }, + "optionalNumber": { + "anyOf": [ + { "type": "number" }, + { "type": "string", "pattern": "\\d*" } + ] + } +} diff --git a/api/schemas/expense.json b/api/schemas/expense.json new file mode 100644 index 0000000000..1551fb1044 --- /dev/null +++ b/api/schemas/expense.json @@ -0,0 +1,25 @@ +{ + "$id": "expense.json", + "type": "object", + "required": ["description", "category", "years"], + "properties": { + "description": { + "$id": "#/properties/activities/items/properties/expenses/items/properties/description", + "type": "string" + }, + "category": { + "$id": "#/properties/activities/items/properties/expenses/items/properties/category", + "type": "string" + }, + "years": { + "$id": "#/properties/activities/items/properties/expenses/items/properties/years", + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/activities/items/properties/expenses/items/properties/years/year", + "type": "number" + } + } + } + } +} diff --git a/api/schemas/federalCitations.json b/api/schemas/federalCitations.json new file mode 100644 index 0000000000..c64f042cdd --- /dev/null +++ b/api/schemas/federalCitations.json @@ -0,0 +1,27 @@ +{ + "$id": "federalCitations.json", + "type": "object", + "required": [], + "patternProperties": { + "^.+$": { + "type": "array", + "items": { + "type": "object", + "required": ["title", "checked", "explanation"], + "properties": { + "title": { + "type": "string" + }, + "checked": { + "type": ["boolean", "string"], + "pattern": "^$" + }, + "explanation": { + "type": "string" + } + } + } + } + }, + "additionalProperties": false +} diff --git a/api/schemas/incentivePayments.json b/api/schemas/incentivePayments.json new file mode 100644 index 0000000000..334bee7252 --- /dev/null +++ b/api/schemas/incentivePayments.json @@ -0,0 +1,24 @@ +{ + "$id": "incentivePayments.json", + "type": "object", + "required": ["ehAmt", "ehCt", "epAmt", "epCt"], + "patternProperties": { + "^e(h|p)(Amt|Ct)$": { + "$id": "#/properties/incentivePayments/type", + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/incentivePayments/type/year", + "type": "object", + "required": ["1", "2", "3", "4"], + "patternProperties": { + "^[0-9]$": { + "$id": "#/properties/incentivePayments/type/year/quarter", + "$ref": "definitions.json#/optionalNumber" + } + } + } + } + } + } +} diff --git a/api/schemas/index.js b/api/schemas/index.js new file mode 100644 index 0000000000..909bfcaf53 --- /dev/null +++ b/api/schemas/index.js @@ -0,0 +1,37 @@ +/* eslint-disable import/no-dynamic-require, global-require */ +const Ajv = require('ajv'); + +// all schemas, except the base apd document schema +const schemas = [ + "activity.json", + "contractorResource.json", + "costAllocation.json", + "costAllocationNarrative.json", + "definitions.json", + "expense.json", + "federalCitations.json", + "incentivePayments.json", + "keyPersonnel.json", + "objective.json", + "person.json", + "previousActivityExpenses.json", + "stateProfile.json" +].map(schema => require(`./${schema}`)); + +const apdSchema = require('./apd.json'); + +const options = { + allErrors: true, + jsonPointers: true, + // Do not remove APD fields when testing. Our example APD documents should not + // have any additional or extraneous fields. Ideally, this would be false, always. + removeAdditional: process.env.NODE_ENV !== 'test' +}; + +const ajv = new Ajv(options); +schemas.forEach(schema => ajv.addSchema(schema)); +const validateApd = ajv.compile(apdSchema); + +module.exports = { + validateApd +}; diff --git a/api/schemas/keyPersonnel.json b/api/schemas/keyPersonnel.json new file mode 100644 index 0000000000..43f39a5e61 --- /dev/null +++ b/api/schemas/keyPersonnel.json @@ -0,0 +1,41 @@ +{ + "$id": "keyPersonnel.json", + "type": "array", + "items": { + "type": "object", + "required": [ + "name", + "position", + "email", + "isPrimary", + "fte", + "hasCosts", + "costs" + ], + "properties": { + "name": { "type": "string" }, + "position": { "type": "string" }, + "email": { "type": "string" }, + "isPrimary": { "type": "boolean" }, + "fte": { + "type": "object", + "patternProperties": { + "^[0-9]{0,2}": { + "type": "number" + } + } + }, + "hasCosts": { + "type": "boolean" + }, + "costs": { + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "type": "number" + } + } + } + } + } +} diff --git a/api/schemas/objective.json b/api/schemas/objective.json new file mode 100644 index 0000000000..bb0af97f4a --- /dev/null +++ b/api/schemas/objective.json @@ -0,0 +1,34 @@ +{ + "$id": "objective.json", + "type": "object", + "required": ["keyResults", "objective"], + "properties": { + "keyResults": { + "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults", + "type": "array", + "items": { + "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items", + "type": "object", + "required": ["baseline", "keyResult", "target"], + "properties": { + "baseline": { + "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/baseline", + "type": "string" + }, + "keyResult": { + "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/keyResult", + "type": "string" + }, + "target": { + "$id": "#/properties/activities/items/properties/objectives/items/properties/keyResults/items/properties/target", + "type": "string" + } + } + } + }, + "objective": { + "$id": "#/properties/activities/items/properties/goals/items/properties/objective", + "type": "string" + } + } +} diff --git a/api/schemas/person.json b/api/schemas/person.json new file mode 100644 index 0000000000..f1ca3eac19 --- /dev/null +++ b/api/schemas/person.json @@ -0,0 +1,22 @@ +{ + "$id": "person.json", + "type": "object", + "required": ["title", "description", "years"], + "properties": { + "title": { "type": "string" }, + "description": { "type": "string" }, + "years": { + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "type": "object", + "required": ["amt", "perc"], + "properties": { + "amt": { "$ref": "definitions.json#/optionalNumber" }, + "perc": { "$ref": "definitions.json#/optionalNumber" } + } + } + } + } + } +} diff --git a/api/schemas/previousActivityExpenses.json b/api/schemas/previousActivityExpenses.json new file mode 100644 index 0000000000..6366bf540d --- /dev/null +++ b/api/schemas/previousActivityExpenses.json @@ -0,0 +1,80 @@ +{ + "$id": "previousActivityExpenses.json", + "type": "object", + "patternProperties": { + "^[0-9]{4}$": { + "$id": "#/properties/previousActivityExpenses/year", + "type": "object", + "required": ["hithie", "mmis"], + "properties": { + "hithie": { + "$id": "#/properties/previousActivityExpenses/year/hithie", + "type": "object", + "required": ["federalActual", "totalApproved"], + "properties": { + "federalActual": { + "$id": "#/properties/previousActivityExpenses/year/hithie/federalActual", + "type": "number" + }, + "totalApproved": { + "$id": "#/properties/previousActivityExpenses/year/hithie/totalApproved", + "type": "number" + } + } + }, + "mmis": { + "$id": "#/properties/previousActivityExpenses/year/mmis", + "type": "object", + "required": ["50", "75", "90"], + "properties": { + "50": { + "$id": "#/properties/previousActivityExpenses/year/mmis/50", + "type": "object", + "required": ["federalActual", "totalApproved"], + "properties": { + "federalActual": { + "$id": "#/properties/previousActivityExpenses/year/mmis/50/federalActaul", + "type": "number" + }, + "totalApproved": { + "$id": "#/properties/previousActivityExpenses/year/mmis/50/totalApproved", + "type": "number" + } + } + }, + "75": { + "$id": "#/properties/previousActivityExpenses/year/mmis/75", + "type": "object", + "required": ["federalActual", "totalApproved"], + "properties": { + "federalActual": { + "$id": "#/properties/previousActivityExpenses/year/mmis/75/federalActual", + "type": "number" + }, + "totalApproved": { + "$id": "#/properties/previousActivityExpenses/year/mmis/75/totalApproved", + "type": "number" + } + } + }, + "90": { + "$id": "#/properties/previousActivityExpenses/year/mmis/90", + "type": "object", + "required": ["federalActual", "totalApproved"], + "properties": { + "federalActual": { + "$id": "#/properties/previousActivityExpenses/year/mmis/90/federalActual", + "type": "number" + }, + "totalApproved": { + "$id": "#/properties/previousActivityExpenses/year/mmis/90/totalApproved", + "type": "number" + } + } + } + } + } + } + } + } +} diff --git a/api/schemas/stateProfile.json b/api/schemas/stateProfile.json new file mode 100644 index 0000000000..1e1f4a1da6 --- /dev/null +++ b/api/schemas/stateProfile.json @@ -0,0 +1,27 @@ +{ + "$id": "stateProfile.json", + "type": "object", + "required": ["medicaidDirector", "medicaidOffice"], + "properties": { + "medicaidDirector": { + "type": "object", + "required": ["name", "email", "phone"], + "properties": { + "name": { "type": "string" }, + "email": { "type": "string" }, + "phone": { "type": "string" } + } + }, + "medicaidOffice": { + "type": "object", + "required": ["address1", "address2", "city", "state", "zip"], + "properties": { + "address1": { "type": "string" }, + "address2": { "type": "string" }, + "city": { "type": "string" }, + "state": { "type": "string" }, + "zip": { "type": "string" } + } + } + } +} diff --git a/api/seeds/development/apds.js b/api/seeds/development/apds.js index c8eae1d6e6..afb96e50b4 100644 --- a/api/seeds/development/apds.js +++ b/api/seeds/development/apds.js @@ -1,1106 +1,1144 @@ -exports.seed = async knex => { - const { state_id } = await knex('users').first('state_id'); // eslint-disable-line camelcase +const logger = require('../../logger')('seeds'); +const { validateApd } = require('../../schemas'); - await knex('apds') // eslint-disable-line camelcase - .insert([ +const apd = { + status: 'draft', + years: '["2020", "2021"]', + document: { + name: 'HITECH IAPD', + activities: [ { - state_id, - status: 'draft', - years: '["2020", "2021"]', - document: { - name: 'HITECH IAPD', - activities: [ - { - alternatives: - '

Modifications to State Level Registry (SLR)

\n\n

The 2015-2017 rule changes are significant and wide ranging; minimally accommodating the new attestations will be problematic for the remainder of the program. Program benefits will potentially not be maximized. To be prepared for Stage 3 and to properly implement all 2015-2017 rule changes; Tycho plans to implement all necessary modifications.

\n\n

There are no significant disadvantages to this option.

\n

\n

Implementing the changes as outlined provide the optimal opportunity to maximize the benefits of the EHR program and its impact on the delivery of health care with improved quality and outcomes.

\n', - contractorResources: [ - { - description: 'Maintain SLR', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - name: 'Super SLR Incorporated', - start: '', - totalCost: 32423, - years: { - '2020': 999756, - '2021': 342444 - } - }, - { - description: 'Technology consulting and planning services.', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - name: 'Tech Consulting Inc.', - start: '', - totalCost: 473573, - years: { '2020': 333000, '2021': 200000 } - } - ], - costAllocation: { + alternatives: + '

Modifications to State Level Registry (SLR)

\n\n

The 2015-2017 rule changes are significant and wide ranging; minimally accommodating the new attestations will be problematic for the remainder of the program. Program benefits will potentially not be maximized. To be prepared for Stage 3 and to properly implement all 2015-2017 rule changes; Tycho plans to implement all necessary modifications.

\n\n

There are no significant disadvantages to this option.

\n

\n

Implementing the changes as outlined provide the optimal opportunity to maximize the benefits of the EHR program and its impact on the delivery of health care with improved quality and outcomes.

\n', + contractorResources: [ + { + description: 'Maintain SLR', + end: '', + hourly: { + data: { '2020': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 + hours: '', + rate: '' }, '2021': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 - } - }, - costAllocationNarrative: { - methodology: - '

No cost allocation is necessary for this activity.

\n', - otherSources: - '

No other funding is provided for this activity.

\n' - }, - description: - '

III.A.1: Modifications to the State Level Repository

\n

Tycho Medicaid is seeking funding to design, develop, and implement modifications to the existing State Level Repository (SLR) for continued administration of the EHR Incentive Program. The modifications of the SLR for CMS program rule changes and guidance changes (Stage 3, IPPS, and OPPS) will require extensive development and implementation efforts and is essential to the effective administration of the Medicaid EHR Incentive Program. Modifications to the SLR are done in phases depending on how CMS rule changes occur. The implementation of the design elements will require provider onboarding activities to be initiated and completed including outreach and training for all program participants. The SLR will increase the efficiency with which Tycho Medicaid administers the program; allow for increased oversight and assure that the program is operated in accordance with the complex and evolving program rules and requirements.

\n

\n

Additionally, Tycho Medicaid is seeking funding to complete a security risk assessment for the State Level Repository to ensure the SLR meets the required system security standards for HIPAA, MARSe, NIST and other state and federal security requirements for information technology.

\n

\n

III.B.1 Administrative and Technical Support Consulting

\n

The DHSS is requesting funding to support activities under the Medicaid EHR Incentive Payment Program to provide technical assistance for statewide activities and implementations. Activities of this initiative will include support of the activities included in this IAPDU, SMPHU development, eCQM implementation, project management services, and assistance with the public health expansion modernization initiative.

\n', - expenses: [ - { - description: '', - category: 'Training and outreach', - years: { '2020': 40000, '2021': 40000 } - }, - { - description: '', - category: 'Travel', - years: { '2020': 35000, '2021': 35000 } - }, - { - description: '', - category: 'Hardware, software, and licensing', - years: { '2020': 700000, '2021': 0 } + hours: '', + rate: '' } - ], - fundingSource: 'HIT', - objectives: [ - { - objective: - 'Accept attestations for 2018, and modify SLR to meet new spec sheets released by CMS.', - keyResults: [ - { - baseline: '13% complete', - keyResult: 'Complete SLR modifications by 11/1/18', - target: '100% complete' - }, - { - baseline: 'not accepting attestations', - keyResult: 'Accept attestations through 4/30/19.', - target: 'all attestations accepted' - } - ] - }, - { - objective: - 'Provide support to EPs and EHs through attestation process.', - keyResults: [ - { - baseline: 'not available', - keyResult: "Guidance available on Tycho's websites", - target: 'available' - }, - { - baseline: 'not available', - keyResult: 'Office hours availble for EPs and EHs', - target: 'available' - }, - { - baseline: 'unvisited sites', - keyResult: 'Site visits, as needed, for EPs and EHs', - target: 'sites visited' - } - ] - } - ], - name: 'Program Administration', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2018-09-07', - milestone: - 'Implementation of Final Rule and Stage 3 System Developments' - }, - { - endDate: '2017-12-31', - milestone: 'Environmental Scan Completion' - }, - { - endDate: '2018-05-30', - milestone: 'HIT Roadmap Development' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' }, - statePersonnel: [ - { - title: 'Project Assistant', - description: - 'Coordination and document management support daily administrative support such as meeting minutes and scribe, manages project library, scheduling, and correspondence tracking.', - years: { - '2020': { amt: 86000, perc: 1 }, - '2021': { amt: 88000, perc: 1 } - } - }, - { - title: - 'EHR Incentive Program Meaningful Use Coordinator (Research Analyst III)', - description: - 'Develop and monitor reports, assist data users in developing and managing queries.', - years: { - '2020': { amt: 101115, perc: 1 }, - '2021': { amt: 102111, perc: 1 } - } - }, - { - title: 'IT Liaison', - description: - 'Provide analysis and coordination activities between the HIT Program Office and the IT section, to ensure that adequate resources and priority are established to complete the technology projects as identified.', - years: { - '2020': { amt: 101000, perc: 1 }, - '2021': { amt: 104000, perc: 1 } - } - }, - { - title: 'Accountant III', - description: - 'Coordinate program state and federal budget and expense reporting, review and validate charges to CMS federal reports.', - years: { - '2020': { amt: 101000, perc: 3 }, - '2021': { amt: 109000, perc: 3 } - } - }, - { - title: 'Public Information Officer', - description: - 'Develop outreach materials including: written, television and radio publications to support outreach for the Medicaid EHR Incentive Program', - years: { - '2020': { amt: 165000, perc: 0.5 }, - '2021': { amt: 170000, perc: 0.5 } - } - }, - { - title: 'Systems Chief', - description: - 'Coordinate office resources, manage staff, budget, and resource assignments, and report program status.', - years: { - '2020': { amt: 135000, perc: 0.5 }, - '2021': { amt: 140000, perc: 0.5 } - } - }, - { - title: - 'Medicaid EHR Incentive Program Manager (Medical Assistance Administrator III)', - description: - 'Data collection and analysis, reporting, planning, service delivery modification, support administration of the EHR Incentive Payment Program including provider application review.', - years: { - '2020': { amt: 110012, perc: 1 }, - '2021': { amt: 111102, perc: 1 } - } - }, - { - title: 'System Analyst (Analyst Programmer IV)', - description: - 'Supports design, development and implementation of information technology infrastructure for the projects/programs under the IT Planning office supported by this Implementation Advanced Planning Document.', - years: { - '2020': { amt: 98987, perc: 4 }, - '2021': { amt: 99897, perc: 4 } - } - } - ], - summary: - 'Continued Operations of the Medicaid EHR Incentive Payment Program, includes modifications to the SLR, HIT staff, auditing, outreach, and non-personnel expenses for administering the program.', - quarterlyFFP: { - '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - }, - '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - } - } + useHourly: false }, - { - alternatives: - "

Medicaid Claims Data Feed to the HIE

\n

Periodic Uploads of Medicaid Claims Data from MMIS to the HIE

\n

The HIE could consume Medicaid claims data from periodic uploads of an extract/export from the MMIS

\n

Increase of administrative burden on development staff.

\n

Short term cost savings, with a higher long-term cost. No real-time data.

\n

The periodic MMIS uploads would not provide real time data. Therefore, Tycho plans to use a Medicaid claims data feed

\n

Medicaid Claims Data Feed to the HIE

\n

Create a Medicaid Claims Data Feed to the HIE

\n

Implementing a Medicaid Claims Data Feed to the HIE would provide information regarding Medicaid claims to participating providers, Hospitals, and patients

\n

Data regarding medications prescribed, tests performed, and the resulting diagnosis would improve care coordination

\n

There are no significant disadvantages to this option

\n

Implementing a Medicaid Claims data feed to the HIE provides updated claims data in real-time to improve care coordination and increase MU. Because data is updated in real-time, a data feed meets Tycho's needs

\n", - contractorResources: [ - { - description: 'Hosting and development support.', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - - name: 'Interface Vendor Inc.', - start: '', - totalCost: 26453574, - years: { '2020': 650000, '2021': 750000 } - }, - { - description: 'Interface M&O contractor.', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - name: 'TBD', - start: '', - totalCost: 7398, - years: { '2020': 0, '2021': 1000000 } - } - ], - costAllocation: { + name: 'Super SLR Incorporated', + start: '', + totalCost: 32423, + years: { + '2020': 999756, + '2021': 342444 + } + }, + { + description: 'Technology consulting and planning services.', + end: '', + hourly: { + data: { '2020': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 + hours: '', + rate: '' }, '2021': { - ffp: { - federal: 75, - state: 25 - }, - other: 0 + hours: '', + rate: '' } }, - costAllocationNarrative: { - methodology: - '

No cost allocation is necessary for this activity.

\n', - otherSources: '' + useHourly: false + }, + name: 'Tech Consulting Inc.', + start: '', + totalCost: 473573, + years: { '2020': 333000, '2021': 200000 } + } + ], + costAllocation: { + '2020': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + }, + '2021': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + } + }, + costAllocationNarrative: { + methodology: '

No cost allocation is necessary for this activity.

\n', + '2020': { + otherSources: '

No other funding is provided for this activity for FFY 2020.

\n' + }, + '2021': { + otherSources: '

No other funding is provided for this activity for FFY 2021.

\n' + } + }, + description: + '

III.A.1: Modifications to the State Level Repository

\n

Tycho Medicaid is seeking funding to design, develop, and implement modifications to the existing State Level Repository (SLR) for continued administration of the EHR Incentive Program. The modifications of the SLR for CMS program rule changes and guidance changes (Stage 3, IPPS, and OPPS) will require extensive development and implementation efforts and is essential to the effective administration of the Medicaid EHR Incentive Program. Modifications to the SLR are done in phases depending on how CMS rule changes occur. The implementation of the design elements will require provider onboarding activities to be initiated and completed including outreach and training for all program participants. The SLR will increase the efficiency with which Tycho Medicaid administers the program; allow for increased oversight and assure that the program is operated in accordance with the complex and evolving program rules and requirements.

\n

\n

Additionally, Tycho Medicaid is seeking funding to complete a security risk assessment for the State Level Repository to ensure the SLR meets the required system security standards for HIPAA, MARSe, NIST and other state and federal security requirements for information technology.

\n

\n

III.B.1 Administrative and Technical Support Consulting

\n

The DHSS is requesting funding to support activities under the Medicaid EHR Incentive Payment Program to provide technical assistance for statewide activities and implementations. Activities of this initiative will include support of the activities included in this IAPDU, SMPHU development, eCQM implementation, project management services, and assistance with the public health expansion modernization initiative.

\n', + expenses: [ + { + description: '', + category: 'Training and outreach', + years: { '2020': 40000, '2021': 40000 } + }, + { + description: '', + category: 'Travel', + years: { '2020': 35000, '2021': 35000 } + }, + { + description: '', + category: 'Hardware, software, and licensing', + years: { '2020': 700000, '2021': 0 } + } + ], + fundingSource: 'HIT', + objectives: [ + { + objective: + 'Accept attestations for 2018, and modify SLR to meet new spec sheets released by CMS.', + keyResults: [ + { + baseline: '13% complete', + keyResult: 'Complete SLR modifications by 11/1/18', + target: '100% complete' }, - description: - "

III.B.3 Medicaid Claims Data Feed to the HIE

\n

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n", - expenses: [ - { - description: '', - category: 'Travel', - years: { '2020': 0, '2021': 0 } - } - ], - fundingSource: 'MMIS', - objectives: [ - { - objective: - 'Build interface between the MMIS Data Warehouse (DW) and the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE.', - keyResults: [ - { - baseline: 'no contractor', - keyResult: - 'Hire contracted support to build an open API for the DW that the HIE and PHR can consume.', - target: 'yes contractor' - }, - { - baseline: 'no support', - keyResult: 'Provide support for using open API for DW', - target: 'yes support' - } - ] - } - ], - name: 'HIE Claims Data Analytics', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2018-12-31', - milestone: 'Implement MMIS-HIE Interface' - }, - { - endDate: '2018-12-31', - milestone: 'Develop MMIS-HIE Interface Requirements' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' + { + baseline: 'not accepting attestations', + keyResult: 'Accept attestations through 4/30/19.', + target: 'all attestations accepted' + } + ] + }, + { + objective: + 'Provide support to EPs and EHs through attestation process.', + keyResults: [ + { + baseline: 'not available', + keyResult: "Guidance available on Tycho's websites", + target: 'available' }, - statePersonnel: [ - { - title: 'Project Assistant', - description: 'Assist with stuff', - years: { - '2020': { amt: 98000, perc: 1 }, - '2021': { amt: 99000, perc: 1 } - } - }, - { - title: 'MMIS Project Manager', - description: - 'This position is responsible for the program development, planning, coordination, evaluation, independent management and oversight of the Tycho Automated Info', - years: { - '2020': { amt: 140000, perc: 1 }, - '2021': { amt: 144000, perc: 1 } - } - }, - { - title: 'MMIS Trainer', - description: - 'Under the direct supervision of the Project Manager, this position is responsible for the development of a comprehensive training and support program for the Tycho Automated Information Management System', - years: { - '2020': { amt: 115000, perc: 1 }, - '2021': { amt: 115000, perc: 1 } - } - }, - { - title: 'Programmer IV', - description: - 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', - years: { - '2020': { amt: 140000, perc: 1 }, - '2021': { amt: 145000, perc: 1 } - } - }, - { - title: 'Security IT', - description: 'Make sure its secure.', - years: { - '2020': { amt: 115000, perc: 1 }, - '2021': { amt: 120000, perc: 1 } - } - }, - { - title: 'Operations Specialist', - description: 'Run the day to day.', - years: { - '2020': { amt: 125000, perc: 1 }, - '2021': { amt: 130000, perc: 1 } - } - }, - { - title: 'Programmer V', - description: - 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', - years: { - '2020': { amt: 150000, perc: 2 }, - '2021': { amt: 155000, perc: 3 } - } - }, - { - title: 'Programmer III', - description: - 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', - years: { - '2020': { amt: 120000, perc: 1 }, - '2021': { amt: 125000, perc: 1 } - } - } - ], - summary: - 'To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. ', - quarterlyFFP: { + { + baseline: 'not available', + keyResult: 'Office hours availble for EPs and EHs', + target: 'available' + }, + { + baseline: 'unvisited sites', + keyResult: 'Site visits, as needed, for EPs and EHs', + target: 'sites visited' + } + ] + } + ], + name: 'Program Administration', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2018-09-07', + milestone: + 'Implementation of Final Rule and Stage 3 System Developments' + }, + { + endDate: '2017-12-31', + milestone: 'Environmental Scan Completion' + }, + { + endDate: '2018-05-30', + milestone: 'HIT Roadmap Development' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: 'Project Assistant', + description: + 'Coordination and document management support daily administrative support such as meeting minutes and scribe, manages project library, scheduling, and correspondence tracking.', + years: { + '2020': { amt: 86000, perc: 1 }, + '2021': { amt: 88000, perc: 1 } + } + }, + { + title: + 'EHR Incentive Program Meaningful Use Coordinator (Research Analyst III)', + description: + 'Develop and monitor reports, assist data users in developing and managing queries.', + years: { + '2020': { amt: 101115, perc: 1 }, + '2021': { amt: 102111, perc: 1 } + } + }, + { + title: 'IT Liaison', + description: + 'Provide analysis and coordination activities between the HIT Program Office and the IT section, to ensure that adequate resources and priority are established to complete the technology projects as identified.', + years: { + '2020': { amt: 101000, perc: 1 }, + '2021': { amt: 104000, perc: 1 } + } + }, + { + title: 'Accountant III', + description: + 'Coordinate program state and federal budget and expense reporting, review and validate charges to CMS federal reports.', + years: { + '2020': { amt: 101000, perc: 3 }, + '2021': { amt: 109000, perc: 3 } + } + }, + { + title: 'Public Information Officer', + description: + 'Develop outreach materials including: written, television and radio publications to support outreach for the Medicaid EHR Incentive Program', + years: { + '2020': { amt: 165000, perc: 0.5 }, + '2021': { amt: 170000, perc: 0.5 } + } + }, + { + title: 'Systems Chief', + description: + 'Coordinate office resources, manage staff, budget, and resource assignments, and report program status.', + years: { + '2020': { amt: 135000, perc: 0.5 }, + '2021': { amt: 140000, perc: 0.5 } + } + }, + { + title: + 'Medicaid EHR Incentive Program Manager (Medical Assistance Administrator III)', + description: + 'Data collection and analysis, reporting, planning, service delivery modification, support administration of the EHR Incentive Payment Program including provider application review.', + years: { + '2020': { amt: 110012, perc: 1 }, + '2021': { amt: 111102, perc: 1 } + } + }, + { + title: 'System Analyst (Analyst Programmer IV)', + description: + 'Supports design, development and implementation of information technology infrastructure for the projects/programs under the IT Planning office supported by this Implementation Advanced Planning Document.', + years: { + '2020': { amt: 98987, perc: 4 }, + '2021': { amt: 99897, perc: 4 } + } + } + ], + summary: + 'Continued Operations of the Medicaid EHR Incentive Payment Program, includes modifications to the SLR, HIT staff, auditing, outreach, and non-personnel expenses for administering the program.', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + }, + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } + } + }, + { + alternatives: + "

Medicaid Claims Data Feed to the HIE

\n

Periodic Uploads of Medicaid Claims Data from MMIS to the HIE

\n

The HIE could consume Medicaid claims data from periodic uploads of an extract/export from the MMIS

\n

Increase of administrative burden on development staff.

\n

Short term cost savings, with a higher long-term cost. No real-time data.

\n

The periodic MMIS uploads would not provide real time data. Therefore, Tycho plans to use a Medicaid claims data feed

\n

Medicaid Claims Data Feed to the HIE

\n

Create a Medicaid Claims Data Feed to the HIE

\n

Implementing a Medicaid Claims Data Feed to the HIE would provide information regarding Medicaid claims to participating providers, Hospitals, and patients

\n

Data regarding medications prescribed, tests performed, and the resulting diagnosis would improve care coordination

\n

There are no significant disadvantages to this option

\n

Implementing a Medicaid Claims data feed to the HIE provides updated claims data in real-time to improve care coordination and increase MU. Because data is updated in real-time, a data feed meets Tycho's needs

\n", + contractorResources: [ + { + description: 'Hosting and development support.', + end: '', + hourly: { + data: { '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } + hours: '', + rate: '' }, '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } + hours: '', + rate: '' } - } + }, + useHourly: false }, - { - alternatives: - '

Health Information Exchange

\n

Maintain existing system.

\n

The existing system has a few benefits. The current EDI process while dated still forms the backbone of the Division’s data sharing needs. The technology works in the fashion that it always has.

\n

The drawbacks of this approach are significant. While the current Edi process affords behavioral health agencies to submit their data to the state, it does not allow for sharing the same data to other providers in either the primary care or behavioral health treatment contexts.

\n

There are more disadvantages than advantages in pursuing this approach. The drawbacks are substantial, such as absence of data normalization, difficulties with aligning the user interface and application design with industry best practices, inconsistencies in design, and difficulties with support and maintenance, making this approach less favorable than the other two alternatives considered.

\n

Health Information Exchange

\n

Update and Enhance Existing System(s), connecting AKAIMS to the Health Information Exchange

\n

Connecting AKAIMS to the Health Information Exchange will provide for the sending and receiving of data across healthcare disciplines. This data sharing is thought to enhance and provide for better care outcomes for patients who are participating in care across multiple providers. This solution future proofs AKAIMS as it will integrate current technologies and leverages those technologies for a more feature rich process.

\n

Training and integration of this updated technology will require some effort and outreach. Newly on-boarded agencies will need to adjust to new data collection protocols.

\n

Full participation in the Health Information Exchange will reduce double data entry at all levels (reducing costs). It is anticipated that efficiencies gained with simplification of data collection and reporting will greatly enhance patient care outcomes.

\n

HIE Platform

\n

Upgrade HIE to the Audacious Inquiry (Ai) platform

\n

Ai offers a strong foundation on which additional functionality can be built. Transitioning to the Ai platform has the potential to minimize the effort required to modernize the HIE, while delivering additional services to users.

\n

Transitioning to Ai means that the State will be leaving the current HIE platform. There is potential risk in adoption and migration of services and data.

\n

The HIE platform will be transitioned to Ai to offer additional services, contain costs on enhancements, and maximize the scalability and flexibility of the HIE to support modernization across the enterprise.

\n

HIE Platform

\n

Keep platform as it is without upgrade.

\n

Keeping the platform as it is without upgrade would allow focus to remain on onboarding.

\n

Functionality supported by existing HIE is not adequate to support future applications. The value delivered by the service as it is could be improved with additional functionality. Potential to ingest different critical types of data is limited without a platform upgrade.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

\n

HIE Platform

\n

Partner with another state HIE for services ranging from sharing the platform itself, to specific services or commonly-developed interfaces.

\n

Sharing with another state offers the potential to

\n

• decrease costs

\n

• Increase speed of onboarding

\n

• Increase functionality

\n

• Provide for greater sustainability

\n

• Address the needs of our partners faster or better

\n

No states currently share HIE services entirely, due to perceived legal constraints; this option presents multiple factors to consider ranging from legal to technical. Potential for cost savings is limited because pricing models are usually based on volume. There is a possibility for significant disruption to service during a transition of this type; significant issues with legal arrangements complying with other states.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

HIE Tools for Care Coordination

\n

Add functional tools to support care coordination, referrals and analytics through other module developers or collaborators

\n

Sharing with another state or regional HIE to develop or utilize HIE tools offers the potential to

\n

• decrease costs

\n

• Increase speed of onboarding

\n

• Increase functionality

\n

• Provide for greater sustainability

\n

• Address the needs of our partners faster or better

\n

If another commercial developer is selected to offer these modules, there is some likelihood that integrating into the HIE platform will be more difficult without the transition to Ai.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

HIE Functionality

\n

Enhancing functionality for participating hospitals

\n

Hospitals are critical stakeholders in the HIE. Providing functionality to assist hospitals in meeting MU3 and in evaluating ER patients are two areas where HIE could provide valuable information.

\n

Hospital focus is based on patient safety. Thus far, there has been little incentive for using HIE data for patient safety.

\n

DHSS is actively pursuing additional functionality for hospitals. This involves hospital stakeholder meetings, vendor discussions, board review and clinical workgroup input.

\n

\n

HIE Functionality

\n

Implement connections with high-value state and federal data sources (Corrections, DJJ, SSA, DoD)

\n

Including health data from correctional facilities (ADT, ORU and/or CCD files) will help provide better more coordinated care for this vulnerable population, many of whom are also Medicaid-eligible.

\n

Aside from the need to allocate staff time across projects, there are no significant drawbacks to this option.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding state and federal data source connections

\n

Less work for the HIE team, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules.

\n

Leaving the information gap among these agencies open will lead to continued delays in needed services.

\n

This option is not preferred.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding emergency department information exchange

\n

Giving providers better tools to coordinate care for high-risk, high-utilizer members of the population has the potential to substantially reduce spending and improve outcomes for this vulnerable population.

\n

Aside from the need to allocate staff time across projects, there are no significant drawbacks to this option.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding prescription information

\n

Less work for the HIE, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules

\n

A continuing information gap around prescriptions filled will limit the potential to improve care coordination for Tycho citizens and heighten patient safety.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding image exchange

\n

Less work for the HIE, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules

\n

The lack of simple diagnostic image exchange presents a significant barrier to widespread health information exchange. Without these technologies, patients often hand-carry their films or electronic files with them, which can present a high risk of lost images and inefficiency.

\n

This option is not preferred at this time.

\n', - contractorResources: [ - { - description: '', - end: '', - hourly: { - data: { - '2020': { hours: '', rate: '' }, - '2021': { hours: '', rate: '' } - }, - useHourly: false - }, - name: '', - start: '', - totalCost: 3496874, - years: { '2020': 0, '2021': 0 } - } - ], - costAllocation: { + name: 'Interface Vendor Inc.', + start: '', + totalCost: 26453574, + years: { '2020': 650000, '2021': 750000 } + }, + { + description: 'Interface M&O contractor.', + end: '', + hourly: { + data: { '2020': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 + hours: '', + rate: '' }, '2021': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 + hours: '', + rate: '' } }, - costAllocationNarrative: { - methodology: '', - otherSources: '' - }, - description: - "

\n\"undefined\"\n

\n

\n

III.D. Statewide HIE Enhancement, Onboarding, and Support of Statewide HIE Operational Strategic Plan

\n

DHSS is requesting funding to support the continued enhancement and provider onboarding activities to the statewide HIE. The success of the statewide HIE is critical for improving data exchange, coordination of care, and modernizing healthcare across Tycho. The following funding requests are for projects that will provide enhanced technical capabilities to providers, support providers in onboarding, support modernizations required for Medicaid redesign, and ensure sustainability beyond State of Tycho and CMS funding. The projects have been designed to meet the following goals and desires for the statewide HIE:

\n\n

III.D.1 Behavioral Health Onboarding & Care Coordination

\n

The Department recognizes the need to increase Behavioral Health (BH) data capacity and sharing to achieve its goals and objectives related to care coordination. This includes promoting effective communication to coordinate care and enhancing the ability for providers to share and gain access to Protected Class Patient Data where appropriate. To support the capacity of data sharing and improving coordination of care, funding is requested to support Behavioral Health provider connectivity through the onboarding program by the development and implementation of a Behavioral Health-centric Unified Landing Page Application. The Behavioral Health Unified Landing Page Application will improve the quality and completeness of behavioral health data and thus, support the ability for providers to achieve MU.

\n

\n

In addition to the Unified Landing Page, funding is requested to support behavioral health provider onboarding to the HIE. The HIE onboarding program will provide funds to offset expenses required for behavioral health providers to adequately participate in statewide health information exchange. The onboarding program will support Tycho's HIE vision of increasing onboarding Medicaid providers and care coordination to help Tycho providers demonstrate MU. This program relates to the guidance provided by CMS in the SMD 16-003 letter dated February 2016 and will assist with covering costs associated with connectivity including but not limited to the following activities:

\n\n

The goal is for the onboarding program to support 40 provider organizations across the State. The initial phase of the program will be focused on Medicaid behavioral health providers with additional provider types potentially targeted in later phases of the initiative. Administrative offset funding will be on-time funding only and will be issued as pass-through funding through healtheConnect (Tycho's HIE organization). The funding will be distributed in 2 parts: 75% upon onboarding initialization (participation/contract signed) and the remaining 25% upon the HIE connection being live or in production.

\n

\n

III.D.2 HIE Strategic Planning

\n

Having a robust HIE is a critical component of Tycho's HIT landscape and will continue to play a role in enhancing Tycho's EPs and EHs ability to achieve MU. As part of the Department’s responsibility for administration of the EHR Incentive Program and in an effort to enhance the maturity of HIE in Tycho, the Department is requesting funds to support a health information exchange assessment using CMS’ standards of the HIE Maturity Model and MITA and a Strategic Plan to enhance platform functionality and initial steps necessary to establish a long-term vision of HIE in Tycho's HIT landscape. This work will further ensure that the Department’s goals and target state (To-Be vision) aligns with CMS guidelines as specified under 42 CFR 495.338, as well as the HIE Maturity Model, MITA and the Seven Standards and Conditions.

\n

\n

The Department is requesting funds to support the statewide HIE in conducting an HIE Assessment using the CMS HIE Maturity Model and MITA standards. The information gathered in the assessment will help clearly articulate the long-term HIE vision for Tycho, define a governance model, and establish a robust sustainability plan built on the framework of the HIE Maturity Model and MITA standards. This information will also be used to identify areas where the statewide HIE can provide services and make connections with the Medicaid enterprise of systems to support health information exchange requirements and sustainability of the HIE.

\n

\n

III.D.3 Integration of Social Determinants of Health

\n

To further drive Tycho's goals around improved health outcomes through HIE, the Department is seeking funds to support the integration of the Social Determinants of Health into the statewide HIE system which will improve coordination of care and information exchange across the state.

\n

\n

This is an important and practical step to help the healthcare delivery system build effective, coordinated, data-driven healthcare services into communities hit hardest by social structures and economic systems. The integration of social determinants of health data will provide support for addressing social determinants of health drivers in Tycho and will identify ways to improve intervention using Social Determinants of Health as part of a comprehensive coordinated care model impacting payment, incentivizing purposeful intervention in the specific needs of their patients and populations to improve health outcomes.

\n

\n

To complete the scope of work, the HIE will integrate a limited CDR and interface to the network as well as provide onboarding services to connect Medicaid providers. The integration of the Social Determinates of Health project will support Medicaid providers ability to achieve meaningful use by allowing providers to incorporate summary of care information from other providers into their EHR using the functions of CEHRT through the HIE.

\n

\n

III.D.4 Staff Augmentation for Adoption and Utilization

\n

DHSS seeks to support onboarding efforts to connect Medicaid Meaningful Use eligible providers and providers supporting eligible providers to the HIE. The provider onboarding program will fund staffing outreach/educational support and technical services to Medicaid EPs that have adopted EHRs but not made HIE use part of day to day operations, not made use of new HIE capabilities, not yet connected, or were unable to take advantage of the ONC Regional Extension Center (REC) services because they were not eligible.

\n

Onboarding will include efforts to provide outreach/educational support and technical services. The Provider Onboarding Program includes the following objectives:

\n\n

The funds requested in this IAPD-U will be used to establish provider groups for onboarding support, establish onboarding benchmarks, and specifically implement training and technical assistance services. Funds will be used to assess barriers to onboarding and adoption of the HIE services, strategies for work flow analysis, and other ways to reduce Medicaid provider burden to onboard to the HIE. The proposed solution shall provide support services that coordinate with HIE processes to onboard and improve participant interoperability (e.g., clinic readiness assessments, bi-directional connection builds development and deployment of bi-directional interface with Medicaid) through utilization of the HIE system.

\n

\n

The adoption and utilization program will continue to expand outreach efforts and technical services to Medicaid providers and continue to boost MU numbers and milestones in Tycho to enhance the HIT vision outlined in the SMHP. In addition to AIU and MU education and technical services, the program will also seek to assist providers in meeting MU Stages 2 and 3 through onboarding provider interfaces and providing the capabilities to automatically meet several MU measures through the enhanced functionality of the HIE.

\n

\n

III.D.5 Trauma Registry

\n

DHSS recognizes the need for a trauma registry as an essential component of information exchange. The trauma registry is necessary to drive an efficient and effective performance improvement program for the care of injured enrollees. Furthermore, as published recently by SAMHSA, there are a range of evidence-based treatments that are effective in helping children and youth who have experienced trauma. Through the HIE, health providers will share and gain access to trauma information to drive an efficient and effective performance improvement program for the care of injured enrollees. The trauma register information will interoperate with the Behavioral Health Unified Landing Page Application to promote evidence-based treatments that are effective in helping enrollees who have experienced trauma. The trauma registry will be recognized as a specialized registry by the State to support MU and data exchange.

\n

\n

III.D.6 Air Medical Resource Location

\n

Tycho is currently struggling with tracking and maintaining the location and availability of air medical resources within the state. This information is critical to the timely delivery of care given the remote nature of Tycho's geography and unique dependence on air transportation. Currently, Tycho's air medical resources are using out of state dispatch centers who do not clearly understand the geography of Tycho or time needed to travel within the state. To address this gap in services and mitigate potential life-threatening delays in air medical resources, the Department would like to request funds to support the integration of the LifeMed application into the HIE. This application will allow healthcare entities: Public Health, hospitals, primary care providers, EMS, and all other authorized provider types to track all air medical resources in the state. The LifeMed application allows for tracking of specific tail numbers on planes and locations/timing for air resources.

\n

\n

The HIE will integrate with the LifeMed application so that Tycho providers and healthcare entities are able to seamlessly track all air medical resources in the state, thus greatly improve coordination and transition of care. The ability to track this information through the HIE will further support providers ability to enhance care coordination by accurately tracking patient location and improves health information exchange by giving providers access to information on patient’s location to submit summary of care records through the HIE to other provider EHR systems. Funds will be used to support the LifeMed software costs, provider training and implementation services.

\n

\n

III.D.7 AURORA-HIE Integration

\n

AURORA is a Public Health online patient care reporting system for EMS developed by Image Trend. The Department is requesting funds to support the connection of the AURORA system to the HIE. This activity would activate the HIE integration with the Image Trend solution to allow for Medicaid providers to send patient information to the AURORA system through the HIE. Upon delivery of the patient to the hospital the patient’s health data from EMS would be transmitted via the HIE to the hospital’s EHR system, and when the patient is discharge the ADT feed from the hospital would be transmitted back to EMS to the AURORA system.

\n

DHSS is seeking funds to integrate the AURORA Public Health online patient care reporting system for EMS to the HIE to help support Medicaid providers ability to achieve Meaningful Use by meeting objectives and measures pertaining to Health Information Exchange, Coordination of Care, and Public Health Reporting. Funds will be used to develop interfaces between the HIE and 10 hospitals and provider training and technical onboarding assistance to providers to connect to the HIE and AURORA system.

\n", - expenses: [ - { - description: '', - category: 'Hardware, software, and licensing', - years: { '2020': 0, '2021': 0 } - } - ], - fundingSource: 'HIE', - objectives: [ - { - objective: 'Plan to do a thing.', - keyResults: [ - { - baseline: '', - keyResult: 'Do a thing.', - target: '' - } - ] - }, - { - objective: 'Onboard 100 providers.', - keyResults: [ - { - baseline: '7 providers onboarded', - keyResult: '100 providers onboarded.', - target: '100 providers onboarded' - } - ] - } - ], - name: 'HIE Enhancement and Onboarding', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2021-09-30', - milestone: 'Onboard providers to assistance program' - }, - { - endDate: '2020-12-31', - milestone: 'Development of Roadmap' - }, - { - endDate: '2020-01-01', - milestone: 'HIE Staff Augmentation' - }, - { - endDate: '2020-01-01', - milestone: 'Modules for Care Coordination' - }, - { - endDate: '2021-09-30', - milestone: 'Provider Onboarding' - }, - { - endDate: '2020-01-01', - milestone: 'EDIE System Implementation' - }, - { - endDate: '2020-12-31', - milestone: 'Develop myAlaska HIE Authentication Requirements' - }, - { - endDate: '2020-03-31', - milestone: - 'Completion of requirements gathering to prepare to receive ELR' - }, - { - endDate: '2020-12-31', - milestone: - 'Configuration of internal BizTalk HL7 processes to translate the HL7 messages to PRISM' - }, - { - endDate: '2020-09-30', - milestone: 'Onboard Lab Providers' - }, - { - endDate: '2018-12-31', - milestone: - 'Establishment of program requirements and outreach strategy' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' + useHourly: false + }, + name: 'TBD', + start: '', + totalCost: 7398, + years: { '2020': 0, '2021': 1000000 } + } + ], + costAllocation: { + '2020': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + }, + '2021': { + ffp: { + federal: 75, + state: 25 + }, + other: 0 + } + }, + costAllocationNarrative: { + methodology: '

No cost allocation is necessary for this activity.

\n', + '2020': { + otherSources: '

No other funding is provided for this activity for FFY 2020.

\n' + }, + '2021': { + otherSources: '

No other funding is provided for this activity for FFY 2021.

\n' + } + }, + description: + "

III.B.3 Medicaid Claims Data Feed to the HIE

\n

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n", + expenses: [ + { + description: '', + category: 'Travel', + years: { '2020': 0, '2021': 0 } + } + ], + fundingSource: 'MMIS', + objectives: [ + { + objective: + 'Build interface between the MMIS Data Warehouse (DW) and the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE.', + keyResults: [ + { + baseline: 'no contractor', + keyResult: + 'Hire contracted support to build an open API for the DW that the HIE and PHR can consume.', + target: 'yes contractor' }, - statePersonnel: [ - { - title: - 'Services Integration Architect/ Programmer (Analyst Programmer V)', - description: - 'Lead technical architecture design and development efforts for designing, implementing and maintaining services integrations leveraging resources such as the MCI, MPI and state HIE along with other DHSS Business Systems.', - years: { - '2020': { amt: 115000, perc: 4 }, - '2021': { amt: 119000, perc: 4 } - } - } - ], - summary: 'Statewide HIE enhancement and onboarding.', - quarterlyFFP: { - '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - }, - '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - } + { + baseline: 'no support', + keyResult: 'Provide support for using open API for DW', + target: 'yes support' } - }, - { - alternatives: - '

Medicaid PHR/Blue Button

\n

Integrate MMIS DW into the HIE with Blue Button download

\n

Allows Medicaid recipients to view their Medicaid claims information in a portal and access it through a Blue Button download

\n

Assists providers in achieving MU by helping them meet the VDT requirements

\n

Supports the MU CQMs including EP Core Measure:Electronic Copy of health information

\n

Alaskans will be able to access their PHRs

\n

User friendly, easy to use technology helps ensure access

\n

There are no significant negatives to this approach

\n

Implement Medicaid PHR/Blue Button

\n', - contractorResources: [ - { - description: '', - end: '', - hourly: { - data: { - '2020': { hours: '', rate: '' }, - '2021': { hours: '', rate: '' } - }, - useHourly: false - }, - name: 'RFP Planning Vendor Inc.', - start: '', - totalCost: 4368734, - years: { '2020': 500000, '2021': 0 } - }, - { - description: '', - end: '', - hourly: { - data: { - '2020': { hours: '', rate: '' }, - '2021': { hours: '', rate: '' } - }, - useHourly: false - }, - name: 'Blue Button Builder Inc.', - start: '', - totalCost: 35246, - years: { '2020': 0, '2021': 2000000 } - } - ], - costAllocation: { - '2020': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 - }, - '2021': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 - } + ] + } + ], + name: 'HIE Claims Data Analytics', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2018-12-31', + milestone: 'Implement MMIS-HIE Interface' + }, + { + endDate: '2018-12-31', + milestone: 'Develop MMIS-HIE Interface Requirements' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: 'Project Assistant', + description: 'Assist with stuff', + years: { + '2020': { amt: 98000, perc: 1 }, + '2021': { amt: 99000, perc: 1 } + } + }, + { + title: 'MMIS Project Manager', + description: + 'This position is responsible for the program development, planning, coordination, evaluation, independent management and oversight of the Tycho Automated Info', + years: { + '2020': { amt: 140000, perc: 1 }, + '2021': { amt: 144000, perc: 1 } + } + }, + { + title: 'MMIS Trainer', + description: + 'Under the direct supervision of the Project Manager, this position is responsible for the development of a comprehensive training and support program for the Tycho Automated Information Management System', + years: { + '2020': { amt: 115000, perc: 1 }, + '2021': { amt: 115000, perc: 1 } + } + }, + { + title: 'Programmer IV', + description: + 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', + years: { + '2020': { amt: 140000, perc: 1 }, + '2021': { amt: 145000, perc: 1 } + } + }, + { + title: 'Security IT', + description: 'Make sure its secure.', + years: { + '2020': { amt: 115000, perc: 1 }, + '2021': { amt: 120000, perc: 1 } + } + }, + { + title: 'Operations Specialist', + description: 'Run the day to day.', + years: { + '2020': { amt: 125000, perc: 1 }, + '2021': { amt: 130000, perc: 1 } + } + }, + { + title: 'Programmer V', + description: + 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', + years: { + '2020': { amt: 150000, perc: 2 }, + '2021': { amt: 155000, perc: 3 } + } + }, + { + title: 'Programmer III', + description: + 'The main purpose of this position is to develop and support Web and Client/Server applications. Duties include analysis, design, testing, debugging, documenting and supporting new and existing systems', + years: { + '2020': { amt: 120000, perc: 1 }, + '2021': { amt: 125000, perc: 1 } + } + } + ], + summary: + 'To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. ', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + }, + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } + } + }, + { + alternatives: + '

Health Information Exchange

\n

Maintain existing system.

\n

The existing system has a few benefits. The current EDI process while dated still forms the backbone of the Division’s data sharing needs. The technology works in the fashion that it always has.

\n

The drawbacks of this approach are significant. While the current Edi process affords behavioral health agencies to submit their data to the state, it does not allow for sharing the same data to other providers in either the primary care or behavioral health treatment contexts.

\n

There are more disadvantages than advantages in pursuing this approach. The drawbacks are substantial, such as absence of data normalization, difficulties with aligning the user interface and application design with industry best practices, inconsistencies in design, and difficulties with support and maintenance, making this approach less favorable than the other two alternatives considered.

\n

Health Information Exchange

\n

Update and Enhance Existing System(s), connecting AKAIMS to the Health Information Exchange

\n

Connecting AKAIMS to the Health Information Exchange will provide for the sending and receiving of data across healthcare disciplines. This data sharing is thought to enhance and provide for better care outcomes for patients who are participating in care across multiple providers. This solution future proofs AKAIMS as it will integrate current technologies and leverages those technologies for a more feature rich process.

\n

Training and integration of this updated technology will require some effort and outreach. Newly on-boarded agencies will need to adjust to new data collection protocols.

\n

Full participation in the Health Information Exchange will reduce double data entry at all levels (reducing costs). It is anticipated that efficiencies gained with simplification of data collection and reporting will greatly enhance patient care outcomes.

\n

HIE Platform

\n

Upgrade HIE to the Audacious Inquiry (Ai) platform

\n

Ai offers a strong foundation on which additional functionality can be built. Transitioning to the Ai platform has the potential to minimize the effort required to modernize the HIE, while delivering additional services to users.

\n

Transitioning to Ai means that the State will be leaving the current HIE platform. There is potential risk in adoption and migration of services and data.

\n

The HIE platform will be transitioned to Ai to offer additional services, contain costs on enhancements, and maximize the scalability and flexibility of the HIE to support modernization across the enterprise.

\n

HIE Platform

\n

Keep platform as it is without upgrade.

\n

Keeping the platform as it is without upgrade would allow focus to remain on onboarding.

\n

Functionality supported by existing HIE is not adequate to support future applications. The value delivered by the service as it is could be improved with additional functionality. Potential to ingest different critical types of data is limited without a platform upgrade.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

\n

HIE Platform

\n

Partner with another state HIE for services ranging from sharing the platform itself, to specific services or commonly-developed interfaces.

\n

Sharing with another state offers the potential to

\n

• decrease costs

\n

• Increase speed of onboarding

\n

• Increase functionality

\n

• Provide for greater sustainability

\n

• Address the needs of our partners faster or better

\n

No states currently share HIE services entirely, due to perceived legal constraints; this option presents multiple factors to consider ranging from legal to technical. Potential for cost savings is limited because pricing models are usually based on volume. There is a possibility for significant disruption to service during a transition of this type; significant issues with legal arrangements complying with other states.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

HIE Tools for Care Coordination

\n

Add functional tools to support care coordination, referrals and analytics through other module developers or collaborators

\n

Sharing with another state or regional HIE to develop or utilize HIE tools offers the potential to

\n

• decrease costs

\n

• Increase speed of onboarding

\n

• Increase functionality

\n

• Provide for greater sustainability

\n

• Address the needs of our partners faster or better

\n

If another commercial developer is selected to offer these modules, there is some likelihood that integrating into the HIE platform will be more difficult without the transition to Ai.

\n

Alternative solutions will leverage existing infrastructure where applicable; will not increase annual maintenance fees, and will follow DHSS purchasing policy.

\n

HIE Functionality

\n

Enhancing functionality for participating hospitals

\n

Hospitals are critical stakeholders in the HIE. Providing functionality to assist hospitals in meeting MU3 and in evaluating ER patients are two areas where HIE could provide valuable information.

\n

Hospital focus is based on patient safety. Thus far, there has been little incentive for using HIE data for patient safety.

\n

DHSS is actively pursuing additional functionality for hospitals. This involves hospital stakeholder meetings, vendor discussions, board review and clinical workgroup input.

\n

\n

HIE Functionality

\n

Implement connections with high-value state and federal data sources (Corrections, DJJ, SSA, DoD)

\n

Including health data from correctional facilities (ADT, ORU and/or CCD files) will help provide better more coordinated care for this vulnerable population, many of whom are also Medicaid-eligible.

\n

Aside from the need to allocate staff time across projects, there are no significant drawbacks to this option.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding state and federal data source connections

\n

Less work for the HIE team, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules.

\n

Leaving the information gap among these agencies open will lead to continued delays in needed services.

\n

This option is not preferred.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding emergency department information exchange

\n

Giving providers better tools to coordinate care for high-risk, high-utilizer members of the population has the potential to substantially reduce spending and improve outcomes for this vulnerable population.

\n

Aside from the need to allocate staff time across projects, there are no significant drawbacks to this option.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding prescription information

\n

Less work for the HIE, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules

\n

A continuing information gap around prescriptions filled will limit the potential to improve care coordination for Tycho citizens and heighten patient safety.

\n

This project should proceed.

\n

HIE Functionality

\n

Keep health information exchange functionality substantially the same regarding image exchange

\n

Less work for the HIE, DHSS and other teams to accomplish, allowing for greater focus on onboarding providers and implementing new technology modules

\n

The lack of simple diagnostic image exchange presents a significant barrier to widespread health information exchange. Without these technologies, patients often hand-carry their films or electronic files with them, which can present a high risk of lost images and inefficiency.

\n

This option is not preferred at this time.

\n', + contractorResources: [ + { + description: '', + end: '', + hourly: { + data: { + '2020': { hours: '', rate: '' }, + '2021': { hours: '', rate: '' } }, - costAllocationNarrative: { - methodology: '', - otherSources: '' + useHourly: false + }, + + name: '', + start: '', + totalCost: 3496874, + years: { '2020': 0, '2021': 0 } + } + ], + costAllocation: { + '2020': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + }, + '2021': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + } + }, + costAllocationNarrative: { + methodology: '', + '2020': { + otherSources: '' + }, + '2021': { + otherSources: '' + } + }, + description: + "

\n\"undefined\"\n

\n

\n

III.D. Statewide HIE Enhancement, Onboarding, and Support of Statewide HIE Operational Strategic Plan

\n

DHSS is requesting funding to support the continued enhancement and provider onboarding activities to the statewide HIE. The success of the statewide HIE is critical for improving data exchange, coordination of care, and modernizing healthcare across Tycho. The following funding requests are for projects that will provide enhanced technical capabilities to providers, support providers in onboarding, support modernizations required for Medicaid redesign, and ensure sustainability beyond State of Tycho and CMS funding. The projects have been designed to meet the following goals and desires for the statewide HIE:

\n\n

III.D.1 Behavioral Health Onboarding & Care Coordination

\n

The Department recognizes the need to increase Behavioral Health (BH) data capacity and sharing to achieve its goals and objectives related to care coordination. This includes promoting effective communication to coordinate care and enhancing the ability for providers to share and gain access to Protected Class Patient Data where appropriate. To support the capacity of data sharing and improving coordination of care, funding is requested to support Behavioral Health provider connectivity through the onboarding program by the development and implementation of a Behavioral Health-centric Unified Landing Page Application. The Behavioral Health Unified Landing Page Application will improve the quality and completeness of behavioral health data and thus, support the ability for providers to achieve MU.

\n

\n

In addition to the Unified Landing Page, funding is requested to support behavioral health provider onboarding to the HIE. The HIE onboarding program will provide funds to offset expenses required for behavioral health providers to adequately participate in statewide health information exchange. The onboarding program will support Tycho's HIE vision of increasing onboarding Medicaid providers and care coordination to help Tycho providers demonstrate MU. This program relates to the guidance provided by CMS in the SMD 16-003 letter dated February 2016 and will assist with covering costs associated with connectivity including but not limited to the following activities:

\n\n

The goal is for the onboarding program to support 40 provider organizations across the State. The initial phase of the program will be focused on Medicaid behavioral health providers with additional provider types potentially targeted in later phases of the initiative. Administrative offset funding will be on-time funding only and will be issued as pass-through funding through healtheConnect (Tycho's HIE organization). The funding will be distributed in 2 parts: 75% upon onboarding initialization (participation/contract signed) and the remaining 25% upon the HIE connection being live or in production.

\n

\n

III.D.2 HIE Strategic Planning

\n

Having a robust HIE is a critical component of Tycho's HIT landscape and will continue to play a role in enhancing Tycho's EPs and EHs ability to achieve MU. As part of the Department’s responsibility for administration of the EHR Incentive Program and in an effort to enhance the maturity of HIE in Tycho, the Department is requesting funds to support a health information exchange assessment using CMS’ standards of the HIE Maturity Model and MITA and a Strategic Plan to enhance platform functionality and initial steps necessary to establish a long-term vision of HIE in Tycho's HIT landscape. This work will further ensure that the Department’s goals and target state (To-Be vision) aligns with CMS guidelines as specified under 42 CFR 495.338, as well as the HIE Maturity Model, MITA and the Seven Standards and Conditions.

\n

\n

The Department is requesting funds to support the statewide HIE in conducting an HIE Assessment using the CMS HIE Maturity Model and MITA standards. The information gathered in the assessment will help clearly articulate the long-term HIE vision for Tycho, define a governance model, and establish a robust sustainability plan built on the framework of the HIE Maturity Model and MITA standards. This information will also be used to identify areas where the statewide HIE can provide services and make connections with the Medicaid enterprise of systems to support health information exchange requirements and sustainability of the HIE.

\n

\n

III.D.3 Integration of Social Determinants of Health

\n

To further drive Tycho's goals around improved health outcomes through HIE, the Department is seeking funds to support the integration of the Social Determinants of Health into the statewide HIE system which will improve coordination of care and information exchange across the state.

\n

\n

This is an important and practical step to help the healthcare delivery system build effective, coordinated, data-driven healthcare services into communities hit hardest by social structures and economic systems. The integration of social determinants of health data will provide support for addressing social determinants of health drivers in Tycho and will identify ways to improve intervention using Social Determinants of Health as part of a comprehensive coordinated care model impacting payment, incentivizing purposeful intervention in the specific needs of their patients and populations to improve health outcomes.

\n

\n

To complete the scope of work, the HIE will integrate a limited CDR and interface to the network as well as provide onboarding services to connect Medicaid providers. The integration of the Social Determinates of Health project will support Medicaid providers ability to achieve meaningful use by allowing providers to incorporate summary of care information from other providers into their EHR using the functions of CEHRT through the HIE.

\n

\n

III.D.4 Staff Augmentation for Adoption and Utilization

\n

DHSS seeks to support onboarding efforts to connect Medicaid Meaningful Use eligible providers and providers supporting eligible providers to the HIE. The provider onboarding program will fund staffing outreach/educational support and technical services to Medicaid EPs that have adopted EHRs but not made HIE use part of day to day operations, not made use of new HIE capabilities, not yet connected, or were unable to take advantage of the ONC Regional Extension Center (REC) services because they were not eligible.

\n

Onboarding will include efforts to provide outreach/educational support and technical services. The Provider Onboarding Program includes the following objectives:

\n\n

The funds requested in this IAPD-U will be used to establish provider groups for onboarding support, establish onboarding benchmarks, and specifically implement training and technical assistance services. Funds will be used to assess barriers to onboarding and adoption of the HIE services, strategies for work flow analysis, and other ways to reduce Medicaid provider burden to onboard to the HIE. The proposed solution shall provide support services that coordinate with HIE processes to onboard and improve participant interoperability (e.g., clinic readiness assessments, bi-directional connection builds development and deployment of bi-directional interface with Medicaid) through utilization of the HIE system.

\n

\n

The adoption and utilization program will continue to expand outreach efforts and technical services to Medicaid providers and continue to boost MU numbers and milestones in Tycho to enhance the HIT vision outlined in the SMHP. In addition to AIU and MU education and technical services, the program will also seek to assist providers in meeting MU Stages 2 and 3 through onboarding provider interfaces and providing the capabilities to automatically meet several MU measures through the enhanced functionality of the HIE.

\n

\n

III.D.5 Trauma Registry

\n

DHSS recognizes the need for a trauma registry as an essential component of information exchange. The trauma registry is necessary to drive an efficient and effective performance improvement program for the care of injured enrollees. Furthermore, as published recently by SAMHSA, there are a range of evidence-based treatments that are effective in helping children and youth who have experienced trauma. Through the HIE, health providers will share and gain access to trauma information to drive an efficient and effective performance improvement program for the care of injured enrollees. The trauma register information will interoperate with the Behavioral Health Unified Landing Page Application to promote evidence-based treatments that are effective in helping enrollees who have experienced trauma. The trauma registry will be recognized as a specialized registry by the State to support MU and data exchange.

\n

\n

III.D.6 Air Medical Resource Location

\n

Tycho is currently struggling with tracking and maintaining the location and availability of air medical resources within the state. This information is critical to the timely delivery of care given the remote nature of Tycho's geography and unique dependence on air transportation. Currently, Tycho's air medical resources are using out of state dispatch centers who do not clearly understand the geography of Tycho or time needed to travel within the state. To address this gap in services and mitigate potential life-threatening delays in air medical resources, the Department would like to request funds to support the integration of the LifeMed application into the HIE. This application will allow healthcare entities: Public Health, hospitals, primary care providers, EMS, and all other authorized provider types to track all air medical resources in the state. The LifeMed application allows for tracking of specific tail numbers on planes and locations/timing for air resources.

\n

\n

The HIE will integrate with the LifeMed application so that Tycho providers and healthcare entities are able to seamlessly track all air medical resources in the state, thus greatly improve coordination and transition of care. The ability to track this information through the HIE will further support providers ability to enhance care coordination by accurately tracking patient location and improves health information exchange by giving providers access to information on patient’s location to submit summary of care records through the HIE to other provider EHR systems. Funds will be used to support the LifeMed software costs, provider training and implementation services.

\n

\n

III.D.7 AURORA-HIE Integration

\n

AURORA is a Public Health online patient care reporting system for EMS developed by Image Trend. The Department is requesting funds to support the connection of the AURORA system to the HIE. This activity would activate the HIE integration with the Image Trend solution to allow for Medicaid providers to send patient information to the AURORA system through the HIE. Upon delivery of the patient to the hospital the patient’s health data from EMS would be transmitted via the HIE to the hospital’s EHR system, and when the patient is discharge the ADT feed from the hospital would be transmitted back to EMS to the AURORA system.

\n

DHSS is seeking funds to integrate the AURORA Public Health online patient care reporting system for EMS to the HIE to help support Medicaid providers ability to achieve Meaningful Use by meeting objectives and measures pertaining to Health Information Exchange, Coordination of Care, and Public Health Reporting. Funds will be used to develop interfaces between the HIE and 10 hospitals and provider training and technical onboarding assistance to providers to connect to the HIE and AURORA system.

\n", + expenses: [ + { + description: '', + category: 'Hardware, software, and licensing', + years: { '2020': 0, '2021': 0 } + } + ], + fundingSource: 'HIE', + objectives: [ + { + objective: 'Plan to do a thing.', + keyResults: [ + { + baseline: '', + keyResult: 'Do a thing.', + target: '' + } + ] + }, + { + objective: 'Onboard 100 providers.', + keyResults: [ + { + baseline: '7 providers onboarded', + keyResult: '100 providers onboarded.', + target: '100 providers onboarded' + } + ] + } + ], + name: 'HIE Enhancement and Onboarding', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2021-09-30', + milestone: 'Onboard providers to assistance program' + }, + { + endDate: '2020-12-31', + milestone: 'Development of Roadmap' + }, + { + endDate: '2020-01-01', + milestone: 'HIE Staff Augmentation' + }, + { + endDate: '2020-01-01', + milestone: 'Modules for Care Coordination' + }, + { + endDate: '2021-09-30', + milestone: 'Provider Onboarding' + }, + { + endDate: '2020-01-01', + milestone: 'EDIE System Implementation' + }, + { + endDate: '2020-12-31', + milestone: 'Develop myAlaska HIE Authentication Requirements' + }, + { + endDate: '2020-03-31', + milestone: + 'Completion of requirements gathering to prepare to receive ELR' + }, + { + endDate: '2020-12-31', + milestone: + 'Configuration of internal BizTalk HL7 processes to translate the HL7 messages to PRISM' + }, + { + endDate: '2020-09-30', + milestone: 'Onboard Lab Providers' + }, + { + endDate: '2018-12-31', + milestone: + 'Establishment of program requirements and outreach strategy' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: + 'Services Integration Architect/ Programmer (Analyst Programmer V)', + description: + 'Lead technical architecture design and development efforts for designing, implementing and maintaining services integrations leveraging resources such as the MCI, MPI and state HIE along with other DHSS Business Systems.', + years: { + '2020': { amt: 115000, perc: 4 }, + '2021': { amt: 119000, perc: 4 } + } + } + ], + summary: 'Statewide HIE enhancement and onboarding.', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + }, + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } + } + }, + { + alternatives: + '

Medicaid PHR/Blue Button

\n

Integrate MMIS DW into the HIE with Blue Button download

\n

Allows Medicaid recipients to view their Medicaid claims information in a portal and access it through a Blue Button download

\n

Assists providers in achieving MU by helping them meet the VDT requirements

\n

Supports the MU CQMs including EP Core Measure:Electronic Copy of health information

\n

Alaskans will be able to access their PHRs

\n

User friendly, easy to use technology helps ensure access

\n

There are no significant negatives to this approach

\n

Implement Medicaid PHR/Blue Button

\n', + contractorResources: [ + { + description: '', + end: '', + hourly: { + data: { + '2020': { hours: '', rate: '' }, + '2021': { hours: '', rate: '' } }, - description: - '

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

\n

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

\n

\n

The PHR will not collect CQMs or interface to public health registries. However, it will provide short and long-term value to providers by assisting them in achieving MU.

\n

Alaska plans to integrate the MMIS DW into the HIE, allowing Medicaid recipients to view their Medicaid claims information in a portal and access it through a Blue Button (or similar) download. Additionally, this initiative will benefit providers by assisting them in achieving MU by helping them meet View, Download, and Transmit (VDT) requirements.

\n

\n

This Medicaid PHR/Blue Button (or similar) approach allows providers to meet VDT requirements without having to create individual patient portals. This supports providers in achieving MU. Medicaid Eligible population will benefit by being able to obtain their Medicaid claim information, along with access to their PHRs. See further cost allocation details in Section VIII and Appendix D.

\n', - expenses: [ - { - description: '', - category: 'Hardware, software, and licensing', - years: { '2020': 0, '2021': 0 } - } - ], - fundingSource: 'HIE', - objectives: [ - { - objective: 'Build blue button.', - keyResults: [ - { - baseline: '0 providers', - keyResult: 'Test blue button with 10 providers.', - target: '10 providers' - } - ] - } - ], - name: 'Medicaid Blue Button', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2020-04-01', - milestone: 'PHR/Blue Button HIE Build' - }, - { - endDate: '2018-12-31', - milestone: 'Blue Button Implementation' - }, - { - endDate: '2018-12-31', - milestone: 'On-Boarding of PHR/Blue Button Participants' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' + useHourly: false + }, + name: 'RFP Planning Vendor Inc.', + start: '', + totalCost: 4368734, + years: { '2020': 500000, '2021': 0 } + }, + { + description: '', + end: '', + hourly: { + data: { + '2020': { hours: '', rate: '' }, + '2021': { hours: '', rate: '' } }, - statePersonnel: [ - { - title: '', - description: '', - years: { - '2020': { amt: 0, perc: 0 }, - '2021': { amt: 0, perc: 0 } - } - } - ], - summary: - 'DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE.', - quarterlyFFP: { - '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - }, - '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - } - } + useHourly: false }, - { - alternatives: - '

HIE Functionality

\n

Update and enhance existing system, adding interfaces with PDMP, PRISM, and Special registries via Public Health Modernization

\n

Connecting these systems to the health information exchange would improve efficiencies for providers and for public health registrars. Reporting to several of these registries is an essential component of meaningful use for EPs and EHs; integrating this function into the HIE helps to reinforce value for the HIE, and will have the benefit of easing reporting.

\n

Expanding the utility of the Health Information Exchange will reduce double data entry at all levels (reducing costs) and simplify reporting for participating EPs and EHs.

\n

Training and integration of this updated technology will require some effort and outreach. Newly on-boarded agencies will need to adjust to new data collection protocols, and currently connected providers will need outreach to help them understand the new functionality.

\n

It is anticipated that efficiencies gained with simplification of data collection and reporting will greatly enhance patient care outcomes, and will assist EPs and EHs in attesting to meaningful use.

\n', - contractorResources: [ - { - description: 'Gateway Implementation.', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - name: 'TBD', - start: '', - totalCost: 246477, - years: { '2020': 0, '2021': 1500000 } - }, - { - description: 'Gateway Development Planning and RFP', - end: '', - hourly: { - data: { - '2020': { - hours: '', - rate: '' - }, - '2021': { - hours: '', - rate: '' - } - }, - useHourly: false - }, - name: 'Gateway Vendor Inc.', - start: '', - totalCost: 7473747, - years: { '2020': 500000, '2021': 0 } - } - ], - costAllocation: { + name: 'Blue Button Builder Inc.', + start: '', + totalCost: 35246, + years: { '2020': 0, '2021': 2000000 } + } + ], + costAllocation: { + '2020': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + }, + '2021': { + ffp: { + federal: 90, + state: 10 + }, + other: 0 + } + }, + costAllocationNarrative: { + methodology: '', + '2020': { + otherSources: '' + }, + '2021': { + otherSources: '' + } + }, + description: + '

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

\n

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

\n

\n

The PHR will not collect CQMs or interface to public health registries. However, it will provide short and long-term value to providers by assisting them in achieving MU.

\n

Alaska plans to integrate the MMIS DW into the HIE, allowing Medicaid recipients to view their Medicaid claims information in a portal and access it through a Blue Button (or similar) download. Additionally, this initiative will benefit providers by assisting them in achieving MU by helping them meet View, Download, and Transmit (VDT) requirements.

\n

\n

This Medicaid PHR/Blue Button (or similar) approach allows providers to meet VDT requirements without having to create individual patient portals. This supports providers in achieving MU. Medicaid Eligible population will benefit by being able to obtain their Medicaid claim information, along with access to their PHRs. See further cost allocation details in Section VIII and Appendix D.

\n', + expenses: [ + { + description: '', + category: 'Hardware, software, and licensing', + years: { '2020': 0, '2021': 0 } + } + ], + fundingSource: 'HIE', + objectives: [ + { + objective: 'Build blue button.', + keyResults: [ + { + baseline: '0 providers', + keyResult: 'Test blue button with 10 providers.', + target: '10 providers' + } + ] + } + ], + name: 'Medicaid Blue Button', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2020-04-01', + milestone: 'PHR/Blue Button HIE Build' + }, + { + endDate: '2018-12-31', + milestone: 'Blue Button Implementation' + }, + { + endDate: '2018-12-31', + milestone: 'On-Boarding of PHR/Blue Button Participants' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: '', + description: '', + years: { + '2020': { amt: 0, perc: 0 }, + '2021': { amt: 0, perc: 0 } + } + } + ], + summary: + 'DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE.', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + }, + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } + } + }, + { + alternatives: + '

HIE Functionality

\n

Update and enhance existing system, adding interfaces with PDMP, PRISM, and Special registries via Public Health Modernization

\n

Connecting these systems to the health information exchange would improve efficiencies for providers and for public health registrars. Reporting to several of these registries is an essential component of meaningful use for EPs and EHs; integrating this function into the HIE helps to reinforce value for the HIE, and will have the benefit of easing reporting.

\n

Expanding the utility of the Health Information Exchange will reduce double data entry at all levels (reducing costs) and simplify reporting for participating EPs and EHs.

\n

Training and integration of this updated technology will require some effort and outreach. Newly on-boarded agencies will need to adjust to new data collection protocols, and currently connected providers will need outreach to help them understand the new functionality.

\n

It is anticipated that efficiencies gained with simplification of data collection and reporting will greatly enhance patient care outcomes, and will assist EPs and EHs in attesting to meaningful use.

\n', + contractorResources: [ + { + description: 'Gateway Implementation.', + end: '', + hourly: { + data: { '2020': { - ffp: { federal: 90, state: 10 }, - other: 0 + hours: '', + rate: '' }, '2021': { - ffp: { federal: 90, state: 10 }, - other: 0 + hours: '', + rate: '' } }, - costAllocationNarrative: { - methodology: '', - otherSources: '' - }, - description: - "

\n

III.C.2 Public Health System Modernization

\n

In order to support meaningful use and provide specialized registries for EPs and EHs to have the ability to electronically report to the registries, Tycho is requesting funding to undergo a transformation and modernization of the current public health systems. The purpose of this modernization initiative is to provide Medicaid EPs and EHs with the tools to improve the coordination of care, transition of care and the availability of specialty registries; increasing the number of providers attesting for and meeting meaningful use requirements.

\n

\n

DHSS in partnership with the DPH has identified multiple public health systems and registries in which the current “as is” process is a manual process for reporting and data submission of public health data. Through this modernization initiative, over 15 public health systems have been defined as meeting the specifications as specialized registries. However, the submissions vary in format, transport and destination. Additionally, the registry data is housed in multiple databases that are used across the agency.

\n

The anticipated registries to be made available for electronic submission by providers include, but not limited to:

\n\n

The requested funding will provide a mechanism for the design, development and implementation of registry database will store registry data in a centralized location; improving security of the data, reliability, performance, integration of datasets, and the range of analytical methods available. Funding is requested for the implementation of Microsoft’s Dynamic CRM tool, which sits on top of SQL Server and provides the required functionality to provide robust reporting and programming methods. This modular approach will provide rapid integration of the Master Client Index (MCI) with registries, and can support the DHSS Enterprise Service Bus (ESB) which already supports integration with the statewide HIE.

\n

\n

The projected data flow, named the DHSS Gateway, is up at the top. @Bren bug fix!

\n

\n

Through the implementation of the modernization initiative, providers will have the ability to submit public health data to a single point of entry; the HIE. The HIE will then pass the received submissions through the DHSS Gateway data store, which will store and parse the data for the individual registries; offering a streamlined and efficient method of submission.

\n

\n

III.C.3 Case Management System Implementation

\n

The Department of Health and Social Services is requesting funding for the design, development, and implementation of a robust, modular care management solution to support the care and services provided to Tycho citizens. This solution will allow Department of Health and Social Services to be more efficient in treating Tycho citizenswe serve across multiple divisions and will allow the patient’s healthcare record to more easily follow their care in a secure, electronic manner. In turn, this will support coordination of care for patients receiving services by various entities. This solution will be designed and implanted through contracting within the statewide Health Information Exchange to take advantage of other service offerings provided by the statewide Health Information Exchange. The modular solution implemented will align with the Medicaid Information Technology Architecture 3.0 business processes to meet the requirements for the department. The department will utilize existing functionality or modules to meet the requirements wherever possible.

\n

\n

III.C.4 MCI Enhancement

\n

Tycho's Medicaid is requesting funding to support the continued design, development and implementation of modifications to the statewide MCI to improve activities for EPs and EHs trying to achieve meaningful use across the state of Tycho. Development of the MCI will provide short and long-term value to providers by reducing de-duplication of client data. An enhanced MCI will support creation of a unique client identifier for each individual. This will allow correlation of all known instances of client data and records for each client. The requested funding will support the cost of state personnel and resources to develop requirements and synchronize the Department’s MCI to the HIE Master Patient Index (eMPI) to provide a more robust demographic source of data for the HIE eMPI and provide new data or updated demographic information from the HIE to the Department’s MCI. This project is critical for improving coordination of care through the HIE.

\n", - expenses: [ - { - description: '', - category: 'Hardware, software, and licensing', - years: { '2020': 0, '2021': 0 } - } - ], - fundingSource: 'HIE', - objectives: [ - { - objective: 'Identifiy PH needs', - keyResults: [ - { - baseline: 'incomplete', - keyResult: - 'Complete a build/implementation plan by Summery 2020', - target: 'complete' - } - ] - }, - { - objective: 'Connect PH systems to HIE', - keyResults: [ - { - baseline: '0 systems connected', - keyResult: 'Connect all 3 PH systems to HIE by Fall 2020', - target: '3 systems connected' - } - ] - } - ], - name: 'Public Health System Modernization', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2017-03-31', - milestone: 'PH Completion of requirements gathering' - }, - { - endDate: '2021-09-30', - milestone: 'PH Development and implementation of CRM Tool' - }, - { - endDate: '2021-09-30', - milestone: 'PH Connection of Public Health systems to HIE' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' - }, - statePersonnel: [ - { - title: '', - description: '', - years: { - '2020': { amt: 0, perc: 0 }, - '2021': { amt: 0, perc: 0 } - } - } - ], - summary: - 'The purpose of PH modernization is to provide Medicaid EPs and EHs with the tools to improve the coordination of care, transition of care and the availability of specialty registries; increasing the number of providers attesting for meaningful use.', - quarterlyFFP: { - '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - }, - '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - } - } + useHourly: false }, - { - alternatives: - '

Must do MITA 3.0 because MITA is awesome and gives Tycho a standardized view of their Medicaid IT maturity. 

\n', - contractorResources: [ - { - description: - 'Research for and RFP development for MITA 3.0 SSA', - end: '', - hourly: { - data: { - '2020': { hours: '', rate: '' }, - '2021': { hours: '', rate: '' } - }, - useHourly: false - }, - name: 'Tech Consulting Inc.', - start: '', - totalCost: 264574, - years: { '2020': 450000, '2021': 150000 } - }, - { - description: 'MITA 3.0 implementation.', - end: '', - hourly: { - data: { - '2020': { hours: '', rate: '' }, - '2021': { hours: '', rate: '' } - }, - useHourly: false - }, - name: 'TBD', - start: '', - totalCost: 64574, - years: { '2020': 200000, '2021': 500000 } - } - ], - costAllocation: { + name: 'TBD', + start: '', + totalCost: 246477, + years: { '2020': 0, '2021': 1500000 } + }, + { + description: 'Gateway Development Planning and RFP', + end: '', + hourly: { + data: { '2020': { - ffp: { - federal: 50, - state: 50 - }, - other: 0 + hours: '', + rate: '' }, '2021': { - ffp: { - federal: 90, - state: 10 - }, - other: 0 - } - }, - costAllocationNarrative: { - methodology: '', - otherSources: '' - }, - description: - '

III.B.4 HITECH MITA 3.0 Development and Implementation

\n

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

\n', - expenses: [ - { - description: '', - category: 'Equipment and supplies', - years: { '2020': 25000, '2021': 25000 } + hours: '', + rate: '' } - ], - fundingSource: 'HIT', - objectives: [ - { - objective: 'Complete MITA 3.0 HITECH portion.', - keyResults: [ - { - baseline: '', - keyResult: - 'Complete MITA 3.0 HITECH portion by July 2020', - target: '' - } - ] - } - ], - name: 'MITA 3.0 Assessment', - plannedEndDate: '', - plannedStartDate: '', - schedule: [ - { - endDate: '2020-02-28', - milestone: 'MITA 3.0 SS-A Project' - }, - { - endDate: '2020-12-31', - milestone: 'HITECH SS-A Assessment' - } - ], - standardsAndConditions: { - doesNotSupport: '', - supports: '' }, - statePersonnel: [ - { - title: 'State MITA Person', - description: '1', - years: { - '2020': { amt: 100000, perc: 0.5 }, - '2021': { amt: 100000, perc: 1 } - } - } - ], - summary: - 'DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A.', - quarterlyFFP: { - '2020': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - }, - '2021': { - '1': { combined: 25, contractors: 25, inHouse: 25 }, - '2': { combined: 25, contractors: 25, inHouse: 25 }, - '3': { combined: 25, contractors: 25, inHouse: 25 }, - '4': { combined: 25, contractors: 25, inHouse: 25 } - } + useHourly: false + }, + name: 'Gateway Vendor Inc.', + start: '', + totalCost: 7473747, + years: { '2020': 500000, '2021': 0 } + } + ], + costAllocation: { + '2020': { + ffp: { federal: 90, state: 10 }, + other: 0 + }, + '2021': { + ffp: { federal: 90, state: 10 }, + other: 0 + } + }, + costAllocationNarrative: { + methodology: '', + '2020': { + otherSources: '' + }, + '2021': { + otherSources: '' + } + }, + description: + "

\n

III.C.2 Public Health System Modernization

\n

In order to support meaningful use and provide specialized registries for EPs and EHs to have the ability to electronically report to the registries, Tycho is requesting funding to undergo a transformation and modernization of the current public health systems. The purpose of this modernization initiative is to provide Medicaid EPs and EHs with the tools to improve the coordination of care, transition of care and the availability of specialty registries; increasing the number of providers attesting for and meeting meaningful use requirements.

\n

\n

DHSS in partnership with the DPH has identified multiple public health systems and registries in which the current “as is” process is a manual process for reporting and data submission of public health data. Through this modernization initiative, over 15 public health systems have been defined as meeting the specifications as specialized registries. However, the submissions vary in format, transport and destination. Additionally, the registry data is housed in multiple databases that are used across the agency.

\n

The anticipated registries to be made available for electronic submission by providers include, but not limited to:

\n\n

The requested funding will provide a mechanism for the design, development and implementation of registry database will store registry data in a centralized location; improving security of the data, reliability, performance, integration of datasets, and the range of analytical methods available. Funding is requested for the implementation of Microsoft’s Dynamic CRM tool, which sits on top of SQL Server and provides the required functionality to provide robust reporting and programming methods. This modular approach will provide rapid integration of the Master Client Index (MCI) with registries, and can support the DHSS Enterprise Service Bus (ESB) which already supports integration with the statewide HIE.

\n

\n

The projected data flow, named the DHSS Gateway, is up at the top. @Bren bug fix!

\n

\n

Through the implementation of the modernization initiative, providers will have the ability to submit public health data to a single point of entry; the HIE. The HIE will then pass the received submissions through the DHSS Gateway data store, which will store and parse the data for the individual registries; offering a streamlined and efficient method of submission.

\n

\n

III.C.3 Case Management System Implementation

\n

The Department of Health and Social Services is requesting funding for the design, development, and implementation of a robust, modular care management solution to support the care and services provided to Tycho citizens. This solution will allow Department of Health and Social Services to be more efficient in treating Tycho citizenswe serve across multiple divisions and will allow the patient’s healthcare record to more easily follow their care in a secure, electronic manner. In turn, this will support coordination of care for patients receiving services by various entities. This solution will be designed and implanted through contracting within the statewide Health Information Exchange to take advantage of other service offerings provided by the statewide Health Information Exchange. The modular solution implemented will align with the Medicaid Information Technology Architecture 3.0 business processes to meet the requirements for the department. The department will utilize existing functionality or modules to meet the requirements wherever possible.

\n

\n

III.C.4 MCI Enhancement

\n

Tycho's Medicaid is requesting funding to support the continued design, development and implementation of modifications to the statewide MCI to improve activities for EPs and EHs trying to achieve meaningful use across the state of Tycho. Development of the MCI will provide short and long-term value to providers by reducing de-duplication of client data. An enhanced MCI will support creation of a unique client identifier for each individual. This will allow correlation of all known instances of client data and records for each client. The requested funding will support the cost of state personnel and resources to develop requirements and synchronize the Department’s MCI to the HIE Master Patient Index (eMPI) to provide a more robust demographic source of data for the HIE eMPI and provide new data or updated demographic information from the HIE to the Department’s MCI. This project is critical for improving coordination of care through the HIE.

\n", + expenses: [ + { + description: '', + category: 'Hardware, software, and licensing', + years: { '2020': 0, '2021': 0 } + } + ], + fundingSource: 'HIE', + objectives: [ + { + objective: 'Identifiy PH needs', + keyResults: [ + { + baseline: 'incomplete', + keyResult: + 'Complete a build/implementation plan by Summery 2020', + target: 'complete' } + ] + }, + { + objective: 'Connect PH systems to HIE', + keyResults: [ + { + baseline: '0 systems connected', + keyResult: 'Connect all 3 PH systems to HIE by Fall 2020', + target: '3 systems connected' + } + ] + } + ], + name: 'Public Health System Modernization', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2017-03-31', + milestone: 'PH Completion of requirements gathering' + }, + { + endDate: '2021-09-30', + milestone: 'PH Development and implementation of CRM Tool' + }, + { + endDate: '2021-09-30', + milestone: 'PH Connection of Public Health systems to HIE' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: '', + description: '', + years: { + '2020': { amt: 0, perc: 0 }, + '2021': { amt: 0, perc: 0 } } - ], - federalCitations: {}, - incentivePayments: { - ehAmt: { - '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, - '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } - }, - ehCt: { - '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, - '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } - }, - epAmt: { - '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, - '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } + } + ], + summary: + 'The purpose of PH modernization is to provide Medicaid EPs and EHs with the tools to improve the coordination of care, transition of care and the availability of specialty registries; increasing the number of providers attesting for meaningful use.', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + }, + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } + } + }, + { + alternatives: + '

Must do MITA 3.0 because MITA is awesome and gives Tycho a standardized view of their Medicaid IT maturity. 

\n', + contractorResources: [ + { + description: + 'Research for and RFP development for MITA 3.0 SSA', + end: '', + hourly: { + data: { + '2020': { hours: '', rate: '' }, + '2021': { hours: '', rate: '' } + }, + useHourly: false }, - epCt: { - '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, - '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } - } + name: 'Tech Consulting Inc.', + start: '', + totalCost: 264574, + years: { '2020': 450000, '2021': 150000 } }, - keyPersonnel: [ - { - name: 'James Holden', - position: 'HIT Coordinator', - email: 'JimPushesButtons@tycho.com', - isPrimary: true, - fte: { '2020': 1, '2021': 1 }, - hasCosts: true, - costs: { '2020': 100000, '2021': 100000 } + { + description: 'MITA 3.0 implementation.', + end: '', + hourly: { + data: { + '2020': { hours: '', rate: '' }, + '2021': { hours: '', rate: '' } + }, + useHourly: false }, - { - name: 'Fred Johnson', - position: 'State Medicaid Director', - email: 'FJohnson@tycho.com', - isPrimary: false, - fte: { '2020': 0.3, '2021': 0.3 }, - hasCosts: false, - costs: { '2020': 0, '2021': 0 } - } - ], - narrativeHIE: - "

Tyco's existing health information infrastructure consists of various organizations operating at the enterprise, local, regional and state levels, and includes:

\n\n

The Tycho HIE has planned to implement a robust public health modernization plan which includes the development of specialized registries and interfaces to the HIE to significantly increase the ability for EPs and EHs to achieve meaningful use. Additionally, plans to collect CQM data and the creation of a Personal Health Record (PHR) has been identified as activities to complete.

\n

\n

Payers/Providers must complete a participation agreement form and possible addendum to participate in the HIE and other services. Governance for the HIE has been defined by the State statute, any related regulations and by the HIE board of directors.

\n

\n

Appropriate cost allocation is a fundamental principle of the federal FFP program to ensure that private sector beneficiaries of public investments are covering the incremental cost of their use. A sustainability plan for proportional investments by other payers/providers than Medicaid was developed in concert with the Tycho HIE Board of Directors and a broad cross-section of stakeholders under the leadership of the Tycho HIE Executive Director and State HIT Coordinator. The Tycho HIE’s fee structure and detailed participation agreements can be viewed at: tychoMedicaid.com

", - narrativeHIT: - '

Continued Operations of the Medicaid EHR Incentive Payment Program

\n

\n

Participate in the CMS EHR incentive program and continue to administer payments to EPs and EHs through the remaining years of the program (2021).

', - narrativeMMIS: - "

Medicaid Claims Data Feed to the HIE

\n

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

", - previousActivityExpenses: { - '2017': { - hithie: { federalActual: 140000, totalApproved: 280000 }, - mmis: { - '50': { federalActual: 23445, totalApproved: 82545 }, - '75': { federalActual: 23440, totalApproved: 75340 }, - '90': { federalActual: 235720, totalApproved: 262460 } - } + name: 'TBD', + start: '', + totalCost: 64574, + years: { '2020': 200000, '2021': 500000 } + } + ], + costAllocation: { + '2020': { + ffp: { + federal: 50, + state: 50 }, - '2018': { - hithie: { federalActual: 146346, totalApproved: 234526 }, - mmis: { - '50': { federalActual: 129387, totalApproved: 375445 }, - '75': { federalActual: 413246, totalApproved: 654455 }, - '90': { federalActual: 614544, totalApproved: 863455 } - } + other: 0 + }, + '2021': { + ffp: { + federal: 90, + state: 10 }, - '2019': { - hithie: { federalActual: 320000, totalApproved: 540000 }, - mmis: { - '50': { federalActual: 0, totalApproved: 0 }, - '75': { federalActual: 0, totalApproved: 0 }, - '90': { federalActual: 0, totalApproved: 0 } + other: 0 + } + }, + costAllocationNarrative: { + methodology: '', + '2020': { + otherSources: '' + }, + '2021': { + otherSources: '' + } + }, + description: + '

III.B.4 HITECH MITA 3.0 Development and Implementation

\n

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

\n', + expenses: [ + { + description: '', + category: 'Equipment and supplies', + years: { '2020': 25000, '2021': 25000 } + } + ], + fundingSource: 'HIT', + objectives: [ + { + objective: 'Complete MITA 3.0 HITECH portion.', + keyResults: [ + { + baseline: '', + keyResult: + 'Complete MITA 3.0 HITECH portion by July 2020', + target: '' } - } + ] + } + ], + name: 'MITA 3.0 Assessment', + plannedEndDate: '', + plannedStartDate: '', + schedule: [ + { + endDate: '2020-02-28', + milestone: 'MITA 3.0 SS-A Project' }, - previousActivitySummary: - '

EHR Incentive Payment Program

\n

As of May 31, 2018, the state has disbursed $22,145,454 to 1200Eligible Professionals (EPs) and $19,884,887 to 32 Eligible Hospitals (EHs) for Adopt/Implement/Upgrade (AIU) incentive payments and $25,454,444 for 1988 EP Meaningful Use (MU) Incentive payments and $19,444,444 for 98 EH MU Incentive payments. Tycho has anticipated payments for the remainder of FFY19 through FFY20 to be approximately $98,888,555.

\n

\n

Tycho has updated the SMHP, and CMS has approved, to reflect the changes such as the auditing contract, the State’s audit strategy, and alignment with the Stage 3 Final Rule. This IAPDU #6 includes updated costs for existing project and EHR Incentive Payment Program administration, as well as several new initiatives. The SMHP will continue to be aligned with CMS rule changes and the IAPDU requests. All planning activities approved under the PAPD have been completed. Table 1 below identifies the approved amounts from the PAPD and the expenses available in the state’s accounting system. The PAPD previously approved was requested to be closed out to the HIT IAPD in March 2011; the remaining balance was carried over to the approved IAPD at that time to complete planning activities related to MU.

\n

\n

IAPD Funding Milestones and Expenditures

\n

The first IAPDU which was approved by CMS in October 2012 requested funding for HIT initiatives. The primary focus of the activities in the IAPDU # 2, which was approved in April 2013 was support of MU Stage 1, preparation for MU Stage 2, and the ongoing administration of the EHR Incentive Payment program. Subsequent IAPD submissions requested continued funding to support program operations and modernization of enterprise systems.

\n

\n

Tycho recently transitioned to a new state-wide financial system and it would be overly burdensome and a manual process to detail expenses out in the method done in previous HITECH IAPD submissions. Tycho has elected to report expenditures based on the CMS-64 line reporting for HITECH as this will be the most audible method due to the state’s transition to a new financial system.

\n

Detailed List of Expenditure Types:

\n', - programOverview: - "

The Department is the state agency that administers the Tycho Medicaid program. The Information Technology (IT) Planning Office is responsible for Health Information Technology (HIT) efforts. Tycho Medicaid has elected to participate in the Electronic Health Record (EHR) Provider Incentive Payment Program funded through CMS. In accordance with Federal regulations, Tycho, requests enhanced Federal Financial Participation (FFP) from the CMS through this Implementation Advance Planning Document Update #9 (IAPDU#9). The State Medicaid Health Information Technology Plan (SMHP) was approved by CMS in March 2017, and is currently being updated for submission in June 2020.

\n

\n

The original IAPD request supported the first phase of the Station's participation in the development and expansion of the use of EHR and collaboration among state entities in a Health Information Exchange (HIE) network. In the first phase, Tycho implemented the system changes necessary to support the Tycho EHR Provider Incentive Payment Program as well as the administrative supports necessary for implementation and operation of this program. 

\n
    \n
  1. The first IAPDU requested additional support for the EHR Provider Incentive Payment Program and additional project support.
    2. \n
  2. The second IAPDU requested funding for the Division of Senior and Disabilities Services (DSDS) Automated Service Plan (ASP) system, supporting expanded use of EHRs.
    3. \n
  3. The third IAPDU requested additional and continued support of HIT initiatives.
    4. \n
\n

Effective with the approval of the original IAPD, Tycho closed the Planning Advance Planning Document (PAPD) submitted to CMS in December 2009 and opened the IAPD. This document represents the sixth update to the approved IAPD.

\n

\n

This funding request time frame is for the period of October 1, 2018 to September 30, 2021. 

", - state: 'mo', - stateProfile: { - medicaidDirector: { - name: 'Cornelius Fudge', - email: 'c.fudge@ministry.magic', - phone: '5551234567' - }, - medicaidOffice: { - address1: '100 Round Sq', - address2: '', - city: 'Cityville', - state: 'MO', - zip: '12345' + { + endDate: '2020-12-31', + milestone: 'HITECH SS-A Assessment' + } + ], + standardsAndConditions: { + doesNotSupport: '', + supports: '' + }, + statePersonnel: [ + { + title: 'State MITA Person', + description: '1', + years: { + '2020': { amt: 100000, perc: 0.5 }, + '2021': { amt: 100000, perc: 1 } } + } + ], + summary: + 'DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A.', + quarterlyFFP: { + '2020': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } }, - status: 'draft', - updated: '2019-10-03T20:12:48.298Z', - years: ['2020', '2021'] + '2021': { + '1': { combined: 25, contractors: 25, inHouse: 25 }, + '2': { combined: 25, contractors: 25, inHouse: 25 }, + '3': { combined: 25, contractors: 25, inHouse: 25 }, + '4': { combined: 25, contractors: 25, inHouse: 25 } + } } } - ]); + ], + federalCitations: {}, + incentivePayments: { + ehAmt: { + '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, + '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } + }, + ehCt: { + '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, + '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } + }, + epAmt: { + '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, + '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } + }, + epCt: { + '2020': { '1': 0, '2': 0, '3': 0, '4': 0 }, + '2021': { '1': 0, '2': 0, '3': 0, '4': 0 } + } + }, + keyPersonnel: [ + { + name: 'James Holden', + position: 'HIT Coordinator', + email: 'JimPushesButtons@tycho.com', + isPrimary: true, + fte: { '2020': 1, '2021': 1 }, + hasCosts: true, + costs: { '2020': 100000, '2021': 100000 } + }, + { + name: 'Fred Johnson', + position: 'State Medicaid Director', + email: 'FJohnson@tycho.com', + isPrimary: false, + fte: { '2020': 0.3, '2021': 0.3 }, + hasCosts: false, + costs: { '2020': 0, '2021': 0 } + } + ], + narrativeHIE: + "

Tyco's existing health information infrastructure consists of various organizations operating at the enterprise, local, regional and state levels, and includes:

\n\n

The Tycho HIE has planned to implement a robust public health modernization plan which includes the development of specialized registries and interfaces to the HIE to significantly increase the ability for EPs and EHs to achieve meaningful use. Additionally, plans to collect CQM data and the creation of a Personal Health Record (PHR) has been identified as activities to complete.

\n

\n

Payers/Providers must complete a participation agreement form and possible addendum to participate in the HIE and other services. Governance for the HIE has been defined by the State statute, any related regulations and by the HIE board of directors.

\n

\n

Appropriate cost allocation is a fundamental principle of the federal FFP program to ensure that private sector beneficiaries of public investments are covering the incremental cost of their use. A sustainability plan for proportional investments by other payers/providers than Medicaid was developed in concert with the Tycho HIE Board of Directors and a broad cross-section of stakeholders under the leadership of the Tycho HIE Executive Director and State HIT Coordinator. The Tycho HIE’s fee structure and detailed participation agreements can be viewed at: tychoMedicaid.com

", + narrativeHIT: + '

Continued Operations of the Medicaid EHR Incentive Payment Program

\n

\n

Participate in the CMS EHR incentive program and continue to administer payments to EPs and EHs through the remaining years of the program (2021).

', + narrativeMMIS: + "

Medicaid Claims Data Feed to the HIE

\n

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

", + previousActivityExpenses: { + '2017': { + hithie: { federalActual: 140000, totalApproved: 280000 }, + mmis: { + '50': { federalActual: 23445, totalApproved: 82545 }, + '75': { federalActual: 23440, totalApproved: 75340 }, + '90': { federalActual: 235720, totalApproved: 262460 } + } + }, + '2018': { + hithie: { federalActual: 146346, totalApproved: 234526 }, + mmis: { + '50': { federalActual: 129387, totalApproved: 375445 }, + '75': { federalActual: 413246, totalApproved: 654455 }, + '90': { federalActual: 614544, totalApproved: 863455 } + } + }, + '2019': { + hithie: { federalActual: 320000, totalApproved: 540000 }, + mmis: { + '50': { federalActual: 0, totalApproved: 0 }, + '75': { federalActual: 0, totalApproved: 0 }, + '90': { federalActual: 0, totalApproved: 0 } + } + } + }, + previousActivitySummary: + '

EHR Incentive Payment Program

\n

As of May 31, 2018, the state has disbursed $22,145,454 to 1200Eligible Professionals (EPs) and $19,884,887 to 32 Eligible Hospitals (EHs) for Adopt/Implement/Upgrade (AIU) incentive payments and $25,454,444 for 1988 EP Meaningful Use (MU) Incentive payments and $19,444,444 for 98 EH MU Incentive payments. Tycho has anticipated payments for the remainder of FFY19 through FFY20 to be approximately $98,888,555.

\n

\n

Tycho has updated the SMHP, and CMS has approved, to reflect the changes such as the auditing contract, the State’s audit strategy, and alignment with the Stage 3 Final Rule. This IAPDU #6 includes updated costs for existing project and EHR Incentive Payment Program administration, as well as several new initiatives. The SMHP will continue to be aligned with CMS rule changes and the IAPDU requests. All planning activities approved under the PAPD have been completed. Table 1 below identifies the approved amounts from the PAPD and the expenses available in the state’s accounting system. The PAPD previously approved was requested to be closed out to the HIT IAPD in March 2011; the remaining balance was carried over to the approved IAPD at that time to complete planning activities related to MU.

\n

\n

IAPD Funding Milestones and Expenditures

\n

The first IAPDU which was approved by CMS in October 2012 requested funding for HIT initiatives. The primary focus of the activities in the IAPDU # 2, which was approved in April 2013 was support of MU Stage 1, preparation for MU Stage 2, and the ongoing administration of the EHR Incentive Payment program. Subsequent IAPD submissions requested continued funding to support program operations and modernization of enterprise systems.

\n

\n

Tycho recently transitioned to a new state-wide financial system and it would be overly burdensome and a manual process to detail expenses out in the method done in previous HITECH IAPD submissions. Tycho has elected to report expenditures based on the CMS-64 line reporting for HITECH as this will be the most audible method due to the state’s transition to a new financial system.

\n

Detailed List of Expenditure Types:

\n', + programOverview: + "

The Department is the state agency that administers the Tycho Medicaid program. The Information Technology (IT) Planning Office is responsible for Health Information Technology (HIT) efforts. Tycho Medicaid has elected to participate in the Electronic Health Record (EHR) Provider Incentive Payment Program funded through CMS. In accordance with Federal regulations, Tycho, requests enhanced Federal Financial Participation (FFP) from the CMS through this Implementation Advance Planning Document Update #9 (IAPDU#9). The State Medicaid Health Information Technology Plan (SMHP) was approved by CMS in March 2017, and is currently being updated for submission in June 2020.

\n

\n

The original IAPD request supported the first phase of the Station's participation in the development and expansion of the use of EHR and collaboration among state entities in a Health Information Exchange (HIE) network. In the first phase, Tycho implemented the system changes necessary to support the Tycho EHR Provider Incentive Payment Program as well as the administrative supports necessary for implementation and operation of this program. 

\n
    \n
  1. The first IAPDU requested additional support for the EHR Provider Incentive Payment Program and additional project support.
    2. \n
  2. The second IAPDU requested funding for the Division of Senior and Disabilities Services (DSDS) Automated Service Plan (ASP) system, supporting expanded use of EHRs.
    3. \n
  3. The third IAPDU requested additional and continued support of HIT initiatives.
    4. \n
\n

Effective with the approval of the original IAPD, Tycho closed the Planning Advance Planning Document (PAPD) submitted to CMS in December 2009 and opened the IAPD. This document represents the sixth update to the approved IAPD.

\n

\n

This funding request time frame is for the period of October 1, 2018 to September 30, 2021. 

", + stateProfile: { + medicaidDirector: { + name: 'Cornelius Fudge', + email: 'c.fudge@ministry.magic', + phone: '5551234567' + }, + medicaidOffice: { + address1: '100 Round Sq', + address2: '', + city: 'Cityville', + state: 'MO', + zip: '12345' + } + }, + years: ['2020', '2021'] + } }; + +const seed = async knex => { + const { state_id } = await knex('users').first('state_id'); // eslint-disable-line camelcase + + if (!validateApd(apd.document)) { + logger.warn('apd document is not valid'); + logger.warn(validateApd.errors); + } + + await knex('apds').insert({ + state_id, // eslint-disable-line camelcase + ...apd + }); +}; + +module.exports = { + apd, + seed +} diff --git a/api/seeds/development/apds.test.js b/api/seeds/development/apds.test.js new file mode 100644 index 0000000000..be4780acd6 --- /dev/null +++ b/api/seeds/development/apds.test.js @@ -0,0 +1,13 @@ +const tap = require('tap'); +const { apd } = require('./apds'); + +const { validateApd } = require('../../schemas'); + +tap.test('development APD seed document', async t => { + t.true(validateApd(apd.document), 'is valid, according to apd.json schema'); + t.false(validateApd.errors, 'has no reported errors'); + + if (validateApd.errors) { + t.equal([], validateApd.errors, 'has empty array of errors'); + } +}); diff --git a/api/seeds/test/4000.json b/api/seeds/test/4000.json index 5f61e6db98..07e35811e4 100644 --- a/api/seeds/test/4000.json +++ b/api/seeds/test/4000.json @@ -71,7 +71,12 @@ }, "costAllocationNarrative": { "methodology": "

No cost allocation is necessary for this activity.

\n", - "otherSources": "

No other funding is provided for this activity.

\n" + "2019": { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

\n" + }, + "2020": { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

\n" + } }, "description": "

III.A.1: Modifications to the State Level Repository

\n

Tycho Medicaid is seeking funding to design, develop, and implement modifications to the existing State Level Repository (SLR) for continued administration of the EHR Incentive Program. The modifications of the SLR for CMS program rule changes and guidance changes (Stage 3, IPPS, and OPPS) will require extensive development and implementation efforts and is essential to the effective administration of the Medicaid EHR Incentive Program. Modifications to the SLR are done in phases depending on how CMS rule changes occur. The implementation of the design elements will require provider onboarding activities to be initiated and completed including outreach and training for all program participants. The SLR will increase the efficiency with which Tycho Medicaid administers the program; allow for increased oversight and assure that the program is operated in accordance with the complex and evolving program rules and requirements.

\n

\n

Additionally, Tycho Medicaid is seeking funding to complete a security risk assessment for the State Level Repository to ensure the SLR meets the required system security standards for HIPAA, MARSe, NIST and other state and federal security requirements for information technology.

\n

\n

III.B.1 Administrative and Technical Support Consulting

\n

The DHSS is requesting funding to support activities under the Medicaid EHR Incentive Payment Program to provide technical assistance for statewide activities and implementations. Activities of this initiative will include support of the activities included in this IAPDU, SMPHU development, eCQM implementation, project management services, and assistance with the public health expansion modernization initiative.

\n", "expenses": [ @@ -381,7 +386,12 @@ }, "costAllocationNarrative": { "methodology": "

No cost allocation is necessary for this activity.

\n", - "otherSources": "" + "2019": { + "otherSources": "

No other funding is provided for this activity for FFY 2019.

\n" + }, + "2020": { + "otherSources": "

No other funding is provided for this activity for FFY 2020.

\n" + } }, "description": "

III.B.3 Medicaid Claims Data Feed to the HIE

\n

Currently, Tycho does not have an All-Payers’ Claims database that can provide consumers and DHSS with consolidated claims data. To provide healthcare statistical information and support MU, Tycho plans to interface the MMIS Data Warehouse (DW) to the HIE so that Medicaid claims data can be made available to consumers in their Personal Health Record (PHR) within the HIE. This initiative will require contractor assistance from Conduent, LLC to complete required MMIS changes as well as Tycho's HIE Service provider, Orion Health to implement the necessary HIE updates. DHSS IT Planning Office will coordinate the efforts of the three vendors.

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n

\n", "expenses": [ @@ -637,7 +647,12 @@ }, "costAllocationNarrative": { "methodology": "", - "otherSources": "" + "2019": { + "otherSources": "" + }, + "2020": { + "otherSources": "" + } }, "description": "

\n\"undefined\"\n

\n

\n

III.D. Statewide HIE Enhancement, Onboarding, and Support of Statewide HIE Operational Strategic Plan

\n

DHSS is requesting funding to support the continued enhancement and provider onboarding activities to the statewide HIE. The success of the statewide HIE is critical for improving data exchange, coordination of care, and modernizing healthcare across Tycho. The following funding requests are for projects that will provide enhanced technical capabilities to providers, support providers in onboarding, support modernizations required for Medicaid redesign, and ensure sustainability beyond State of Tycho and CMS funding. The projects have been designed to meet the following goals and desires for the statewide HIE:

\n\n

III.D.1 Behavioral Health Onboarding & Care Coordination

\n

The Department recognizes the need to increase Behavioral Health (BH) data capacity and sharing to achieve its goals and objectives related to care coordination. This includes promoting effective communication to coordinate care and enhancing the ability for providers to share and gain access to Protected Class Patient Data where appropriate. To support the capacity of data sharing and improving coordination of care, funding is requested to support Behavioral Health provider connectivity through the onboarding program by the development and implementation of a Behavioral Health-centric Unified Landing Page Application. The Behavioral Health Unified Landing Page Application will improve the quality and completeness of behavioral health data and thus, support the ability for providers to achieve MU.

\n

\n

In addition to the Unified Landing Page, funding is requested to support behavioral health provider onboarding to the HIE. The HIE onboarding program will provide funds to offset expenses required for behavioral health providers to adequately participate in statewide health information exchange. The onboarding program will support Tycho's HIE vision of increasing onboarding Medicaid providers and care coordination to help Tycho providers demonstrate MU. This program relates to the guidance provided by CMS in the SMD 16-003 letter dated February 2016 and will assist with covering costs associated with connectivity including but not limited to the following activities:

\n\n

The goal is for the onboarding program to support 40 provider organizations across the State. The initial phase of the program will be focused on Medicaid behavioral health providers with additional provider types potentially targeted in later phases of the initiative. Administrative offset funding will be on-time funding only and will be issued as pass-through funding through healtheConnect (Tycho's HIE organization). The funding will be distributed in 2 parts: 75% upon onboarding initialization (participation/contract signed) and the remaining 25% upon the HIE connection being live or in production.

\n

\n

III.D.2 HIE Strategic Planning

\n

Having a robust HIE is a critical component of Tycho's HIT landscape and will continue to play a role in enhancing Tycho's EPs and EHs ability to achieve MU. As part of the Department’s responsibility for administration of the EHR Incentive Program and in an effort to enhance the maturity of HIE in Tycho, the Department is requesting funds to support a health information exchange assessment using CMS’ standards of the HIE Maturity Model and MITA and a Strategic Plan to enhance platform functionality and initial steps necessary to establish a long-term vision of HIE in Tycho's HIT landscape. This work will further ensure that the Department’s goals and target state (To-Be vision) aligns with CMS guidelines as specified under 42 CFR 495.338, as well as the HIE Maturity Model, MITA and the Seven Standards and Conditions.

\n

\n

The Department is requesting funds to support the statewide HIE in conducting an HIE Assessment using the CMS HIE Maturity Model and MITA standards. The information gathered in the assessment will help clearly articulate the long-term HIE vision for Tycho, define a governance model, and establish a robust sustainability plan built on the framework of the HIE Maturity Model and MITA standards. This information will also be used to identify areas where the statewide HIE can provide services and make connections with the Medicaid enterprise of systems to support health information exchange requirements and sustainability of the HIE.

\n

\n

III.D.3 Integration of Social Determinants of Health

\n

To further drive Tycho's goals around improved health outcomes through HIE, the Department is seeking funds to support the integration of the Social Determinants of Health into the statewide HIE system which will improve coordination of care and information exchange across the state.

\n

\n

This is an important and practical step to help the healthcare delivery system build effective, coordinated, data-driven healthcare services into communities hit hardest by social structures and economic systems. The integration of social determinants of health data will provide support for addressing social determinants of health drivers in Tycho and will identify ways to improve intervention using Social Determinants of Health as part of a comprehensive coordinated care model impacting payment, incentivizing purposeful intervention in the specific needs of their patients and populations to improve health outcomes.

\n

\n

To complete the scope of work, the HIE will integrate a limited CDR and interface to the network as well as provide onboarding services to connect Medicaid providers. The integration of the Social Determinates of Health project will support Medicaid providers ability to achieve meaningful use by allowing providers to incorporate summary of care information from other providers into their EHR using the functions of CEHRT through the HIE.

\n

\n

III.D.4 Staff Augmentation for Adoption and Utilization

\n

DHSS seeks to support onboarding efforts to connect Medicaid Meaningful Use eligible providers and providers supporting eligible providers to the HIE. The provider onboarding program will fund staffing outreach/educational support and technical services to Medicaid EPs that have adopted EHRs but not made HIE use part of day to day operations, not made use of new HIE capabilities, not yet connected, or were unable to take advantage of the ONC Regional Extension Center (REC) services because they were not eligible.

\n

Onboarding will include efforts to provide outreach/educational support and technical services. The Provider Onboarding Program includes the following objectives:

\n\n

The funds requested in this IAPD-U will be used to establish provider groups for onboarding support, establish onboarding benchmarks, and specifically implement training and technical assistance services. Funds will be used to assess barriers to onboarding and adoption of the HIE services, strategies for work flow analysis, and other ways to reduce Medicaid provider burden to onboard to the HIE. The proposed solution shall provide support services that coordinate with HIE processes to onboard and improve participant interoperability (e.g., clinic readiness assessments, bi-directional connection builds development and deployment of bi-directional interface with Medicaid) through utilization of the HIE system.

\n

\n

The adoption and utilization program will continue to expand outreach efforts and technical services to Medicaid providers and continue to boost MU numbers and milestones in Tycho to enhance the HIT vision outlined in the SMHP. In addition to AIU and MU education and technical services, the program will also seek to assist providers in meeting MU Stages 2 and 3 through onboarding provider interfaces and providing the capabilities to automatically meet several MU measures through the enhanced functionality of the HIE.

\n

\n

III.D.5 Trauma Registry

\n

DHSS recognizes the need for a trauma registry as an essential component of information exchange. The trauma registry is necessary to drive an efficient and effective performance improvement program for the care of injured enrollees. Furthermore, as published recently by SAMHSA, there are a range of evidence-based treatments that are effective in helping children and youth who have experienced trauma. Through the HIE, health providers will share and gain access to trauma information to drive an efficient and effective performance improvement program for the care of injured enrollees. The trauma register information will interoperate with the Behavioral Health Unified Landing Page Application to promote evidence-based treatments that are effective in helping enrollees who have experienced trauma. The trauma registry will be recognized as a specialized registry by the State to support MU and data exchange.

\n

\n

III.D.6 Air Medical Resource Location

\n

Tycho is currently struggling with tracking and maintaining the location and availability of air medical resources within the state. This information is critical to the timely delivery of care given the remote nature of Tycho's geography and unique dependence on air transportation. Currently, Tycho's air medical resources are using out of state dispatch centers who do not clearly understand the geography of Tycho or time needed to travel within the state. To address this gap in services and mitigate potential life-threatening delays in air medical resources, the Department would like to request funds to support the integration of the LifeMed application into the HIE. This application will allow healthcare entities: Public Health, hospitals, primary care providers, EMS, and all other authorized provider types to track all air medical resources in the state. The LifeMed application allows for tracking of specific tail numbers on planes and locations/timing for air resources.

\n

\n

The HIE will integrate with the LifeMed application so that Tycho providers and healthcare entities are able to seamlessly track all air medical resources in the state, thus greatly improve coordination and transition of care. The ability to track this information through the HIE will further support providers ability to enhance care coordination by accurately tracking patient location and improves health information exchange by giving providers access to information on patient’s location to submit summary of care records through the HIE to other provider EHR systems. Funds will be used to support the LifeMed software costs, provider training and implementation services.

\n

\n

III.D.7 AURORA-HIE Integration

\n

AURORA is a Public Health online patient care reporting system for EMS developed by Image Trend. The Department is requesting funds to support the connection of the AURORA system to the HIE. This activity would activate the HIE integration with the Image Trend solution to allow for Medicaid providers to send patient information to the AURORA system through the HIE. Upon delivery of the patient to the hospital the patient’s health data from EMS would be transmitted via the HIE to the hospital’s EHR system, and when the patient is discharge the ADT feed from the hospital would be transmitted back to EMS to the AURORA system.

\n

DHSS is seeking funds to integrate the AURORA Public Health online patient care reporting system for EMS to the HIE to help support Medicaid providers ability to achieve Meaningful Use by meeting objectives and measures pertaining to Health Information Exchange, Coordination of Care, and Public Health Reporting. Funds will be used to develop interfaces between the HIE and 10 hospitals and provider training and technical onboarding assistance to providers to connect to the HIE and AURORA system.

\n", "expenses": [ @@ -860,7 +875,12 @@ }, "costAllocationNarrative": { "methodology": "", - "otherSources": "" + "2019": { + "otherSources": "none" + }, + "2020": { + "otherSources": "none" + } }, "description": "

III.C.1 Medicaid Personal Health Record (PHR)/Blue Button Initiative

\n

DHSS is requesting HITECH funding to support the onboarding of Medicaid recipients to the developed personal health record (PHR) available within the HIE. The requested funds will be utilized to enhance the ability of patients to access their own health care data in an electronic format that supports MU CQMs including EP Core Measure: Electronic copy of health information. Medicaid PHR/Blue Button (or similar) implementation supports this functionality.

\n

\n

The PHR will not collect CQMs or interface to public health registries. However, it will provide short and long-term value to providers by assisting them in achieving MU.

\n

Alaska plans to integrate the MMIS DW into the HIE, allowing Medicaid recipients to view their Medicaid claims information in a portal and access it through a Blue Button (or similar) download. Additionally, this initiative will benefit providers by assisting them in achieving MU by helping them meet View, Download, and Transmit (VDT) requirements.

\n

\n

This Medicaid PHR/Blue Button (or similar) approach allows providers to meet VDT requirements without having to create individual patient portals. This supports providers in achieving MU. Medicaid Eligible population will benefit by being able to obtain their Medicaid claim information, along with access to their PHRs. See further cost allocation details in Section VIII and Appendix D.

\n", "expenses": [ @@ -1041,7 +1061,12 @@ }, "costAllocationNarrative": { "methodology": "", - "otherSources": "" + "2019": { + "otherSources": "none" + }, + "2020": { + "otherSources": "none" + } }, "description": "

\n

III.C.2 Public Health System Modernization

\n

In order to support meaningful use and provide specialized registries for EPs and EHs to have the ability to electronically report to the registries, Tycho is requesting funding to undergo a transformation and modernization of the current public health systems. The purpose of this modernization initiative is to provide Medicaid EPs and EHs with the tools to improve the coordination of care, transition of care and the availability of specialty registries; increasing the number of providers attesting for and meeting meaningful use requirements.

\n

\n

DHSS in partnership with the DPH has identified multiple public health systems and registries in which the current “as is” process is a manual process for reporting and data submission of public health data. Through this modernization initiative, over 15 public health systems have been defined as meeting the specifications as specialized registries. However, the submissions vary in format, transport and destination. Additionally, the registry data is housed in multiple databases that are used across the agency.

\n

The anticipated registries to be made available for electronic submission by providers include, but not limited to:

\n\n

The requested funding will provide a mechanism for the design, development and implementation of registry database will store registry data in a centralized location; improving security of the data, reliability, performance, integration of datasets, and the range of analytical methods available. Funding is requested for the implementation of Microsoft’s Dynamic CRM tool, which sits on top of SQL Server and provides the required functionality to provide robust reporting and programming methods. This modular approach will provide rapid integration of the Master Client Index (MCI) with registries, and can support the DHSS Enterprise Service Bus (ESB) which already supports integration with the statewide HIE.

\n

\n

The projected data flow, named the DHSS Gateway, is up at the top. @Bren bug fix!

\n

\n

Through the implementation of the modernization initiative, providers will have the ability to submit public health data to a single point of entry; the HIE. The HIE will then pass the received submissions through the DHSS Gateway data store, which will store and parse the data for the individual registries; offering a streamlined and efficient method of submission.

\n

\n

III.C.3 Case Management System Implementation

\n

The Department of Health and Social Services is requesting funding for the design, development, and implementation of a robust, modular care management solution to support the care and services provided to Tycho citizens. This solution will allow Department of Health and Social Services to be more efficient in treating Tycho citizenswe serve across multiple divisions and will allow the patient’s healthcare record to more easily follow their care in a secure, electronic manner. In turn, this will support coordination of care for patients receiving services by various entities. This solution will be designed and implanted through contracting within the statewide Health Information Exchange to take advantage of other service offerings provided by the statewide Health Information Exchange. The modular solution implemented will align with the Medicaid Information Technology Architecture 3.0 business processes to meet the requirements for the department. The department will utilize existing functionality or modules to meet the requirements wherever possible.

\n

\n

III.C.4 MCI Enhancement

\n

Tycho's Medicaid is requesting funding to support the continued design, development and implementation of modifications to the statewide MCI to improve activities for EPs and EHs trying to achieve meaningful use across the state of Tycho. Development of the MCI will provide short and long-term value to providers by reducing de-duplication of client data. An enhanced MCI will support creation of a unique client identifier for each individual. This will allow correlation of all known instances of client data and records for each client. The requested funding will support the cost of state personnel and resources to develop requirements and synchronize the Department’s MCI to the HIE Master Patient Index (eMPI) to provide a more robust demographic source of data for the HIE eMPI and provide new data or updated demographic information from the HIE to the Department’s MCI. This project is critical for improving coordination of care through the HIE.

\n", "expenses": [ @@ -1232,7 +1257,12 @@ }, "costAllocationNarrative": { "methodology": "", - "otherSources": "" + "2019": { + "otherSources": "none" + }, + "2020": { + "otherSources": "none" + } }, "description": "

III.B.4 HITECH MITA 3.0 Development and Implementation

\n

DHSS is requesting funding to support the completion of a MITA 3.0 State Self-Assessment. Initially, funding will be utilized to support the development of a competitive procurement and support of planning efforts for the MITA 3.0 SS-A. Following the release of the procurement, a vendor will be selected to design, develop, and implement a commercial off the shelf solution for completing a HITECH MITA 3.0 SS-A and supporting the modernization of enterprise systems by assuring compliance to the MITA standards.

\n", "expenses": [ @@ -1519,7 +1549,6 @@ }, "previousActivitySummary": "", "programOverview": "", - "state": "mn", "stateProfile": { "medicaidDirector": { "name": "", @@ -1534,7 +1563,5 @@ "zip": "" } }, - "status": "draft", - "updated": "1910-06-18T09:00:00.000Z", - "years": [] + "years": ["2019", "2020"] } diff --git a/api/seeds/test/4001.json b/api/seeds/test/4001.json index ba449c7f90..ac4e3a7958 100644 --- a/api/seeds/test/4001.json +++ b/api/seeds/test/4001.json @@ -1,60 +1,87 @@ { - "id": 4001, "name": "AZ-1865-12-06-HITECH-APD", "activities": [ { "id": 4110, - "alternatives": null, + "alternatives": "", "contractorResources": [ { - "description": null, - "end": null, + "description": "", + "end": "", + "hourly": { + "data": { + "2019": { + "hours": "", + "rate": "" + }, + "2020": { + "hours": "", + "rate": "" + } + }, + "useHourly": false + }, "hourlyData": [], "id": 9900, - "name": null, - "start": null, - "totalCost": null, - "useHourly": false, - "years": [] + "name": "", + "start": "", + "totalCost": 0, + "years": { + "1865": 0, + "1866": 0 + } } ], - "costAllocation": [], - "costAllocationNarrative": { "methodology": null, "otherSources": null }, - "description": null, + "costAllocation": {}, + "costAllocationNarrative": { + "methodology": "", + "2019": { + "otherSources": "none" + }, + "2020": { + "otherSources": "none" + } + }, + "description": "", "expenses": [], - "fundingSource": null, - "name": null, + "fundingSource": false, + "name": "", "objectives": [], - "plannedEndDate": null, - "plannedStartDate": null, + "plannedEndDate": "", + "plannedStartDate": "", "schedule": [], - "standardsAndConditions": null, + "standardsAndConditions": { + "doesNotSupport": "", + "supports": "" + }, "statePersonnel": [], - "summary": null, - "quarterlyFFP": [] + "summary": "", + "quarterlyFFP": {} } ], - "federalCitations": null, - "incentivePayments": [], + "federalCitations": {}, + "incentivePayments": { + "ehAmt": {}, + "ehCt": {}, + "epAmt": {}, + "epCt": {} + }, "keyPersonnel": [], - "narrativeHIE": null, - "narrativeHIT": null, - "narrativeMMIS": null, - "previousActivityExpenses": [], - "previousActivitySummary": null, - "programOverview": null, - "state": "az", + "narrativeHIE": "", + "narrativeHIT": "", + "narrativeMMIS": "", + "previousActivityExpenses": {}, + "previousActivitySummary": "", + "programOverview": "", "stateProfile": { - "medicaidDirector": { "name": null, "email": null, "phone": null }, + "medicaidDirector": { "name": "", "email": "", "phone": "" }, "medicaidOffice": { - "address1": null, - "address2": null, - "city": null, - "state": null, - "zip": null + "address1": "", + "address2": "", + "city": "", + "state": "", + "zip": "" } }, - "status": "draft", - "updated": "1919-06-04T16:30:00.000Z", - "years": null + "years": ["2019", "2020"] } diff --git a/api/seeds/test/4002.json b/api/seeds/test/4002.json index a3f3cc23b3..8ac88b8e83 100644 --- a/api/seeds/test/4002.json +++ b/api/seeds/test/4002.json @@ -1,28 +1,29 @@ { - "id": 4002, "name": "MN-1936-08-03-HITECH-APD", "activities": [], - "federalCitations": null, - "incentivePayments": [], + "federalCitations": {}, + "incentivePayments": { + "ehAmt": {}, + "ehCt": {}, + "epAmt": {}, + "epCt": {} + }, "keyPersonnel": [], - "narrativeHIE": null, - "narrativeHIT": null, - "narrativeMMIS": null, - "previousActivityExpenses": [], - "previousActivitySummary": null, - "programOverview": null, - "state": "mn", + "narrativeHIE": "", + "narrativeHIT": "", + "narrativeMMIS": "", + "previousActivityExpenses": {}, + "previousActivitySummary": "", + "programOverview": "", "stateProfile": { - "medicaidDirector": { "name": null, "email": null, "phone": null }, + "medicaidDirector": { "name": "", "email": "", "phone": "" }, "medicaidOffice": { - "address1": null, - "address2": null, - "city": null, - "state": null, - "zip": null + "address1": "", + "address2": "", + "city": "", + "state": "", + "zip": "" } }, - "status": "not draft", - "updated": "1947-04-10T00:00:00.000Z", - "years": null + "years": [] } diff --git a/api/seeds/test/apds.test.js b/api/seeds/test/apds.test.js new file mode 100644 index 0000000000..faee3501a1 --- /dev/null +++ b/api/seeds/test/apds.test.js @@ -0,0 +1,25 @@ +/* eslint-disable no-shadow, global-require, import/no-dynamic-require */ +const tap = require('tap'); +const { validateApd } = require('../../schemas'); + +const apdFiles = [ + '4000.json', + '4001.json', + '4002.json' +]; + +tap.test('test APD seed documents', async t => { + apdFiles.forEach(filename => { + const document = require(`./${filename}`); + t.test(`document '${document.name}' within '${filename}'`, async t => { + t.true(validateApd(document), 'is valid, according to apd.json schema'); + t.false(validateApd.errors, 'has no reported errors'); + + // Determine the specific erroneous document properties. + if (validateApd.errors) { + t.equal(validateApd.errors.length, 0, 'has zero errors'); + t.equal([], validateApd.errors, 'has empty array of errors'); + } + }); + }); +}); diff --git a/web/audit-ci.json b/web/audit-ci.json index 5ebc75b5ff..b4206e4037 100644 --- a/web/audit-ci.json +++ b/web/audit-ci.json @@ -3,7 +3,8 @@ "package-manager": "auto", "allowlist": [ "1550|postcss-custom-properties>postcss-values-parser>is-url-superb>url-regex", - "1550|postcss-custom-properties>postcss-values-parser>url-regex" + "1550|postcss-custom-properties>postcss-values-parser>url-regex", + "1561|webpack-dev-server>selfsigned>node-forge" ], "registry": "https://registry.npmjs.org" } diff --git a/web/jest.config.js b/web/jest.config.js index dffa7718fb..6575af226f 100644 --- a/web/jest.config.js +++ b/web/jest.config.js @@ -3,6 +3,10 @@ module.exports = { rootDir: 'src', setupFiles: ['../polyfills.test.js', '../setup.enzyme.test.js'], setupFilesAfterEnv: ['../setup.rtl.test.js'], + moduleDirectories: [ + 'src', + 'node_modules' + ], moduleNameMapper: { 'apd-testing-library': '/shared/apd-testing-library.js' }, diff --git a/web/src/actions/editActivity/costAllocate.js b/web/src/actions/editActivity/costAllocate.js index bafedc9cde..5e4c640377 100644 --- a/web/src/actions/editActivity/costAllocate.js +++ b/web/src/actions/editActivity/costAllocate.js @@ -7,9 +7,9 @@ export const setCostAllocationMethodology = (index, methodology) => ({ value: methodology }); -export const setCostAllocationOtherFunding = (index, otherFunding) => ({ +export const setCostAllocationOtherFunding = (index, year, otherFunding) => ({ type: EDIT_APD, - path: `/activities/${index}/costAllocationNarrative/otherSources`, + path: `/activities/${index}/costAllocationNarrative/${year}/otherSources`, value: otherFunding }); diff --git a/web/src/actions/editActivity/costAllocate.test.js b/web/src/actions/editActivity/costAllocate.test.js index 91befd720b..71c915f4cb 100644 --- a/web/src/actions/editActivity/costAllocate.test.js +++ b/web/src/actions/editActivity/costAllocate.test.js @@ -36,12 +36,12 @@ describe('APD activity edit actions for cost allocation section', () => { }); it('dispatches an action for setting the cost allocation other funding', () => { - store.dispatch(setCostAllocationOtherFunding(1, 'rich Uncle Pennybags')); + store.dispatch(setCostAllocationOtherFunding(1, 2020, 'rich Uncle Pennybags')); expect(store.getActions()).toEqual([ { type: EDIT_APD, - path: '/activities/1/costAllocationNarrative/otherSources', + path: '/activities/1/costAllocationNarrative/2020/otherSources', value: 'rich Uncle Pennybags' } ]); diff --git a/web/src/containers/activity/ActivityRoutes.js b/web/src/containers/activity/ActivityRoutes.js index 6de05602db..b929d6e989 100644 --- a/web/src/containers/activity/ActivityRoutes.js +++ b/web/src/containers/activity/ActivityRoutes.js @@ -7,7 +7,7 @@ import { } from 'react-router-dom'; import ContractorResources from './ContractorResources'; -import CostAllocate from './CostAllocate'; +import CostAllocation from './CostAllocation'; import FFP from './CostAllocateFFP'; import Costs from './Costs'; import Milestones from './Milestones'; @@ -39,7 +39,7 @@ const ActivityRoutes = ({ activityIndex, useRouteMatch }) => {
- +
diff --git a/web/src/containers/activity/CostAllocateFFP.js b/web/src/containers/activity/CostAllocateFFP.js index b7f92cd577..c785495862 100644 --- a/web/src/containers/activity/CostAllocateFFP.js +++ b/web/src/containers/activity/CostAllocateFFP.js @@ -6,11 +6,7 @@ import { connect } from 'react-redux'; import Instruction from '../../components/Instruction'; import CostAllocateFFPQuarterly from './CostAllocateFFPQuarterly'; -import { - setCostAllocationFFPFundingSplit, - setCostAllocationFFPOtherFunding -} from '../../actions/editActivity'; -import DollarField from '../../components/DollarField'; +import { setCostAllocationFFPFundingSplit } from '../../actions/editActivity'; import Dollars from '../../components/Dollars'; import { selectCostAllocationForActivityByIndex, @@ -103,13 +99,8 @@ const CostAllocateFFP = ({ aKey, isViewOnly, setFundingSplit, - setOtherFunding, stateName }) => { - const setOther = year => e => { - setOtherFunding(activityIndex, year, e.target.value); - }; - const setFederalStateSplit = year => e => { const [federal, state] = e.target.value.split('-').map(Number); setFundingSplit(activityIndex, year, federal, state); @@ -119,10 +110,11 @@ const CostAllocateFFP = ({ return ( +

Budget and FFP

{Object.keys(years).map(ffy => ( -

- Cost Allocation and Budget for FFY {ffy} +

+ Activity {activityIndex + 1} Budget for FFY {ffy}

-
- - -
-
@@ -306,7 +281,6 @@ CostAllocateFFP.propTypes = { costSummary: PropTypes.object.isRequired, isViewOnly: PropTypes.bool, setFundingSplit: PropTypes.func.isRequired, - setOtherFunding: PropTypes.func.isRequired, stateName: PropTypes.string.isRequired }; @@ -336,8 +310,7 @@ const mapStateToProps = ( }; const mapDispatchToProps = { - setFundingSplit: setCostAllocationFFPFundingSplit, - setOtherFunding: setCostAllocationFFPOtherFunding + setFundingSplit: setCostAllocationFFPFundingSplit }; export default connect(mapStateToProps, mapDispatchToProps)(CostAllocateFFP); diff --git a/web/src/containers/activity/CostAllocateFFP.test.js b/web/src/containers/activity/CostAllocateFFP.test.js index b9b9bc2d65..06a58dd944 100644 --- a/web/src/containers/activity/CostAllocateFFP.test.js +++ b/web/src/containers/activity/CostAllocateFFP.test.js @@ -7,8 +7,7 @@ import { mapDispatchToProps } from './CostAllocateFFP'; import { - setCostAllocationFFPFundingSplit, - setCostAllocationFFPOtherFunding + setCostAllocationFFPFundingSplit } from '../../actions/editActivity'; describe('the CostAllocateFFP component', () => { @@ -152,16 +151,6 @@ describe('the CostAllocateFFP component', () => { }); }); - it('handles changes to other funding', () => { - const component = shallow(); - component - .find('DollarField') - .at(0) - .simulate('change', { target: { value: 150 } }); - - expect(props.setOtherFunding).toHaveBeenCalledWith(0, '1990', 150); - }); - it('handles changes to cost allocation dropdown', () => { const component = shallow(); component @@ -262,8 +251,7 @@ describe('the CostAllocateFFP component', () => { it('maps dispatch actions to props', () => { expect(mapDispatchToProps).toEqual({ - setFundingSplit: setCostAllocationFFPFundingSplit, - setOtherFunding: setCostAllocationFFPOtherFunding + setFundingSplit: setCostAllocationFFPFundingSplit }); }); }); diff --git a/web/src/containers/activity/CostAllocate.js b/web/src/containers/activity/CostAllocation/CostAllocate.js similarity index 51% rename from web/src/containers/activity/CostAllocate.js rename to web/src/containers/activity/CostAllocation/CostAllocate.js index eff1b88ae9..97dca2f9d2 100644 --- a/web/src/containers/activity/CostAllocate.js +++ b/web/src/containers/activity/CostAllocation/CostAllocate.js @@ -2,26 +2,21 @@ import PropTypes from 'prop-types'; import React from 'react'; import { connect } from 'react-redux'; -import { - setCostAllocationMethodology, - setCostAllocationOtherFunding -} from '../../actions/editActivity'; -import Instruction from '../../components/Instruction'; -import RichText from '../../components/RichText'; -import { Subsection } from '../../components/Section'; -import { selectActivityByIndex } from '../../reducers/activities.selectors'; +import { setCostAllocationMethodology } from '../../../actions/editActivity'; +import Instruction from '../../../components/Instruction'; +import RichText from '../../../components/RichText'; +import { selectActivityByIndex } from '../../../reducers/activities.selectors'; +import { Subsection } from '../../../components/Section'; const CostAllocate = ({ activity, activityIndex, setMethodology, - setOtherFunding }) => { const { - costAllocationNarrative: { methodology, otherSources } + costAllocationNarrative: { methodology } } = activity; const syncMethodology = html => setMethodology(activityIndex, html); - const syncOtherFunding = html => setOtherFunding(activityIndex, html); return ( - -
- - -
); }; @@ -64,8 +44,7 @@ const CostAllocate = ({ CostAllocate.propTypes = { activity: PropTypes.object.isRequired, activityIndex: PropTypes.number.isRequired, - setMethodology: PropTypes.func.isRequired, - setOtherFunding: PropTypes.func.isRequired + setMethodology: PropTypes.func.isRequired }; export const mapStateToProps = (state, { activityIndex }) => { @@ -75,9 +54,8 @@ export const mapStateToProps = (state, { activityIndex }) => { }; export const mapDispatchToProps = { - setMethodology: setCostAllocationMethodology, - setOtherFunding: setCostAllocationOtherFunding + setMethodology: setCostAllocationMethodology }; -export { CostAllocate as CostAllocateRaw }; +export { CostAllocate as plain }; export default connect(mapStateToProps, mapDispatchToProps)(CostAllocate); diff --git a/web/src/containers/activity/CostAllocate.test.js b/web/src/containers/activity/CostAllocation/CostAllocate.test.js similarity index 68% rename from web/src/containers/activity/CostAllocate.test.js rename to web/src/containers/activity/CostAllocation/CostAllocate.test.js index 0160d54432..330ff2c65b 100644 --- a/web/src/containers/activity/CostAllocate.test.js +++ b/web/src/containers/activity/CostAllocation/CostAllocate.test.js @@ -2,16 +2,15 @@ import { shallow } from 'enzyme'; import React from 'react'; import { - CostAllocateRaw as CostAllocate, + plain as CostAllocate, mapStateToProps, mapDispatchToProps } from './CostAllocate'; import { - setCostAllocationMethodology, - setCostAllocationOtherFunding -} from '../../actions/editActivity/costAllocate'; + setCostAllocationMethodology +} from '../../../actions/editActivity/costAllocate'; -describe('the CostAllocate component', () => { +describe('', () => { const props = { activityIndex: 1, activity: { @@ -21,14 +20,11 @@ describe('the CostAllocate component', () => { otherSources: 'other funding' } }, - years: ['1066', '1067'], - setMethodology: jest.fn(), - setOtherFunding: jest.fn() + setMethodology: jest.fn() }; beforeEach(() => { props.setMethodology.mockClear(); - props.setOtherFunding.mockClear(); }); test('renders correctly', () => { @@ -44,12 +40,6 @@ describe('the CostAllocate component', () => { .filterWhere(n => n.props().content === 'cost allocation') .prop('onSync')('bloop'); expect(props.setMethodology).toHaveBeenCalledWith(1, 'bloop'); - - component - .find('Connect(RichText)') - .filterWhere(n => n.props().content === 'other funding') - .prop('onSync')('florp'); - expect(props.setOtherFunding).toHaveBeenCalledWith(1, 'florp'); }); test('maps redux state to component props', () => { @@ -73,8 +63,7 @@ describe('the CostAllocate component', () => { test('maps dispatch actions to props', () => { expect(mapDispatchToProps).toEqual({ - setMethodology: setCostAllocationMethodology, - setOtherFunding: setCostAllocationOtherFunding + setMethodology: setCostAllocationMethodology }); }); }); diff --git a/web/src/containers/activity/CostAllocation/OtherFunding.js b/web/src/containers/activity/CostAllocation/OtherFunding.js new file mode 100644 index 0000000000..2257aec98b --- /dev/null +++ b/web/src/containers/activity/CostAllocation/OtherFunding.js @@ -0,0 +1,144 @@ +import PropTypes from 'prop-types'; +import React, { Fragment } from 'react'; +import { connect } from 'react-redux'; + +import Instruction from '../../../components/Instruction'; + +import { + setCostAllocationFFPOtherFunding, + setCostAllocationOtherFunding +} from '../../../actions/editActivity'; + +import DollarField from '../../../components/DollarField'; +import Dollars from '../../../components/Dollars'; +import { + selectCostAllocationForActivityByIndex, + selectActivityCostSummary, + selectActivityByIndex +} from '../../../reducers/activities.selectors'; + +import { t } from '../../../i18n'; +import RichText from '../../../components/RichText' + +const OtherFunding = ({ + activityIndex, + activity, + costAllocation, + costSummary, + setOtherFunding, + syncOtherFunding +}) => { + const { costAllocationNarrative } = activity; + const { years } = costSummary; + + const setOther = year => e => { + setOtherFunding(activityIndex, year, e.target.value); + }; + const syncOther = year => html => syncOtherFunding(activityIndex, year, html); + + return ( + +

{t('activities.otherFunding.title')}

+ {Object.keys(years).map(ffy => ( + +

+ FFY {ffy} +

+
+ + +
+ +
+ + +
+ +
+ + + + + + + + + + + + + + + +
Activity Total Cost + {years[ffy].totalCost} +
Other Funding- + {years[ffy].otherFunding} +
Medicaid Share + {years[ffy].medicaidShare} +
+ + ))} + + ); +}; + +OtherFunding.propTypes = { + activityIndex: PropTypes.number.isRequired, + activity: PropTypes.object.isRequired, + costAllocation: PropTypes.object.isRequired, + costSummary: PropTypes.object.isRequired, + setOtherFunding: PropTypes.func.isRequired, + syncOtherFunding: PropTypes.func.isRequired +}; + +const mapStateToProps = ( + state, + { activityIndex }, + { + getActivity = selectActivityByIndex, + getCostAllocation = selectCostAllocationForActivityByIndex, + getCostSummary = selectActivityCostSummary, + } = {} +) => { + const activity = getActivity(state, { activityIndex }); + return { + activity, + costAllocation: getCostAllocation(state, { activityIndex }), + costSummary: getCostSummary(state, { activityIndex }), + }; +}; + +const mapDispatchToProps = { + setOtherFunding: setCostAllocationFFPOtherFunding, + syncOtherFunding: setCostAllocationOtherFunding +}; + +export default connect(mapStateToProps, mapDispatchToProps)(OtherFunding); + +export { + OtherFunding as plain, + mapStateToProps, + mapDispatchToProps +}; diff --git a/web/src/containers/activity/CostAllocation/OtherFunding.test.js b/web/src/containers/activity/CostAllocation/OtherFunding.test.js new file mode 100644 index 0000000000..584b1f4955 --- /dev/null +++ b/web/src/containers/activity/CostAllocation/OtherFunding.test.js @@ -0,0 +1,72 @@ +import { shallow } from 'enzyme'; +import React from 'react'; + +import { plain as OtherFunding, mapDispatchToProps } from './OtherFunding'; +import { + setCostAllocationFFPOtherFunding, + setCostAllocationOtherFunding +} from '../../../actions/editActivity'; + +describe('', () => { + const props = { + activityIndex: 1, + activity: { + key: 'activity key', + costAllocationNarrative: { + methodology: 'cost allocation', + '1066': { otherSources: 'other funding for FFY 1066' }, + '1067': { otherSources: 'other funding for FFY 1067' } + } + }, + costAllocation: { + '1066': { + other: 1235 + }, + '1067': { + other: 1234 + } + }, + costSummary: { + years: { + '1066': { + totalCost: 5459076, + otherFunding: 4322, + medicaidShare: 3450509 + }, + '1067': { + totalCost: 5459077, + otherFunding: 4323, + medicaidShare: 3450510 + } + } + }, + setOtherFunding: jest.fn(), + syncOtherFunding: jest.fn() + }; + + beforeEach(() => { + props.setOtherFunding.mockClear(); + }); + + it('renders correctly', () => { + const component = shallow(); + expect(component).toMatchSnapshot(); + }); + + it('updates activity when text is changed', () => { + const component = shallow(); + + component + .find('Connect(RichText)') + .filterWhere(n => n.props().content === 'other funding for FFY 1066') + .prop('onSync')('florp'); + expect(props.syncOtherFunding).toHaveBeenCalledWith(1, '1066', 'florp'); + }); + + it('maps dispatch actions to props', () => { + expect(mapDispatchToProps).toEqual({ + setOtherFunding: setCostAllocationFFPOtherFunding, + syncOtherFunding: setCostAllocationOtherFunding + }); + }); +}); diff --git a/web/src/containers/activity/__snapshots__/CostAllocate.test.js.snap b/web/src/containers/activity/CostAllocation/__snapshots__/CostAllocate.test.js.snap similarity index 55% rename from web/src/containers/activity/__snapshots__/CostAllocate.test.js.snap rename to web/src/containers/activity/CostAllocation/__snapshots__/CostAllocate.test.js.snap index 7d2e95e82b..b049b6bafb 100644 --- a/web/src/containers/activity/__snapshots__/CostAllocate.test.js.snap +++ b/web/src/containers/activity/CostAllocation/__snapshots__/CostAllocate.test.js.snap @@ -1,6 +1,6 @@ // Jest Snapshot v1, https://goo.gl/fbAQLP -exports[`the CostAllocate component renders correctly 1`] = ` +exports[` renders correctly 1`] = ` -
- - -
`; diff --git a/web/src/containers/activity/CostAllocation/__snapshots__/OtherFunding.test.js.snap b/web/src/containers/activity/CostAllocation/__snapshots__/OtherFunding.test.js.snap new file mode 100644 index 0000000000..879d3a1d72 --- /dev/null +++ b/web/src/containers/activity/CostAllocation/__snapshots__/OtherFunding.test.js.snap @@ -0,0 +1,223 @@ +// Jest Snapshot v1, https://goo.gl/fbAQLP + +exports[` renders correctly 1`] = ` + +

+ Other Funding +

+

+ + FFY + 1066 + +

+
+ + +
+
+ + +
+ + + + + + + + + + + + + + + + +
+ Activity Total Cost + + + 5459076 + +
+ Other Funding + + - + + + 4322 + +
+ Medicaid Share + + + 3450509 + +
+

+ + FFY + 1067 + +

+
+ + +
+
+ + +
+ + + + + + + + + + + + + + + + +
+ Activity Total Cost + + + 5459077 + +
+ Other Funding + + - + + + 4323 + +
+ Medicaid Share + + + 3450510 + +
+ +`; diff --git a/web/src/containers/activity/CostAllocation/index.js b/web/src/containers/activity/CostAllocation/index.js new file mode 100644 index 0000000000..cc9c76e68c --- /dev/null +++ b/web/src/containers/activity/CostAllocation/index.js @@ -0,0 +1,18 @@ +import PropTypes from 'prop-types'; +import React, { Fragment } from 'react'; + +import CostAllocate from './CostAllocate'; +import OtherFunding from './OtherFunding'; + +const CostAllocation = ({ activityIndex }) => ( + + + + +); + +CostAllocation.propTypes = { + activityIndex: PropTypes.number.isRequired +}; + +export default CostAllocation; diff --git a/web/src/containers/activity/__snapshots__/ActivityRoutes.test.js.snap b/web/src/containers/activity/__snapshots__/ActivityRoutes.test.js.snap index 7e7724d0ba..80a59d00ed 100644 --- a/web/src/containers/activity/__snapshots__/ActivityRoutes.test.js.snap +++ b/web/src/containers/activity/__snapshots__/ActivityRoutes.test.js.snap @@ -48,7 +48,7 @@ exports[` component renders as expected 1`] = ` id={null} resource={null} > - diff --git a/web/src/containers/activity/__snapshots__/CostAllocateFFP.test.js.snap b/web/src/containers/activity/__snapshots__/CostAllocateFFP.test.js.snap index ab76f8a2fb..4142fefe70 100644 --- a/web/src/containers/activity/__snapshots__/CostAllocateFFP.test.js.snap +++ b/web/src/containers/activity/__snapshots__/CostAllocateFFP.test.js.snap @@ -2,10 +2,17 @@ exports[`the CostAllocateFFP component renders correctly renders correctly in editable mode (standard) 1`] = ` +

+ Budget and FFP +

- Cost Allocation and Budget for FFY + Activity + 1 + Budget for FFY 1990

-
- - -
@@ -302,9 +287,11 @@ exports[`the CostAllocateFFP component renders correctly renders correctly in ed />

- Cost Allocation and Budget for FFY + Activity + 1 + Budget for FFY 1991

-
- - -
@@ -749,10 +714,17 @@ exports[`the CostAllocateFFP component renders correctly renders correctly in ed exports[`the CostAllocateFFP component renders correctly renders correctly in view-only mode 1`] = ` +

+ Budget and FFP +

- Cost Allocation and Budget for FFY + Activity + 1 + Budget for FFY 1990

- Cost Allocation and Budget for FFY + Activity + 1 + Budget for FFY 1991

!!value.match(/^[0-9]{4}$/); + const Activity = ({ activity, activityIndex }) => { const buildObjective = objective => { return ( @@ -267,19 +269,37 @@ const Activity = ({ activity, activityIndex }) => { __html: activity.costAllocationNarrative.methodology }} /> -

Description of Other Funding

-
+ +
+

Other Funding

+ + {Object.entries(activity.costAllocationNarrative) + .filter(([year, _]) => isYear(year)) // eslint-disable-line no-unused-vars + .map(([year, narrative]) => ( + +

FFY {year}

+

Other Funding Description

+
+
+ Other Funding Amount: + + {(activity.costAllocation[year.toString()] || { other: 0 }).other} + +
+
+ + ))}

Activity {activityIndex + 1} ({activity.name})
- Federal Financial Participation (FFP) and Cost Allocation + Budget and Federal Financial Participation (FFP)

- Include any participating non-Medicaid FTEs. methodology: instruction: - heading: Description of cost allocation methodology + heading: Description of Cost Allocation Methodology detail: >- Do not assume absence of other payers is sufficient cause for Medicaid to be primary payer. Limit ambiguity about other @@ -38,16 +37,6 @@ methodology: this section. ffp: title: Federal Financial Participation (FFP) and Cost Allocation - otherFundingInstruction: - heading: Other Funding Amount - detail: Enter the total amount that will be used from additional funding sources. - helpText: >- - Other funding consists of funds that are not directly tied to the CMS - grant and the matching state funds for this activity. This funding may - come from another federal source, another state agency, and/or - contributions or donations from a third party. Other funding will be - deducted from the total cost of the activity prior to calculating the - Medicaid share. federalStateSplitInstruction: heading: Federal-State Split detail: >- @@ -82,11 +71,3 @@ quarterly: state: In-House Costs contractor: Private Contractor Costs combined: Total Enhanced FFP -otherFunding: - instruction: - heading: Other funding description - detail: >- - Write a high level description of funding used to support this activity. - (Review Letter 10‐016 for examples of grants for inclusion.) - helpText: >- - Ensure new grants are included, and remove expired grants. diff --git a/web/src/i18n/locales/en/activities/index.js b/web/src/i18n/locales/en/activities/index.js index 0e9ef21185..d6b37a0a4b 100644 --- a/web/src/i18n/locales/en/activities/index.js +++ b/web/src/i18n/locales/en/activities/index.js @@ -4,6 +4,7 @@ import costAllocate from './costAllocate.yaml'; import expenses from './expenses.yaml'; import goals from './goals.yaml'; import milestones from './milestones.yaml'; +import otherFunding from './otherFunding.yaml'; import overview from './overview.yaml'; import schedule from './schedule.yaml'; import standardsAndConditions from './standardsAndConditions.yaml'; @@ -16,6 +17,7 @@ export default { expenses, goals, milestones, + otherFunding, overview, schedule, standardsAndConditions, diff --git a/web/src/i18n/locales/en/activities/otherFunding.yaml b/web/src/i18n/locales/en/activities/otherFunding.yaml new file mode 100644 index 0000000000..66d1e55bbf --- /dev/null +++ b/web/src/i18n/locales/en/activities/otherFunding.yaml @@ -0,0 +1,33 @@ +title: Other Funding +description: + instruction: + heading: Other Funding Description + detail: >- + Provide a high level description of funds that are not directly tied to + the HITECH Medicaid grant. This funding may come from another federal + source, another state agency, and/or donations or contributions from a + third party such as payer and provider subscription fees. If other funds + will be used to cover the State share tied to the HITECH Medicaid grant, + please include a justification for this here. (Review SMD Letter 10‐016 + for examples of grants for inclusion.) + helpText: '' +amount: + instruction: + heading: Other Funding Amount + detail: >- + Provide the total amount of funds not associated with the HITECH Medicaid + grant (i.e. any cost allocated funding from all parties) and the amount + from other funding that will will not be used for the State share of the + HITECH Medicaid grant. This amount will be deducted from the total cost of + the activity to calculate the total computable Medicaid share for this + activity. + helpText: >- + Example: For a $1,000,000 project that is 80% cost allocated to Medicaid + (related to 80% Medicaid transaction volume, for example) and 20% for all + other stakeholders, enter $200,000 (20% of $1,000,000). + + + Example: For a $1,000,000 project which receives a $100,000 grant (i.e. + other funding) prior to cost allocation and is cost allocated to Medicaid + at 80%, enter $280,000 ($100,000 [other funding] + $180,000 [20% of the + remaining $900,000]). diff --git a/web/src/reducers/nav.items.js b/web/src/reducers/nav.items.js index bd0c44dfc2..5bd40a70a0 100644 --- a/web/src/reducers/nav.items.js +++ b/web/src/reducers/nav.items.js @@ -122,11 +122,11 @@ const buildActivitySection = i => [ url: `/apd/activity/${i}/contractor-costs` }, { - label: 'Cost allocation', + label: 'Cost allocation and other funding', url: `/apd/activity/${i}/cost-allocation` }, { - label: 'FFP and budget', + label: 'Budget and FFP', url: `/apd/activity/${i}/ffp` } ]; diff --git a/web/src/styles/scss/activity.scss b/web/src/styles/scss/activity.scss index 09f31b4c1f..50f0904987 100644 --- a/web/src/styles/scss/activity.scss +++ b/web/src/styles/scss/activity.scss @@ -13,3 +13,16 @@ .entry-details--review div h4.ds-u-font-weight--bold { font-weight: 600 !important; } + +.heading-ffy { + width: 100%; + text-align: left; + border-bottom: 2px solid #000; + line-height: 0.1em; + margin: 10px 0 20px; +} + +.heading-ffy span { + background:#fff; + padding-right: 10px; +}