This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
documentation:next_cdm:location_history [2016/10/14 15:56] gowtham_rao Changed based on new discussion |
documentation:next_cdm:location_history [2016/10/14 16:41] 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's location was for a given date-time. This maybe solved using a location_history table, which acts as a relational entity between Person and Location. | + | 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's location was for a given date-time. This maybe solved using a location_history table, which acts as a relational entity between Person and Location. |
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?** |