Location history detail view (you might not want to merge yet) #1274
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
fredkingham
force-pushed
the
location-history-detail-view
branch
from
a709d44 to
b9a0b72
Compare
…hs rather than roll our own width classes
…are/elcid-rfh into location-history-detail-view
…e max end date as this is sometimes sporadically in the future
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
103 as is has not link to patient id in the transfer history, there is a PR to merge that will add this in. After this is merged change the transfer history lookup in api.py to use patient id rather than mrn.
I think we may want to rename some of the columns