Gprelations change

mdsupport wrote on Tuesday, July 14, 2015:

There is persistent requirement to track relationships between issues - e.g.

1 : Head Injury (Medical Problem)
2 : Memory Loss (Medical Problem)
3 : Weight Gain (Medical Problem)
4 : Surgery #1 (Surgery)
5 : Surgery #2 (Surgery)

We plan to use gprelations to link issue id (1) to issue ids (2,3,4,5). However in current schema there is no way to retain the sequence as specified by clinician. Our approach is to add a ‘seq’ column to capture order in which ‘entity 2’ entries are to be represented for ‘entity 1’.

Has anyone handled this type of requirement another way?

On a related note - we will probably need to capture encounter - issues sequence as well. Any thoughts on gprelations vs issue_encounter?