Not sure what I would search for, so I'm just asking a question.
We have one client where the immunization dates are getting altered. We craft a good string for the MEL IMMUN_ADD function but then when we read it back via MEL IMMUN_GETLIST, the immunization date has been altered to the day before.
The system time on the client/server box looks good. Is there any configuration in Centricity that might affect how dates are processed? The client is in India, not sure geographically where the client/server machine is but it's date is east coast US and the date displayed in Centricity is east coast US.
Any thoughts of what I could look for?
Thanks,
Dennis
In your command, are you coding the AdministeredDate field, and the AdministeredDateType field? They are both recommended.
I remember seeing this awhile ago when testing the GE HTML immunization form that the form used the date and time based on your location. The details are fuzzy, but I do remember we opened a ticket with GE. It was at a previous company, so I can't get the information about the ticket but GE may know about a 'time issue' with immunizations and time zones?
I remember that I was in a different time zone than the servers (both DB and Citrix), and that is what was causing the issue. But it sounds like Server/Clients are set to the same time zone as the local workstations? It was somehow related that the immunizations get added with a time of Midnight so being an hour off moved the date.
Sorry not a huge help, but maybe can help point in the right direction...
mkherman -- time zone certainly is an area of suspicion for me since we're working with a client in India and this has worked fine for many US-based clients. But I'm not seeing anything that sets the time to their local time or that indicates they are in a different geographical location.
I was figuring the DB runs on the same machine but maybe not. That's a good clue.
joeg -- we are setting the date type field to a 'D' indicating day-level precision.
Thanks for your help!
Dennis