-
Notifications
You must be signed in to change notification settings - Fork 10
Contact info for external services
We use a number of public government websites and APIs to help build eRegulations. We can get in touch with their teams if their product is behaving in an unexpected way (not in accordance with their documentation), or if we have a question we can't figure out from their documentation.
The same team works on both of these sites. On eCFR.gov or FederalRegister.gov, click the "Site Feedback" button (at lower right) and fill out the form.
Note that when we previously contacted them about a data issue for an older FR document, they said: "The metadata we have for 1994-1999 is incomplete. We are currently only correcting data from 2000 to the present."
Most GovInfo developer products have public GitHub repositories where you can file an issue, linked from their Developer Hub page. For example, for the GovInfo Link Service, you can file an issue here.
If you find an error in a statute compilation file, the Statute Compilations help page includes an email address to contact.
The office that works on this site has contact information posted here, including an email address. The email address only accepts messages under 84kb, so set Gmail to plain text mode and avoid including attachments. Include your phone number, because they may call you to ask for clarification about your inquiry.
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