[Design Issue] Create Closing Notes and Error Messages for Alt Considerations and Risks and Conditions for Enhanced Funding

[akuas]

The designs are done for these pages with the MES expansion, but we need closing notes, annotations, and error message designs for them as they transition to dev work

This task is done when…

• [ ] any acceptance criteria (not process oriented, requirements of feature)
• [x] designs are created, taking into consideration validation, multiple FFY, multiple entries, long entries, weird entries, and/or the export view if applicable
• [x] 508 visual, content, and UX considerations and/or recommendations are reviewed
• [x] designs are shared
• [ ] designs are approved by product
• [ ] if there is a long discussion, a summary of changes for dev will be added to the last comment before transfer
• [ ] a list of changes to be made if this is improving an existing feature

---

Add additional labels (design, dev, compliance, BUG, etc) and size before submitting.

If the issue is needed to complete prioritized work for the CURRENT SPRINT, add it to the "This Sprint" pipeline. Otherwise, all other issues will be automatically added to the unprioritized pipeline for prioritization in backlog refinement or sprint planning with Product.

[akuas]

Analysis of Alternatives and Risks Closing Notes

As of 3.14.2023

1. These are all new fields for MMIS.
2. Validation:

   This page is completely optional. This should allow users to enter in new substantive info if need be and keep it blank if any of these planning questions have not been reassessed. So, there will be no error messages and it will not show up on the admin check.

3. The field titles are all title case in this situation because they are proper nouns.

[akuas]

Conditions for Enhanced Funding Closing Notes

As of 3.14.2023

1. Business Logic:

a. This page is connected to Budget and FFP because they both deal with match rate but the validation is not conditionally linked to each other. This means what you select on the Conditions for Enhanced Funding page will not limit or expand how many ffp options you have. b. The Enhanced Funding Qualification is always required. If left blank and you run the admin check, the error message will be "Select an enhanced funding qualification." c. If you select yes to the Enhanced Funding Qualification, the Enhanced Funding Justification will expand. The Enhanced Funding Justification is only required if you select yes. d. If you select no, you have answered all the required fields for that page. e. 90/10 DDI, 75/25 DDI and M&O are enhanced funding. 50/50 M&O is not enhanced funding and is used largely for miscellenous costs i.e. postage. When a project becomes certified, it becomes enhanced funding again.

Enhanced Funding Justification

The rich text editor allows users to pick and choose which standards and conditions apply to their project.

Standard and Conditions Help Drawer Copy

An Excerpt 42 CFR 433.112 and Additional Conditions for Enhanced Funding (1) CMS determines the system is likely to provide more efficient, economical. and effective adminstation of the State plan. (2) The system meets the system requirements, standards and conditions, and performance standards in Part 11 of the State Medicaid Manual, as periodically amended. (3) The system is compatible with the claims processing and information retrieval used in the administration of Medicare for prompt eligibility verification and for processing claims for persons eligible for both programs. (4) The system supports the data requirements of quality improvement organizations established under Part B of title XI of the Act. (5) The State owns any software that is designed, developed, installed or improved with 90 percent FFP. (6) The Department has a royalty free, non-exclusive. and irrevocable license to reproduce, publish, or otherwise use and authorize others to use, for Federal Government purposes, software, modifications to software, and documentation that is designed, developed, installed or enhanced with 90 percent FFP. (7) The costs of the system are determined in accdordance with the 45 CFR 75, subpart E. (8) The Medicaid agency agrees in writing to use the system for the period of time specified in the advance planning document approved by CMS or for any shorter period of time that CMS determines justifies the Federal funds invested. (9) The agency agrees in writing that the information in the system will be safeguarded in accordance with subpart F, part 431 of this subchapter. (10) Use a modular, flexible approach to systems development, including the use of open interfaces and exposed application programming interfaces; the separation of business rules from core programming, available in both human and machine readable formats. (11) Align to, and advance increasingly, in MITA maturity for business, architecture, and data. (12) The agency ensures alignment with, and incorporation of, industry standards adopted by the Office of the National Coordinator for Health IT in accordance with 45 CFR part 170, subpart B: The HIPAA privacy, security and transaction standards; accessibility standards established under section 508 of the Rehabilitation Act, or standards that provide greater accessibility for individuals with disabilities, and compliance with Federal civil rights laws; standards adopted by the Secretary under section 1104 of the Affordable Care Act; and standards and protocols adopted by the Secretary under section 1561 of the Affordable Care Act. (13) Promote sharing, leverage, and reuse of Medicaid technologies and systems within and among States. (14) Support accurate and timely processing and adjudications/eligibility determinations and effective communications with providers, beneficiaries, and the public. (15) Produce transaction data, reports, and performance information that would contribute to program evaluation, continuous improvement in business operations, and transparency and accountability. (16) The system supports seamless coordination and integration with the Marketplace, the Federal Data Services Hub, and allows interoperability with health information exchanges, public health agencies, human services programs, and community organizations providing outreach and enrollment assistance services as applicable. (17) For E&E systems, the State must have delivered acceptable MAGI-based system functionality, demonstrated by performance testing and results based on critical success factors, with limited mitigations and workarounds. (18) The State must submit plans that contain strategies for reducing the operational consequences of failure to meet applicable requirements for all major milestones and functionality. (19) The agency, in writing through the APD, must identify key state personnel by name, type and time commitment assigned to each project. (20) Systems and modules developed, installed or improved with 90 percent match must include documentation of components and procedures such that the systems could be operated by a variety of contractors or other users. (21) For software systems and modules developed, installed or improved with 90 percent match, the State must consider strategies to minimize the costs and difficulty of operating the software on alternate hardware or operating systems. (22) Other conditions for compliance with existing statutory and regulatory requirements, issued through formal guidance procedures, determined by the Secretary to be necessary to update and ensure proper implementation of those existing requirements.

Standards and Conditions Design

The help drawer will have an abridged version of the standards and conditions, present so that users can refer to them. They can click on the link below to open the actual regulation in a new tab. Im not sure if the admin check has this but I put a visual indicator that you can scroll through this help drawer.

Links

Standards and Conditions Help: Review 42. CFR 433.112 documentation opens up the same link below in a new tab Enhanced Funding Justification:42 CFR 433.112.: opens up https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-C/part-433/subpart-C/section-433.112 in a new tab

Error Messages

Enhanced Funding Qualification: Select an enhanced funding qualification. Enhanced Funding Justification: Provide an enhanced funding justification.

[akuas]

@jeromeleecms Can you please post the links for the standards and conditions help and the 42 cfr 433.112?

[akuas]

@thetif Above are the closing notes and I created a validation design for the conditions for enhanced funding. Let me know if there are any questions :).

[jeromeleecms]

@akuas Are you referring to: https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-C/part-433/subpart-C/section-433.112?

[akuas]

@jeromeleecms Thanks, I think so. Do you remember if we were using the same link for both the help drawer and the enhanced funding justification.

[thetif]

@akuas could we put the nested section between yes and no? We can do it the other way, but the Design System component is set up to open whatever directly under the checkbox and it's done like that is most of the other places in the system.

[akuas]

@thetif Good callout. Just updated the design to nest Enhanced Funding Justification under the yes option.

[thetif]

created dev tickets #4612, #4613

[jeromeleecms]

This looks fine, pending final design review. If the help drawer concept is hard to implement/time consuming, we can just open the link to the eCFR like we've done in the past with other reg references.

[SGilliamA1M]

@jeromeleecms the design specs look good.

[thetif]

I created a help drawer, but it comes out of the side of the screen and not right under the link. I was going to let Akua and Sherry let me know if that was ok.

[SGilliamA1M]

@thetif - the help drawer coming out from the right side of the screen looks great and it shares a similar treatment that we're using for the Admin Check.

[jeromeleecms]

This is good to close!