A CLI bundled with an electron front-end that provides data-linkage and AI deduplication for reported ACO data at scale.
deduplifhir_v1_demo_final.mov
As part of the Affordable Care Act, and attempts to reduce costs/utilization/expenditures, ACOS were created; Accountable care organizations.
Currently, ACO health metrics are self-reported and can result in duplicate records. DedupliFHIR is a tool that leverages existing open source AI data linkage libraries to help improve the quality of reported health data. This tool’s initial release targets the FHIR data format for ACO reported eCQM metrics. Future releases are planning to support QRDA formats, as well as generic .csv and other text formats.
This project originated from the CMS Open Source Community as a resource ACOs can use when preparing their patient records submission.
The DedupliFHIR project does not include or share any Personally Identifiable Information or Personal Health Information (PII/PHI) in this source code repository. All training and testing data we ship in the source code repository is ‘synthetic’ data, which is artificially generated. The tool itself uses only local data, uploaded by users on their own systems. The tool processes that data locally, and does not share that information over the network. Users control who that data is shared with after processing, and how it is shared, if at all.
You'll need poetry installed (see installation instructions).
make install
To test your installation run:
make test
To run the cli (for now) use the command:
poetry run python cli/ecqm-dedupe.py <command> [--fmt] [<args>]
To run the desktop app, run the commands in the frontend directory:
npm install
npm start
- Are measures just instructions and patient bundles contain actual information?
- If so, should run everything on patient bundle
- Should we pre-generate weights rather than training?
An up-to-date list of core team members can be found in MAINTAINERS.md. At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles.
- CONTRIBUTING.md
- MAINTAINERS.md
- CODEOWNERS.md
- GOVERNANCE.md
- COMMUNITY_GUIDELINES.md
- CODE_OF_CONDUCT.md
- SECURITY.md
- LICENSE
- SUPPORT.md
.
├── .github
│ └── workflows - Directory containing GitHub Actions workflows for automating CI/CD processes.
├── cli - Command line tool for data linkage and deduplication of ACO patient data.
│ └── deduplifhirLib
├── frontend - Native desktop app frontend built using Electron.
└── profile - Information about the Digital Service at CMS team.
The following guide is for members of the project team who have access to the repository as well as code contributors. The main difference between internal and external contributions is that externabl contributors will need to fork the project and will not be able to merge their own pull requests. For more information on contribributing, see: CONTRIBUTING.md.
Each application has its own linting and testing guidelines. Lint and code tests are run on each commit, so linters and tests should be run locally before committing.
We follow the GitHub Flow Workflow
- Fork the project
- Check out the
mainbranch - Create a feature branch
- Write code and tests for your change
- From your branch, make a pull request against
devif you have a feature change andmainif it is a hotfix - Work with repo maintainers to get your change reviewed and resolve git history if needed
- Wait for your change to be pulled into
devand later released intomain - Delete your feature branch
Thank you for considering contributing to an Open Source project of the US Government! For more information about our contribution guidelines, see CONTRIBUTING.md.
Those responsible for the code and documentation in this repository can be found in CODEOWNERS.md.
The DeDupliFHIR team is taking a community-first and open source approach to the product development of this tool. We believe government software should be made in the open and be built and licensed such that anyone can download the code, run it themselves without paying money to third parties or using proprietary software, and use it as they will.
We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets.
Principles and guidelines for participating in our open source community are can be found in COMMUNITY_GUIDELINES.md. Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events.
If you have ideas for how we can improve or add to our capacity building efforts and methods for welcoming people into our community, please let us know at mailto:opensource@cms.hhs.gov. If you would like to comment on the tool itself, please let us know by filing an issue on our GitHub repository.
We adhere to the CMS Open Source Policy. If you have any questions, just shoot us an email.
Submit a vulnerability: Vulnerability reports can be submitted through Bugcrowd. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.
For more information about our Security, Vulnerability, and Responsible Disclosure Policies, see SECURITY.md.
A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
In the spirit of Executive Order 14028 - Improving the Nation’s Cyber Security, a SBOM for this repository is provided here: https://github.com/DSACMS/dedupliFHIR/network/dependencies.
For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.
This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication as indicated in our LICENSE.
All contributions to this project will be released under the CC0 dedication. By submitting a pull request or issue, you are agreeing to comply with this waiver of copyright interest.