-
Notifications
You must be signed in to change notification settings - Fork 10
Audiences
These are generalized archetypes based on our research with many CMCS staff members who have generously shared their time and expertise with our eRegulations team.
Titles may be: Healthcare Policy Analyst, Health Insurance Specialist, State Officer
- Needs: An onramp into conducting policy research, easier than eCFR or a printed CFR book
- Goals: Learn how to research Medicaid regulations effectively and accurately; understand the difference between statute and regulation; gain exposure to how subregulatory guidance influences policy and operations
- eRegulations goals: We want to provide a useful tool that Learners can easily use
Titles may be: same as Learner but with more experience
- Needs: A tool that enables fast regulation access, enhanced with related content and subregulatory guidance
- Goals: Help states and fellow CMCS staff apply policy consistently and accurately; develop guidance and briefing docs; analyze materials; review and process policy actions and/or other documents from states
- eRegulations goals: We want Researchers to use eRegulations, find it helpful, and give us feedback so we can strengthen the tool
Titles may be: Technical Director, Technical Lead, Branch Manager, State Lead, State Officer Team Lead, Senior Policy Advisor, experienced Health Insurance Specialist
- Needs: Continuing to do deep research and produce well-informed results using the tools and techniques they’ve built over their years of experience; supporting colleagues in their research
- Goals: Ensuring consistent and reliable understanding of Medicaid authority and interpretation of policy that supports Medicaid and CHIP program needs and improves health outcomes
- eRegulations goals: We want Knowledge Keepers to find eRegulations acceptable and to recommend it to Researchers and Learners; we need their feedback
Titles may be: Center Director, Group Director, Deputy Group Director, Division Director, Deputy Division Director, Special Assistant, Senior Advisor
- Needs: Be able to speak to regulations as needed within their management positions
- Goals: Provide good faith negotiation and technical assistance to states; improve processing time of policy actions; show that they are advancing program goals, Administration priorities, and Medicaid mission
- eRegulations goals: We want Decision Makers to find eRegulations useful and valuable for their staff; we do not expect Decision Makers to provide detailed feedback
- Needs: Look up regulations and subregulatory policy as required for their goals; need the process to be easy and straightforward, since their main job may not otherwise require a broad knowledge of regulations
- Goals: Accurately review policy within their area of specialization
- eRegulations goals: We want CMCS contractors to find eRegulations of value as they need it; we welcome feedback but do not expect it
For example: Policy Analysts, System Administrators, Program Directors, State Medicaid Directors, State Plan Amendment Coordinators, CFOs, Financial staff, Managed Care staff
For example: Area Agencies on Aging or other state agencies that partner on HCBS programs
For example: IT Developers
For example: Foundations & Nonprofits, Advocates, Journalists, Attorneys (especially Public Aid associations), Beneficiaries
See Fundamental needs and preferences and Medicaid and CHIP regulations user experience for research summaries.
Please note that all pages on this GitHub wiki are draft working documents, not complete or polished.
Our software team puts non-sensitive technical documentation on this wiki to help us maintain a shared understanding of our work, including what we've done and why. As an open source project, this documentation is public in case anything in here is helpful to other teams, including anyone who may be interested in reusing our code for other projects.
For context, see the HHS Open Source Software plan (2016) and CMS Technical Reference Architecture section about Open Source Software, including Business Rule BR-OSS-13: "CMS-Released OSS Code Must Include Documentation Accessible to the Open Source Community".
For CMS staff and contractors: internal documentation on Enterprise Confluence (requires login).
- Federal policy structured data options
- Regulations
- Resources
- Statute
- Citation formats
- Export data
- Site homepage
- Content authoring
- Search
- Timeline
- Not built
- 2021
- Reg content sources
- Default content view
- System last updated behavior
- Paragraph indenting
- Content authoring workflow
- Browser support
- Focus in left nav submenu
- Multiple content views
- Content review workflow
- Wayfinding while reading content
- Display of rules and NPRMs in sidebar
- Empty states for supplemental content
- 2022
- 2023
- 2024
- Medicaid and CHIP regulations user experience
- Initial pilot research outline
- Comparative analysis
- Statute research
- Usability study SOP
- 2021
- 2022
- 2023-2024: 🔒 Dovetail (requires login)
- 🔒 Overview (requires login)
- Authentication and authorization
- Frontend caching
- Validation checklist
- Search
- Security tools
- Tests and linting
- Archive