-
Notifications
You must be signed in to change notification settings - Fork 10
Initial pilot research outline
From October 2020
- How can eRegulations be useful to CMCS people who work with regulations?
- What tools do they use right now?
- How did they learn those tools?
- What's missing - what would they find helpful?
We'd like to talk to both people who have a lot of experience and people who may still be learning and improving their knowledge about interpreting regulations and subregulatory guidance, to help us identify how eRegulations may support them.
- Our Product Owners have a few notes and stories from people they talked to while preparing for this project
- Policy and domain SME on our team!
- Regulations SME who works with T-MSIS, MACPRO, and other systems
- A person from DSG
- A person from a CMCS policy group, because they likely have a different perspective and may use different tools or have different needs
- A contractor who contributes to this work for any group, because they may also have a different perspective than the employees do, such as different access to tools or different training
- A person who works closely with states who are implementing CMS guidance, such as Medicaid Enterprise Systems State Officers
- A person who interprets regulations and subregulatory guidance as part of their everyday job, such as an analyst who reviews State Plan Amendments (SPAs), including reviewing Requests for Additional Information (RAIs)
- A person in OGC who interprets regulations as part of their job
- A State staff member who works with regulations as part of their job, such as drafting SPAs or overseeing managed care plans
- A person who works in an advocacy group, such as National Association of Medicaid Directors, who may comment on or otherwise engage with regulations
- A person in a provider group or managed care organization who needs to comply with regulations
- A person who works for a State contractor on an IT system that needs to implement regulations, such as a product manager who works on an eligibility system for a state
- A person at MACPAC who uses regulations as part of writing oversight reports and helpful explainers
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