Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

An HTML attachment was scrubbed... URL:

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

Hugh Grady wrote: >This thread seemed to start with the assumptions that firstly, a >DV_CODED_TEXT will inevitably be stored in XML and that, secondly, the >mapping to XML will be a very direct one, even up to the names of the >corresponding elements. Are either of these valid assumptions? Even i

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

ng managed. -Original Message- From: owner-openehr-techni...@openehr.org [mailto:owner-openehr-technical at openehr.org] On Behalf Of Thomas Beale Sent: Monday, 23 January 2006 3:45 PM To: openehr-technical at openehr.org Subject: Re: Proposed slightly radical change to CODE_PHRASE in Text

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

sorry I missed this one - didn't get the message in fact - something odd going on with this list Heath Frankel wrote: >Tom, >My only comments is related to the resulting XML schema. Any reason we >couldn't simplify the XML further to the following: > > > clinical finding >

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

...@openehr.org [mailto:owner-openehr-technical at openehr.org] On Behalf Of Thomas Beale Sent: Thursday, 19 January 2006 9:38 AM To: openehr-technical at openehr.org Subject: Re: Proposed slightly radical change to CODE_PHRASE in Text package in openEHR Hugh Grady wrote: >Hi Tom > >I p

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

Ed Dodds wrote: >Sorry for not knowing better but I'll ask anyway; why >not something like: > > > clinical finding > > terminology_id="SNOMED-CT">404684003 > > > > Hi Ed, this works in XML-schema only, but not in any other formalism. We also don't make any special use of

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

Hugh Grady wrote: >Hi Tom > >I prefer the original structure, mainly from a general dislike of aggregate >attributes (such as the new one combining the terminology and the code id). > > In general I agree with the sentiment; I would only say that coded terms are somewhat of an exception - or an

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

An HTML attachment was scrubbed... URL:

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

5 January 2006 2:19 PM >To: Openehr-Technical >Subject: Proposed slightly radical change to CODE_PHRASE in Text package in >openEHR > > >Dear all, > >we just came across a "feature" of the current openEHR Reference Model >which, in the light of current implementations

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

Sorry for not knowing better but I'll ask anyway; why not something like: clinical finding 404684003 Ed Dodds

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

: Proposed slightly radical change to CODE_PHRASE in Text package in openEHR Dear all, we just came across a "feature" of the current openEHR Reference Model which, in the light of current implementations (particularly XML), it seems would be good to alter slightly. The change has n

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

echnical > Subject: Proposed slightly radical change to CODE_PHRASE in > Text package in openEHR > > > Dear all, > > we just came across a "feature" of the current openEHR > Reference Model which, in the light of current > implementations (particularly XML

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

Dear all, we just came across a "feature" of the current openEHR Reference Model which, in the light of current implementations (particularly XML), it seems would be good to alter slightly. The change has no semantic effect, only affecting how data are persisted. We are too close to the Relea