Notifications
Clear all
Topic starter
For some strange reason, it appears that the administereddate field in the new immunization table can be a date, but it may not be a properly formatted date mm/dd/yyyy. It can change based on what is in the administereddatetype field - which appears to allow for it to simply be a year (and maybe other options). Ugh.
So, while writing and testing a report to see patients in compliance with pneumovax, I keep getting random date field errors.
Has anyone figured out logic to take whatever may be stored in the date field, copy it to a variable while making sure what you write is a date?
Posted : June 29, 2017 6:11 am
I just checked on a CEMR 9.8 and 9.10 database and the field IMMUNIZATION.ADMINISTEREDDATE in the database is in fact a date. The data type of the actual field is a DATE so there would be no way to store anything other than a date or NULL.
The ADMINISTEREDDATETYPE field determines if the program should ignore the day or month of the immunization, but it still stores everything as a date.
Posted : June 29, 2017 7:19 am
