Core Data Model - NPPES PUF Output Discovery #236
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
module-name: Core Data Model - NPPES PUF Output Discovery
Jira Ticket #262
Problem
We need to ensure that out core data model supports the entities, data elements, and relationships of the outputs that we are expected to produce. Those outputs are the NPPES PUFs and the R4b FHIR JSON standard.
Solution
This draft PR introduces a Jupyter notebook detailing the process to analyze the NPPES PUF files and break them into more normalized entities and data elements, as well as to understand the relationships between individuals/organizations and those entities.
Result
The result of the notebook is an Excel spreadsheet with two sheets:
Test Plan
N.B. Since this is discovery work, I don't think this PR should be merged into the code base, but it provides context for the process that was used to generate the NPPES Data Elements Excel Workbook (which I'll upload to Google Drive somewhere). This output may also inform the mapping of the core data model to the NPPES PUF output, a process that will eventually be incorporated into the code base.