Our current solution to this situation, as I mentioned in another post was to add the following routines to the PARTIAL_DATE type: probable_date: DATE possible_dates:INTERVAL<DATE>
If the user GUI was then constructed so that a blank date, and a blank month were allowed, the software behind would create a PARTIAL_DATE object. These functions would provide sensible values for statistical computation (i.e. 15th of the month if date unknown, 1st/June if date and month unknown). The possible_dates function provides the outer limits of the possible values of the date, which can be used for query matching. I am not sure of how much skew this introduces, but it has to be better than having falsely accuracte dates, or else no structured date at all. Paul, what do you think of this approach? - thomas beale - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
