Conference session on EHR Management and Preservation, Taiwan, Submission deadline: September 1, 2012
Dear All: Please help to circulate, many thanks! --Wo Call for Paper and Participation CODATA Conference Session on Electronic Health Record Management and Preservation (EHR-MP) October 28 - 31, 2012, Taipei, Taiwan The CODATA (Committee on Data, established since 1966), an interdisciplinary Scientific Committee of the International Council for Science (ICSU), which works to improve the quality, reliability, management and accessibility of data of importance to all fields of science and technology, is happy to host the conference sessions on Electronic Health Record on Management and Preservation at its 23rd Conference in Taipei, Taiwan, Oct. 28 ? 31, 2012. Please see http://ehrmp.nist.gov for details. Background The ability to apply standard and interoperable solutions to manage and preserve electronic health records (lab test results, CT scans, physician notes, pharmacies, long-term care, etc.) and migrate, distribute, replicate, and access these records from legacy formats and platforms to advanced standard formats and operating systems are vital for clinical care and medical research. However, management and systems interoperability for preservation, storage, and accessibility of such health data has not yet fully defined for electronic health records (EHRs). If management and preservation of clinical information are not addressed, valuable and irreplaceable information will become Inaccessible, or disappear over time with disastrous consequences for patient safety, care and research value. Replacing lost data even if possible, will entail huge costs for patients, clinicians, administrators, pharmacists, and potentially, the entire country?s economy. The conference session focuses on underlying models, methods, systems, and application areas, with a strong emphasis on clinical information modeling, system performance, and behavior (backward and forward compatibility). The list of topics of interest includes, but is not limited to: ? Clinical Knowledge Modeling ? Universal Representation for Clinical Information ? EHR Management, Archival, and Preservation ? EHR System Architecture and Workflow ? EHR Harmonization ? EHR Format Migration Strategy ? EHR DICOM and Multimedia Management ? EHR/PHR Mobile Application ? EHR Systems for Clinical Research ? EHR Security, and Access Control ? EHR Metadata and Ontologies ? EHR Semantic Interoperability ? EHR Query Language ? Web Services to EHR Repositories Paper Submission and Proceedings Publication Full-length papers between 4 and 6 A4 pages are solicited. Detailed submission instructions will be posted on the EHR-MP website in due time. Each submission will go through peer-review process. The conference proceedings potentially be published by the ACM International Conference Proceedings Series. Important Dates / Websites Abstract submission: September 1, 2012 Notification to authors: September 15, 2012 Paper submission: October 20, 2012 Camera ready papers: November 10, 2012 Conference dates: October 28 - 31, 2012 EHR-MP website: http://ehrmp.nist.gov CODATA website: http://www.codata2012.com General Chair Wo Chang, National Institute of Standards and Technology, USA Program Committee Dr. Kenneth Thibodeau, NIST, USA Dr. Shinji KOBAYASHI, MD, PhD, Ehime University, Japan Mr. Kenneth S Rubin, HP, USA Dr. Sadahiko Kano, Waseda University, Japan Mr. Gora Ditta, C2C, USA Dr. Rong Chen, MD, PhD, Health Informatics, Sweden Dr. Hiroyuki Yoshihara, MD, PhD, Kyoto University, Japan --Wo Chang Digital Data Preservation, Project Lead Digital Media Group, Manager Information Access Division (IAD) Information Technology Laboratory (ITL) National Institute of Standards and Technology (NIST) Email: wchang at nist.govmailto:wchang at nist.gov Phone: (301) 975-3439 -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120801/30b0278a/attachment-0001.html
Building software to convert HL7 v2/v3 messaging into archetypes templates
Dear All: thank you all for your reply to my question! Sorry I was out last week. Dear Health, Thank you for taking the time to explain your process getting the HL7 v2/v3 to archtypes templates! Would it possible for you to share your XSLT with us? Even better if you can share one or two instances of HL7 messages so that I can follow your instruction steps from your slides to see how the entire process works. BTW: if anyone knows of any public available test dataset on HL7 v2, v3, 13606, X12, etc. I'd very much appreciated for their URLs. Much thanks in advanced for your help! --Wo From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-boun...@openehr.org] On Behalf Of Heath Frankel Sent: Monday, February 06, 2012 5:35 AM To: 'For openEHR technical discussions' Subject: RE: Building software to convert HL7 v2/v3 messaging into archetypes templates Hi Wo, Not sure if anyone else has some tools for the Job, but my experience in doing this over the last 5 years is that there is no silver bullet for this task. The process is just like any integration mapping, however the commercial mapping tools that I have attempted to use and those I have attempted to build myself just don't give me the capability needed for the mapping complexity I require. One of the ley issues is support for abstract types. I would be very happy to know if others have found a better tool than those I have tried I write XSLT by hand to transform the input message (HL7 V2 needs to be converted to XML using an integration component such as Mirth) into a Template Data Document (TDD) as defined in my presentation. The TDD is validated against the Template Data Schema (TDS) generated from a Template defined in the Ocean Template Designer, which augments the document with fixed and default values in the schema. The validated TDD is then transformed using a TDD to openEHR composition transform that can be used for any template exported using the Ocean Template Designer. These transforms are applied within an integration service which also provides communication ports and message tracing. You could certainly skip the intermediate TDD step but we have found that using it provides a more concrete (domain) model of the message that you are transforming to and allows the use of standard XML schema validation tools to catch 95% of the structural errors without the need for specialised openEHR validation tools. Although as openEHR experts we benefit from this process, the advantages for those that are not is huge. The nice thing about using archetypes to define the schema of the target of a transform is that you only need to write the transform template per archetype once. Each message that uses the same input structure corresponding to this archetype can reuse the same transform. Unfortunately, the real world of integration is not so simple and different source systems, even different messages from the same source system may be different, but you still have a good starting point to tweak the transform to support the variation between implementations. I hope this helps. Regards Heath From: openehr-technical-bounces at openehr.orgmailto:openehr-technical-bounces at openehr.org [mailto:openehr-technical-bounces at openehr.org]mailto:[mailto:openehr-technical-boun...@openehr.org] On Behalf Of Chang, Wo L. Sent: Saturday, 4 February 2012 8:07 AM To: openehr-technical at openehr.orgmailto:openehr-technical at openehr.org Subject: Building software to convert HL7 v2/v3 messaging into archetypes templates Dear All, I hope this is the right reflector First of all, thanks to those who developed tools, prepared tutorials, etc.!! I have spending the last few days playing around with the followings: * Java Reference Implementation of openEHR * LiU-Archtype-Editor-0.5.2 * Archtype Editor 2.2.779 * ADL 1.5 Workbench beta * Template Designer 2.6.1213.3 * Etc. Along with reading very good tutorials on: * Intro to openEHR, Sam Heard * Knowledge-enabled approach to eHealth records, Heather Leslie * Using Archtypes with HL7 Messages and Clinical Documents, Health Frankel * EN 13606-2 Gello - DCM, Andrew McIntyre * Etc. And openEHR stable specifications on: * Introducing openEHR * Architecture Overview * Etc. And ISO 13606 Part-1 and Part-2. I truly believe the archtype/template would be the right approach for my project on long-term management and preservation of EHRs. The Java ref. implementation libraries, Archtype Editor, Template Designer are great utils/tools. My basic question is: are there any public tools available to allow me to covert HL7 v2/v3 messaging to/from archtypes/templates as described in Health Frankel's tutorial on Using Archtypes with HL7 Messages and Clinical Documents? I know there is deep learning curve and would very much
Building software to convert HL7 v2/v3 messaging into archetypes templates
Dear David, Thanks for the LinkEHR link especially you have a free version for testing. I think this is sort of tool that I am looking for to transform HL7, EN13606, X12, etc. into archtypes. There seems to be a number of LinkEHR video clips available on YouTube, that's great! Thanks! --Wo From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-boun...@openehr.org] On Behalf Of David Moner Sent: Thursday, February 09, 2012 1:23 PM To: For openEHR technical discussions Subject: Re: Building software to convert HL7 v2/v3 messaging into archetypes templates Hello, Here at the Technical University of Valencia, we have been developing LinkEHR (www.linkehr.comhttp://www.linkehr.com) for the last six years and it seems to be exactly what you are looking for. LinkEHR Studio has two main functionalities: - It is a generic archetype editor, able of working with any reference model you import into it. We have worked with archetypes for openEHR, EN13606, HL7 CDA, CDISC ODM, MML and many others. - It is a data transformation tool based on archetypes. You can use an archetype and map it to a data source, defining the appropriate transformation functions and rules. Then the tools automatically generates an XQuery to transform existing XML data instances into XML extracts that follow the archetype and reference model rules. Although we have not worked directly with HL7 v2.x messages, it should be possible to work with them in their XML representation version. You just have to choose or define an archetype as target schema, import the HL7 XML message schema as source, and define the correspondences between those two. We have generated CDA documents based on this methodology, so v2.X messages should be even easier to manage. Contact us if you have any question. Best regards, David 2012/2/3 Chang, Wo L. wchang at nist.govmailto:wchang at nist.gov Dear All, I hope this is the right reflector First of all, thanks to those who developed tools, prepared tutorials, etc.!! I have spending the last few days playing around with the followings: * Java Reference Implementation of openEHR * LiU-Archtype-Editor-0.5.2 * Archtype Editor 2.2.779 * ADL 1.5 Workbench beta * Template Designer 2.6.1213.3 * Etc. Along with reading very good tutorials on: * Intro to openEHR, Sam Heard * Knowledge-enabled approach to eHealth records, Heather Leslie * Using Archtypes with HL7 Messages and Clinical Documents, Health Frankel * EN 13606-2 Gello - DCM, Andrew McIntyre * Etc. And openEHR stable specifications on: * Introducing openEHR * Architecture Overview * Etc. And ISO 13606 Part-1 and Part-2. I truly believe the archtype/template would be the right approach for my project on long-term management and preservation of EHRs. The Java ref. implementation libraries, Archtype Editor, Template Designer are great utils/tools. My basic question is: are there any public tools available to allow me to covert HL7 v2/v3 messaging to/from archtypes/templates as described in Health Frankel's tutorial on Using Archtypes with HL7 Messages and Clinical Documents? I know there is deep learning curve and would very much appreciated for any pointers. Thanks in advance for any help! --Wo ___ openEHR-technical mailing list openEHR-technical at openehr.orgmailto:openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- David Moner Cano Grupo de Inform?tica Biom?dica - IBIME Instituto ITACA http://www.ibime.upv.es Universidad Polit?cnica de Valencia (UPV) Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta Valencia - 46022 (Espa?a) -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120213/e224e6e1/attachment.html
Building software to convert HL7 v2/v3 messaging into archetypes templates
Dear Paulo, That's great that you have your prototype working for the conversion! If any detail notes and/or codes that you can share, I'd be interested and much thanks in advance for your help. Best, --Wo From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-boun...@openehr.org] On Behalf Of Paulo Ferreira Sent: Thursday, February 09, 2012 12:13 PM To: openehr-technical at openehr.org Subject: RE: Building software to convert HL7 v2/v3 messaging into archetypes templates Hello all, I'm working on my thesis project, which one of the components is EHRstorage in a openEHR repository. Since the input is HL7v2.x messages there isthe necessity of openEHR conversion. I think Heath remembers me, because Heath andChunlan helps me with this issue. I was capable to assemble a small prototypethat includes Mirth, which invokes a Java implementation environment to performthe conversion. The clinical data that that is present in an Unsolicited ObservationResult (ORU^R01) for instance, it's successfully converted, but withoutdemographic data, neither a patient identification instance. Can you give someclue about this topic? Best Regards, Paulo Ferreira. -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120213/88628f08/attachment.html
Building software to convert HL7 v2/v3 messaging into archetypes templates
Dear All, I hope this is the right reflector First of all, thanks to those who developed tools, prepared tutorials, etc.!! I have spending the last few days playing around with the followings: * Java Reference Implementation of openEHR * LiU-Archtype-Editor-0.5.2 * Archtype Editor 2.2.779 * ADL 1.5 Workbench beta * Template Designer 2.6.1213.3 * Etc. Along with reading very good tutorials on: * Intro to openEHR, Sam Heard * Knowledge-enabled approach to eHealth records, Heather Leslie * Using Archtypes with HL7 Messages and Clinical Documents, Health Frankel * EN 13606-2 Gello - DCM, Andrew McIntyre * Etc. And openEHR stable specifications on: * Introducing openEHR * Architecture Overview * Etc. And ISO 13606 Part-1 and Part-2. I truly believe the archtype/template would be the right approach for my project on long-term management and preservation of EHRs. The Java ref. implementation libraries, Archtype Editor, Template Designer are great utils/tools. My basic question is: are there any public tools available to allow me to covert HL7 v2/v3 messaging to/from archtypes/templates as described in Health Frankel's tutorial on Using Archtypes with HL7 Messages and Clinical Documents? I know there is deep learning curve and would very much appreciated for any pointers. Thanks in advance for any help! --Wo -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120203/ea70639b/attachment.html
13606 revisited - list proposal
Dear Thomas, Wonderful and much appreciated for setting the special reflector for it, thanks! Can you kindly provide the link how to join the new reflector? Thanks! --Wo -Original Message- From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-boun...@openehr.org] On Behalf Of Thomas Beale Sent: Wednesday, December 14, 2011 7:49 PM To: Openehr-Technical Subject: 13606 revisited - list proposal At the CIMI meeting last week and elsewhere, I have noticed a lot of interest in the ISO 13606 2012 revision, specifically in a) whether the openEHR and 13606 reference models can be brought together for part 1 of the revision and b) in finalising ADL/AOM 1.5 for providing a new snapshot to ISO for part 2. It seems to me that it would be useful to have a dedicated place to discuss this, so I would like to propose a new mailing list, 13606-alignment at openehr.org Does this seem like a useful idea? - thomas beale ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
