This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous 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 18:15] (current) gowtham_rao [Table] |
||
---|---|---|---|
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?** |
+ | |||
+ | |||
+ | |||
+ | | **location_history_id** | **entity_domain_id** | **entity_id** | **location_id** | **start_date** | **start_time** | **end_date** | **end_time** | | ||
+ | | res1 | person | person_id_1 | location1 | May 1985 | 24:00 | - | - | | ||
+ | | res2 | provider | provider_id_1 | location1 | May 1985 | - | - | - | | ||
+ | | res3 | care_site | care_site_id_1 | location2 | July 2011 | - | June 2012 | - | | ||
+ | | res4 | person | person_id_2 | location3 | July 2012 | 14:55 | August 2012 | 21:00 | | ||