Burke is right that it should be treated as a column. However, person attributes are never deleted/changed. They are voided and recreated like obs. So if you wanted to see the history you could do a query against the person_attribute. We don't expose this in the API or UI anywhere that I know of.
I don't remember how the design for the new general attributes turned out to know if going forward when more objects have attributes like this it will have the same hidden feature. Ben On Sun, May 13, 2012 at 12:37 PM, Burke Mamlin <[email protected]>wrote: > OpenMRS Attributes (like person attributes) are designed to allow > implementations to extend tables to meet their needs – i.e., to effectively > add an a column to the person table. Based on this design, an attribute > should behave as like any other column on the table (gender, birthdate, > etc.). This means that a history of values or multiple values would not be > supported for simple datatypes; rather, you would need a custom datatype. > > If you want to keep longitudinal data (a history of values), then I would > suggest using observations. These don't have to be mutually exclusive – > i.e., you can, for example, record civil status both as a person attribute > *and* and an observation, where the current civil status is always > available as a person attribute and, when you want to see the history, you > can search observations. > > Cheers, > > -Burke > > > On Sat, May 12, 2012 at 6:34 PM, Joaquín Blaya < > [email protected]> wrote: > >> Hi, >> I was wondering if there was a history kept of patient attributes >> changes. I looked at the page >> https://wiki.openmrs.org/display/docs/Best+Practices+for+Implementations and >> it mentions that some patient attributes such as civil status can change >> over time and an implementer could want to keep a record of that, but it >> doesn't confirm if a record is maintained or not. >> >> It mentions "Is it better to record civil status as a person attribute >> with concept answers" is there anywhere that shows how to do this? Darius >> mentioned that the tribe module allowed you to have a coded patient >> attribute, is that what is done? >> >> Thanks, >> >> >> Joaquín >> ___________________________________________________________________ >> Gerente de Desarrollo, eHealth Systems <http://www.ehs.cl/> >> Research Fellow, Escuela de Medicina de Harvard <http://hms.harvard.edu/> >> Moderador, GHDOnline.org <http://www.ghdonline.org/> >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list > _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
