Remove DEA and NPI from PROVIDER table
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- databases
Research direction
Locate the PROVIDER table definitions and identify where the DEA and NPI columns are declared. Check any associated DDL or validation material before removing them, and confirm that the resulting PROVIDER schema no longer includes either column.
Written by the indexing model from the issue text.
Description
There is a suggestion to remove these columns from the PROVIDER table as they are not relevant to population-level observational research .
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 513
- Avg merge
- 8d 3h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OHDSI/CommonDataModel
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
OHDSI/CommonDataModel#802 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OHDSI/CommonDataModel#799 ·
-
fix: mark cohort_definition_id as primary key in cohort_definition table for v5.3 and v5.4Possibly taken @rtmalikian claimed this 137 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OHDSI/CommonDataModel#787 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OHDSI/CommonDataModel#784 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
OHDSI/CommonDataModel#823 ·
All issues in OHDSI/CommonDataModel
Similar issues
-
Remove: 21 SexturyOpenchannels:remove check:passed
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 4 days
-
[bug-bash] print maps a missing item's HTTP 404 to exit 1 instead of documented not-found exit 5Openbug bug-bash
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure/CosmosDBShell#279 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SACGF/variantgrid#2647 ·
Maintainers usually reply within 1 day
-
divergence lane:reliability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
read_messages: the first read after subscribe/psubscribe returns no messages even when some are waitingPossibly taken @matheussilvano claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day