Merge pull request #14 from DSACMS/sjp/provider_tables

Sjp/provider tables

Author: ftrotter-gov

CODE_OF_CONDUCT.md

@@ -2,7 +2,7 @@
 
 As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
 
-We are committed to making participation in this project a harassment-free experience for everyone, regardless of the level of experience, gender, gender identity, expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.
+We are committed to making participation in this project a harassment-free experience for everyone.
 
 Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
 
@@ -14,4 +14,4 @@ This Code of Conduct is adapted from the [Contributor Covenant](http://contribut
 
 ## Acknowledgements
 
-This CODE_OF_CONDUCT.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions.
+This CODE_OF_CONDUCT.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions.

COMMUNITY.md

@@ -1,23 +1,17 @@
 # COMMUNITY.md
 
-ndh is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
+NDH (soon to be renamed) is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
 
 ## Project Members
 
-<!-- TODO: Who are the points of contact in your project who are responsible/accountable for the project? This can often be an engineering or design manager or leader, who may or may not be the primary maintainers of the project.
-
-Roles to include, but not limited to: Project Owner, Technical Lead, Developers/Contributors, Community Manager, Security Team, Policy Advisor, Contracting Officer's Representative, Compliance Officer, Procurement Officer -->
 
 | Role   | Name    | Affiliation    |
 | :----- | :------ | :------------- |
 | Product Manager | Julie Sossamon | DSAC |
 | Technical Lead | Fred Trotter | DSAC |
 | Engineer | Sarah Popelka | DSAC |
 
-<!-- TODO: A CODEOWNERS.md file is available in .github to define individuals responsible for specific parts of the codebase. Provide a reference to this file if used:
-
 See [CODEOWNERS.md](.github/CODEOWNERS.md) for a list of those responsible for the code and documentation in this repository.
--->
 
 See [Community Guidelines](#NDH-open-source-community-guidelines) on principles and guidelines for participating in this open source project.
 
@@ -30,21 +24,17 @@ The members of ndh community are responsible for guiding its development, ensuri
 - @ftrotter-gov
 - @spopelka-dsac
 
-<!-- TODO: List the individuals who are the maintainers. What groups/domains are maintainers a part of? Does your project have domains/areas that are maintained by specific people? List @USERNAMES directly, or any @ALIASES for groups/teams. -->
-
 ### Approvers:
 
 - @ftrotter-gov
 - @spopelka-dsac
 
-<!-- TODO: Who are the project approvers? List out @USERNAMES where possible so they can be tagged in issues/PRs directly. -->
 
 ### Reviewers:
 
 - @ftrotter-gov
 - @spopeelka-dsac
 
-<!-- TODO: Who are the project reviewers? List out @USERNAMES where possible so they can be tagged in issues/PRs directly. -->
 
 | Roles      | Responsibilities                               | Requirements                                                                      | Defined by                                                |
 | ---------- | :--------------------------------------------- | :-------------------------------------------------------------------------------- | :-------------------------------------------------------- |
@@ -53,15 +43,10 @@ The members of ndh community are responsible for guiding its development, ensuri
 | approver   | approve accepting contributions                | highly experienced and active reviewer + contributor to a sub-project             | COMMUNITY file approver entry and GitHub Triage Team      |
 | maintainer | set direction and priorities for a sub-project | demonstrated responsibility and excellent technical judgement for the sub-project | COMMUNITY file owner entry and GitHub Org Admin Team      |
 
-<!-- TODO: If the repository's release process is outlined in CONTRIBUTING.md, provide a reference to it:
-
 See [CONTRIBUTING.md](CONTRIBUTING.md) for more details on the release process.
--->
 
 ## Contributors
 
-<!-- TODO: A list of CONTRIBUTORS is generated below using contributors.yml located in the workflows directory. In order to automatically update the COMMUNITY.md, you must enter a secret into your Secrets and Variables under Actions within your repository settings. The name of the secret must be PUSH_TO_PROTECTED_BRANCH and the value must be a Personal Access Token with specific permissions. Please follow [this link](https://github.com/CasperWA/push-protected?tab=readme-ov-file#notes-on-token-and-user-permissions) for more information. -->
-
 Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COUNT END-->
 
 <!-- readme: contributors -start -->
@@ -121,13 +106,14 @@ When participating in NDH open source community conversations and spaces, we ask
 
 - When joining a conversation for the first time, please introduce yourself by providing a brief intro that includes:
   - your related organization (if applicable)
-  - your pronouns
   - your superpower, and how you hope to use it for NDH
-- Embrace a culture of learning, and educate each other. We are all entering this conversation from different starting points and with different backgrounds. There are no dumb questions.
-- Take space and give space. We strive to create an equitable environment in which all are welcome and able to participate. We hope individuals feel comfortable voicing their opinions and providing contributions and will do our best to recognize and make space for individuals who may be struggling to find space here. Likewise, we expect individuals to recognize when they are taking up significant space and take a step back to allow room for others.
+- Embrace a culture of learning
+- Take space and give space. 
 <!-- TODO: Add if your repo has a community chat - Be present when joining synchronous conversations such as our community chat. Why be here if you're not going to _be here_? -->
 - Be respectful.
 - Default to positive. Assume others' contributions are legitimate and valuable and that they are made with good intention.
+- Embrace a culture of learning, and educate each other. We are all entering this conversation from different starting points and with different backgrounds. There are no dumb questions.
+- Take space and give space. We strive to create an environment in which all are welcome and able to participate. We hope individuals feel comfortable voicing their opinions and providing contributions and will do our best to recognize and make space for individuals who may be struggling to find space here. Likewise, we expect individuals to recognize when they are taking up significant space and take a step back to allow room for others.
 
 ### Acknowledgements
 

README.md

@@ -4,19 +4,18 @@ National Provider and Payer Directory at CMS
 
 ## About the Project
 
-**{project statement}**
+The soon to be renamed NDH project at CMS will implement a new Provider and Payer Directory service that will eventually grow to encompass (and probably replace) the functionality of NPPES.
 
-<!---
 ### Project Vision
-**{project vision}** -->
+Enable patient data to work for patients, by supporting interoperability by providing clean enumeration of U.S. healthcare entities, and a reliable map of how those entities connect. 
 
 <!--
 ### Project Mission
 **{project mission}** -->
 
-<!--
+
 ### Agency Mission
-TODO: Good to include since this is an agency-led project -->
+The Centers for Medicare and Medicaid Services (CMS) provides health coverage to more than 100 million people through Medicare, Medicaid, the Children’s Health Insurance Program, and the Health Insurance Marketplace. The CMS seeks to strengthen and modernize the Nation’s health care system, to provide access to high quality care and improved health at lower costs.
 
 <!--
 ### Team Mission
@@ -28,11 +27,8 @@ A list of core team members responsible for the code and documentation in this r
 
 ## Repository Structure
 
-<!-- TODO: Including the repository structure helps viewers quickly understand the project layout. Using the "tree -d" command can be a helpful way to generate this information, but, be sure to update it as the project evolves and changes over time. -->
-
-```plaintext
-.
-```
+This is a mega-repository that will contain multiple different sub-projects. Look in the [src](src) for a list of projects. You will find more information about each project in a ReadMe.md file within the respective directories. 
+We may eventually setup seperate repos for our project, but until we do a central merged github repo is a simpler way to coordinate our work. 
 
 
 **{list directories and descriptions}**

SECURITY.md

@@ -9,4 +9,4 @@ Review the HHS Disclosure Policy and websites in scope:
 
 This policy describes *what systems and types of research* are covered under this
 policy, *how to send* us vulnerability reports, and *how long* we ask security
-researchers to wait before publicly disclosing vulnerabilities.
+researchers to wait before publicly disclosing vulnerabilities.