Hi Koray,

Thanks for the links.

The "HL7 CDA Personal Healthcare Monitoring Report Draft" is the standard to
which we are working. CKM now contains a CLUSTER.device archetype which is
compatible with the draft standard. Other aspects of the various device
readings will be handled within 'normal' CKM archetpye e.g. Heart
rate-Pulse, Blood pressure and Oximetry. There is also now a
CLUSTER.waveform archetype to hande this form pf device output.


Ian



Dr Ian McNicoll
office / fax  +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
ian at mcmi.co.uk

Clinical Analyst  Ocean Informatics openEHR Archetype Editorial Group
Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health Scotland



On 23 February 2010 21:16, Koray Atalag <k.atalag at auckland.ac.nz> wrote:

>  Hi Ian, I am pretty excited to hear what you are up to.
>
> We are currently running a rather large trial here in New Zealand around
> establishing an evidence base on the use of telemonitoring for chronic
> disease management. Obviously we will have large amounts of device data
> comprising mainly vital signs as well as basic medical information in the
> clinical backend. So we are looking at a pathway to do the clinical
> information requirements and modelling with openEHR and then transforming
> this into CCD. I have so far seen that this is indeed doable by means of
> deriving archetype specific transform and that the art of doing this is how
> we structure the template and leverage existing high quality archetypes.
>
>
>
> The answer to your question is: Yes I am volunteering!
>
>
>
> I have came across a few recent publications on the use of CDA/CCDD which
> you might find interesting:
>
> 1.
>
> Wolf K, Schirmer S, Marschollek M, Haux R. Representing Sensor Data Using
> the HL7 CDA Personal Healthcare Monitoring Report Draft. Stud Health Technol
> Inform 2009;150:480-484.
>
>
>
> 2.
>
> Spyropoulos B, Tzavaras A, Botsivaly M, Koutsourakis K. Ensuring the
> Continuity of Care of Cardiorespiratory Diseases at Home. Monitoring
> Equipment and Medical Data Exchange over Semantically Annotated Web Services
> [Internet]. Methods Inf Med 2010 Feb;49(2)[cited 2010 Feb 10 ] Available
> from: http://www.ncbi.nlm.nih.gov.ezproxy.auckland.ac.nz/pubmed/20135082
>
>
>
> I will soon put these and some other relevant stuff into the Zotero openEHR
> group: http://www.zotero.org/groups/openehr/items
>
>
>
>
>
> Cheers,
>
>
>
> -koray
>
>
>
> *From:* openehr-clinical-bounces at chime.ucl.ac.uk [mailto:
> openehr-clinical-bounces at chime.ucl.ac.uk] *On Behalf Of *Ian McNicoll
> *Sent:* Wednesday, 24 February 2010 3:12 a.m.
> *To:* For openEHR technical discussions; For openEHR clinical discussions
> *Subject:* Re: Template and Schema for the ASTM Continuity of Care Record
> (CCR) and HL7 CCD
>
>
>
> Hi Alberto/ Anton et al,
>
> The expression of CCD in openEHR is vitally important but I think  we want
> to be able to do this by creating CCD-aligned templates of the official
> openEHR (CKM) archetypes, wherever possible. In general the CKM archetypes,
> because of the 'maximal dataset' approach are supersets of CCD templates. We
> can then constrain down the CKM archetypes to match the CCD templates,
> adding the relevant term and termset bindings.
>
> We should definitely be doing this in a shared,international space and it
> seems to me that this would be a great opportunity to use the newly arrived
> CKM Template review facility to create and review a set of CCD templates at
> www.openehr.org/knowledge
>
> What we need is for people to look at the relevant CKM archetypes and try
> to identify any gaps or mis-alignments from a CCD perspective, and then
> either contribute to the formal reviews or simply add comments to the
> archetype. The top 10 CKM archetypes thatwe are currently working through
> are very similar in scope to the CCD templates.
>
> Doing things this way will greatly reduce the work overall and will result
> in a set of good quality CKM archetypes that are wholly CCD compatible. We
> can then start to add simple transforms that can convert native openEHR data
> into  valid CDA XML. I am currently involved in just such an example for
> importing CDA-based device data but is heavily based on CCD templates.
>
> Any volunteers for a CCD template team for CKM? I have copied this to the
> Clinical list as I think there will be some interest there as well.
>
> Ian
>
>
>
> Dr Ian McNicoll
> office / fax  +44(0)141 560 4657
> mobile +44 (0)775 209 7859
> skype ianmcnicoll
> ian.mcnicoll at oceaninformatics.com
> ian at mcmi.co.uk
>
> Clinical Analyst  Ocean Informatics openEHR Archetype Editorial Group
> Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health
> Scotland
>
>
>  On 23 February 2010 13:03, Alberto Moreno Conde <
> albertomorenoconde at gmail.com> wrote:
>
> Dear Anton,
>
> At the moment I am working dissertation about the archetype
> development process for the MS in Health Informatics in Trinity
> College, at the same time I am working in the University Hospitals
> Virgen del Rocio in Spain in a project that involves the a system
> implementation based in archetypes and HL7 CDA. I agree with you that
> our work is very related since I need map from CDA to Archetypes and
> HL7 CCD looks like the first step in my journey. I think that there
> are many people working doing similar things and a lot duplicated
> work. I hope also that the outcome of your project will help to foster
> the archetype widespread. Are your future developed archetypes going
> to be shared at the end of your project? In what point of development
> are you now?
>
> Kind Regards
>
> Alberto
>
> 2010/2/23 Anton Brass <anton.brass at helmholtz-muenchen.de>:
>
> > Dear Alberto Merona Conde,
> >
> > my name is Anton Brass and I'm working on a research project
> > (http://www.helmholtz-muenchen.de/en/bymedconnect/home/index.html) in
> > Germany about communication of health data between different health care
> > institutions based on the 13606. For this purpose we analyse the CCR and
> our
> > next step is to create (or adapt) an archetype (of course several
> > archetypes) that should represent it.
> >
> > May I ask what are you working on? Maybe we have some intersections in
> our
> > research work.
> >
> > Kind Regards
> >
> > Anton
> >
> > Alberto Moreno Conde schrieb:
> >
> > Dear all,
> >
> > In the openEHR Specifications Strategic Directions for 2008 there was
> > the creation of templates and schemas for the Continuity of Care
> > Record (CCR)  and HL7 CCD. In what stage is this project and where can
> > I find more information about?
> >
> >
> > Kind Regards
> >
> > Alberto
> > _______________________________________________
> > openEHR-technical mailing list
> > openEHR-technical at openehr.org
> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> >
> >
> >
> > --
> >
> > Anton Brass
> >
> > Institute for Biological and Medical Imaging - MEDIS
> > Phone: +49 89-3187-4181
> >
> > Helmholtz Zentrum M?nchen
> > German Research Center for Environmental Health (GmbH)
> > Ingolstaedter Landstr. 1
> > D-85764 Neuherberg, Germany
> > www.helmholtz-muenchen.de
> > Chairman of Supervisory Board: MinDir Dr. Peter Lange
> > Board of Directors: Prof. Dr. G?nther Wess and Dr. Nikolaus Blum
> > Registergericht: Register of Societies: Amtsgericht M?nchen HRB 6466
> >
> > _______________________________________________
> > openEHR-technical mailing list
> > openEHR-technical at openehr.org
> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
> >
> >
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100224/809cb289/attachment.html>

Reply via email to