This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Patient allergies #679
Merged
Patient allergies #679
Conversation
This file contains 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
jkleinsc
approved these changes
Oct 20, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Addresses #234 .
Changes proposed in this pull request:
cc @HospitalRun/core-maintainers
Happy Hacktoberfest!
Taking an initial shot at this model. I assume it'll probably need changing. :) Not sure how many other allergy code types are out there or if you'd rather just pick a single system. Just did some initial googling around at allergy coding and found references to both of these.
I am assuming here that the data for these allergies would be seeded in the DB. Although, some UI for adding (or maybe importing?) new allergies is probably worth considering too?