Data Types

Tim I think this is true but from a date point of view we can only know the year if the month is unknown - if it is one or two then the person will have to guess and store it as a fuzzy date. I think this is the only sensible approach. We can record in text the time issues that have been

TBD_10

This was meant to be a data type for the physical location of something - an Xray film, specimen etc. I agree that this should be an archetype. Cheers, Sam -Original Message- From: owner-openehr-technical at openehr.org [mailto:owner-openehr-technical at openehr.org]On Behalf Of

data types - QUANTIFIED.accuracy

so in other words: represent and store as a % but allow input and display as DV_QUANTITY or %? Hm... this might need an extra flag if the DV_QUANTIFIED object is to remember whether it was originally in % or quantity form. Extra flag (attribute) good point. DV_QUANTIFIED.is_quantity

Imprecise Dates/Times other data was: Data Types

record and think that the two dates were probably the same, and that it was therefore the same fracture. I would guess that this is a real contrived long shot, and probably unrealistic, but we need some more evidence from clinicians... *** CAUTION *** This turned into a rambling about