documentation:next_cdm:location_history
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:next_cdm:location_history [2016/10/14 15:56] – Changed based on new discussion gowtham_rao | documentation:next_cdm:location_history [2016/10/14 18:15] (current) – [Table] gowtham_rao | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| === Proposal === | === Proposal === | ||
| - | The location_id in the Person table is only capable of storing a single location address for an individual. We want to be able to know where a person' | + | The location_id in the Person table is only capable of storing a single location address for an individual. We want to know where a person' |
| There are several things to consider here: | There are several things to consider here: | ||
| Line 27: | Line 27: | ||
| It was agreed that the location_id in person table would represent the current location of the person. | It was agreed that the location_id in person table would represent the current location of the person. | ||
| - | It was discussed that location_history may need to be generalized to include device, care site, provider etc. | + | It was discussed that location_history may need to be generalized to include device, care site, provider etc. **How do we do that?** |
| + | |||
| + | |||
| + | |||
| + | | **location_history_id** | ||
| + | | res1 | person | ||
| + | | res2 | provider | ||
| + | | res3 | care_site | ||
| + | | res4 | person | ||
documentation/next_cdm/location_history.1476460613.txt.gz · Last modified: by gowtham_rao
