Reading the specs at 22.214.171.124. Partial Date/Times:
“If not even the year is known, then the date is obviously extremely approximate and it would probably be unsafe to represent it computationally. However, if computatable representation was needed in this case, a date interval can be used. A pedantic example which breaks these rules is someone who claims to be born on “a Monday at the start of May in 1934” (i.e. day but not date unknown). Either the clinician determines what date the first Monday in May 1934 actually was and record that (assuming the patient’s way of accurately remembering just happens to be via day rather than date), or else records a partial date of the form “May 1934” (in ISO 8601 form,
"1934-05") if they determine that the patient really is unsure.”
I would like to be able to record an approximate date that is more exact than a partial date (eg month and year) but annotate that it is not precise. And definitely not wanting to record an interval - definitely not wanting to record ‘2020-08-01 - 2020-08-05’.
What I’d like to be able to record is “~2020-08-03” in the same way as DV_QUANTIFIED’s
"~" magnitude_status. It is closer to real-life recording in many situations. Any age or duration derived from it would be more accurate, even if qualified by a similar ‘~’, than an age or duration calculated or derived from a partial date.
There conceivably may be similar use cases for use of ‘<’ or ‘>’ as in ‘earlier than/before’ or ‘later than/after’ a specified date as well although I don’t have a specific use case at present. Clearly these can’t be used to drive decision support, but only in the same way as an interval or a partial date have significant limitations.