Offhand, if it's purely related to the ETL work and you never want to show it in the OpenMRS UI, I'd create a separate table. Then in the ETL scripts you could add a step to ensure that any patients without a row in that table get the table populated.
If you need to access it in "real OpenMRS" for some reason, you could try doing a person attribute with an editPrivilege that nobody has. But I guess that wouldn't stop people from seeing it. -Darius On Fri, May 11, 2012 at 9:24 AM, Andrew Kanter <[email protected]>wrote: > Folks, we are using the new Pentaho methods for creating a de-identified > data warehouse from multiple OpenMRS servers. One question that came up was > the need to date-shift all dates in a patient record during the export. > This requires saving a date shift factor (-15d to +15d) in the OpenMRS > database to be used repeatedly when exporting data. This information should > not be visible to the average user. Does it make sense to have a separate > table with the patient_id and date_shift_factor that does not appear in the > UI, or can it be appended to an existing patient table but not be > accessible such as a person_attribute would be? > > Thanks, > Andy > > *-------------------- > 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 > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
