I think this is sort of what we were expecting we could do to expose current states/properties of a patient to external systems. Like active lists, if we were able to use OBS to define patient attributes which then are updated by encounters, calculations, or data transactions, then these attributes could be part of an ATOM stream for monitoring systems... Oh, a patient just became pregnant.... better send an alert to the CHW to be sure to visit her, etc... -------------------- Andrew S. Kanter, MD MPH
Asst. Prof. of Clinical Biomedical Informatics and Clinical Epidemiology Columbia University Email: [email protected] Mobile: +1 (646) 469-2421 Office: +1 (212) 305-4842 Skype: akanter-ippnw Yahoo: andy_kanter >________________________________ > From: Joaquín Blaya <[email protected]> >To: [email protected] >Sent: Monday, May 14, 2012 12:15 PM >Subject: Re: [OPENMRS-IMPLEMENTERS] Is there a history of patient attributes >kept in OpenMRS > > >Thanks Ben and Burke, >The solution you mentioned of having the value be both a person attribute and >an observation sounds exactly like what I want to do. > > >My ideal implementation is that the user enters it as an observation, and the >latest observation is seen as a patient attribute. My only question is how do >I get a patient attribute to automatically show the latest obs for a specific >concept? > > >Thanks, > >Joaquín >___________________________________________________________________ >Gerente de Desarrollo, eHealth Systems >Research Fellow, Escuela de Medicina de Harvard >Moderador, GHDOnline.org > > > >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 >>>Research Fellow, Escuela de Medicina de Harvard >>>Moderador, GHDOnline.org >> >>________________________________ >> Click here to unsubscribe from OpenMRS Implementers' mailing list > >________________________________ > Click here to unsubscribe 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]
