Rename package and add EHRData workflow support#1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rename the package from ˋehrapy-drug-screeningˋ / ˋehrapy_drug_screeningˋ to drugscreenpyˋ and align repository metadata, documentation links, imports, tests, and release configuration with the new independent package name.
Add first-class ˋehrdata. EHRDataˋ workflow support while preserving the existing pandas DataFrame APIs. Drug-screening input tables can now be stored in ˋedata.uns["drugscreenpy"]["tables"]ˋ, patient/cohort metadata is read from edata.obsˋ, and screening results/intermediate tables are written back to ‘edata.uns["drugscreenpy"]ˋ. This allows users to chain workflows through EHRData objects while the implementation continues to use DataFrames internally.
Also updates the drug-screening documentation and API docs with an EHRDatafirst workflow, OMOP-derived EHRData guidance, and tests covering EHRData parity for substance-level, cohort-level, grouped-therapy, prescriptionpreparation, and exposure-window workflows.