-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to populate drug_exposure.quantity when the dose form of the drug is liquid #139
Comments
PLEASE COPY THIS TEMPLATE INTO ASSIGNED ISSUE Issue # and locationThemis Format as follows: Issue summaryQuantity is represented in several different formats which all depends on the form of the drug. For drugs in the form of liquids it may be unclear how to store quantity. Convention typeField CDM tableDrug Exposure CDM fieldQuantity Links to issue discussionLinks to location of discussion on forums, CDM GitHub, Themis GitHub, etc. Format as follows: Provenance of dataThis applies to all data. Different types of sources will have drug information. The ratified conventionTo find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is ‘Has dose form’.If the drug is a liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table (typically stored as some measure of volume e.g. milliliters etc). If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. Date of ratification/publishedApril 17, 2024 Downstream implicationsNo Link to DQD checkNo Format as follows: Related conventions/further information#Tags |
Moving all "quantity" convention issues to Needs More Work column for further review of wording. |
How to populate drug_exposure.quantity when the dose form of the drug is liquid
CDM or THEMIS convention?
Themis
Table or Field level?
Field
Is this a general convention?
No
Summary of issues
Summary of answer
Related links
The text was updated successfully, but these errors were encountered: