Data Types

Sam, I think you have misunderstood me. Human beings love complex patterns, but computers hate them. Of course you must keep the richness of "the day before the big storm", but you should not try to put that sort of thing into a Julian date field. Let people do what they are good for and let us

Subject header for this list

> May I suggest that if this list can add a prefix to the > email's subject > line? eg. [OpenEHR-Tech] > > I am not sure about the rest of you, but this would > certainly make my life easier in sorting my incoming email. Eddy, All messages are FROM: "owner-openehr-technical at openehr.org" tha

Data Types

Thomas, You are correct - I meant fuzzy month, not year. I wish Duke were in a position to let you install. Ed - If you have any questions about using this list, please send a message to d.lloyd at openehr.org

Data Types

Time to weigh in on fuzzy dates. We have been using fuzzy dates at Duke and in TMR since the early 70s for just the reason Sam states. Often patients will know on;y the year, more frequently the month and year only but no date. We discover that partial data is much more useful than no data. So

The concept of contribution

Mike Mair wrote: >Dear Thomas > >>>I am still not convinced that it is an EHR structure that has to be >>> >shared > >>>for meaningful communication. Both aspects of interoperabiliy, functional >>>and semantic, can be served without sharing an EHR structure. >>> >>Ah but they cannot - if you can

Imprecise Dates/Times & other data was: Data Types

At 19:28 -0500 9/6/02, Tim Cook wrote: >[many very good points deleted for brevity] > >> > Envision being able to scan a medical record for all partial >dates. >> > Retrieve those dates along with some context of the >CONTRIBUTION. A >> > computer could do very little with that information in m

The concept of contribution

d at openehr.org > - If you have any questions about using this list, please send a message to d.lloyd at openehr.org -- next part -- An embedded and charset-unspecified text was scrubbed... Name: InterScan_Disclaimer.txt URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20020611/e337c44e/attachment.txt>

FW: The concept of contribution

-Original Message- From: Li, Henry Sent: Tuesday, 11 June 2002 9:10 To: 'Denis Nosworthy' Subject:RE: The concept of contribution Hi I am not a real techno but I understand and deeply interested in the discussion. I had this vision of a real good electronic health recor

The concept of contribution

Dear All There is no doubht that the solution will have a degree of complexity - just look at HL7 v3 which is aimed at messaging. I believe that the HL7 and CEN EHR approaches will align - and will include the level 3 CDA demands - though it will take some time and must arise through implementatio

The concept of contribution

Sam, I agree that a certain degree of convegence is desirable and inevitable and will evolve over time based on implementation experience, but what is the reference to smoke filled rooms about? Liora At 09:37 AM 6/11/02 +0930, Sam Heard wrote: >Dear All > >There is no doubht that the solution

The concept of contribution

Dear Thomas > >I am still not convinced that it is an EHR structure that has to be shared > >for meaningful communication. Both aspects of interoperabiliy, functional > >and semantic, can be served without sharing an EHR structure. > > > Ah but they cannot - if you can't write software which can