ECG archetypes

2007-03-11 Thread Sam Heard
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070311/a0adcd71/attachment.html
-- next part --
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical


terminology

2007-03-11 Thread Bert Verhees
 !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
 html
 head
   meta content=text/html;charset=ISO-8859-1 http-equiv=Content-Type
 /head
 body bgcolor=#ff text=#00
 Hi Bertbr
 br
 The CODE_PHRASE is the space for keeping the link from the
 DV_CODED_TEXT (or any other coded information) and the terminology from
 which it has arisen. The text of the DV_CODED_TEXT (inherited from
 DV_TEXT) is where you display what the terminology provides as text in
 that language for that code. These ihave/i to be in tune.br
 br
 If the user edits the textural display then the CODE_PHRASE can only be
 a TERM_MAPPING, as the code_string is no longer defining of the text.br
 br
 Ocean's terminology server (which provides access to LOINC and SNOMED
 with ICD_10 on the way) has a well developed service interface. Hugh
 Grady will provide documentation for this as it works with the Template
 Designer - it is based on CTS but has a different approach to meet the
 needs of archetypes. There is a CTS (Common Terminology Service)
 specification from HL7 - which is moving to version 2. Russel Hamm is
 the guru.br
 br
 I hope this helps, Sambr

Thanks, Sam, it sure gives some places to look at.
The only remaining problem will be that I will write a terminology-service
on my own, because I need it, and good or bad, but probably not in sync
with further developments on OpenEhr-specs.

But that is where we have versions for, isn't it? ;-)

I didn't know about CTS, I will look at the HL7-site to find more information


regards
Bert Verhees

___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical





ECG archetypes

2007-03-11 Thread Heath Frankel
David,
FYI, There are forthcoming recommendations on including binary data in XML
without using base-64.  I expect that these would be used when available in
implementation.
 
Heath


  _  

From: openehr-technical-boun...@openehr.org
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Sam Heard
Sent: Sunday, 11 March 2007 7:49 PM
To: dclunie at dclunie.com; For openEHR technical discussions
Subject: Re: ECG archetypes


Hi David

Absolutely not - what we need are readers that can make sense of data as a
blob and get these specified as suitable for use in an EHR. Do you recommend
any very good or very widely used specs which have readers that are publicly
available?

Cheers, Sam

David Clunie wrote: 

Hi



I hope you guys are not considering yet another standard for

the encoding of bulk ECG data (as opposed to referencing it

or wrap it as a blob).



ECG's are analogous to images from radiology; large amounts

of bulk data, highly specific meta-data of little or no interest

to non-image aware applications and well-standardized already

by DICOM.



Unfortunately, ECG device and distribution vendors have been

slower to adopt standards than the medical imaging device

vendors, and so there are a plethora of them, SCP-ECG,

DICOM waveforms, HL7 V2 waveforms, and the FDA HL7-CDISC XML

submission standard, not to mention just storing a picture

of the ECG in a PDF file (the IHE consensus solution).



These standards also address the annotation of the waveforms

and the conclusions drawn from them by the acquisition device,

and it is probably only the latter that would be relevant to

be extracted into the EHR.



David



PS. As to the wrapping versus referencing question for the bulk

binary data, I just got through sending a 1.4GB 2,600 slice

cardiac CT angiogram to a colleague, which I presume nobody

would be crazy enough to base-64 encode and embed in an XML

document, for example. The point being that wrapping things

is not a scalable solution.



Mie Faerch Jensen wrote:

  

Greetings all;



We are two graduate students from Aalborg University, Denmark, taking our 

master in Biomedical Engineering and Informatics. In this semester ?our 

finale, we are working with complex data interoperability to an Electronic 

Health Record (EHR). We are following the openEHR?s EHR architecture
standard, 

and therefore also working with archetypes. 

We have a few questions we would like you to help us deal with.



- What we are trying to investigate is how to represent a recorded
ECG-signal 

in an archetype, and therefore we are wondering what the status is on
dealing 

with ECG-signals as an archetype? So far we haven?t been able to locate an
ECG-

archetype, only the description of it as an observation-entry.



- We have described workflows and clinical information guidelines for the 

observation and clinical evaluation of an incoming ECG-signal, but we are a 

bit confused on how to map the clinical information guidelines to an 

archetype. Can anyone give us an example on how this mapping is done?





Best regards



Mie F?rch Nielsen og Louise Pape S?rensen 

Aalborg University, Denmark, 

Master in Biomedical Engineering and Informatics,

10th semester

Reply-email: 06gr956d at miba.auc.dk





-

This mail sent through IMP: http://horde.org/imp/



___

openEHR-technical mailing list

openEHR-technical at openehr.org

http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical







___

openEHR-technical mailing list

openEHR-technical at openehr.org

http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

  


-- 


Dr. Sam Heard
MBBS, FRACGP, MRCGP, DRCOG, FACHI


CEO and Clinical Director
Ocean Informatics Pty.  http://www.oceaninformatics.biz/ Ltd.
Adjunct Professor, Health Informatics, Central Queensland University
Senior Visiting Research Fellow, CHIME, University College London
Chair, Standards Australia, EHR Working Group (IT14-9-2)
Australia

Ph: +61 (0)4 1783 8808
Fx: +61(0)8 8948 0215
UK
 Ph: +44 (0)77 9871 0980
Fx: +44 (0)207 1174610 




-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070311/fa3e1f15/attachment.html
-- next part --
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical