1 / 13

Data models standards to define, exchange and archive data MedInfo 2013, Copenhagen

Data models standards to define, exchange and archive data MedInfo 2013, Copenhagen. HL7 CDA. CDA = Clinical Document Architecture Defined by HL7 Available at http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7 Version 1: November 2000

brock-sampson
Télécharger la présentation

Data models standards to define, exchange and archive data MedInfo 2013, Copenhagen

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data models standards to define, exchange and archive dataMedInfo 2013,Copenhagen

  2. HL7 CDA • CDA = Clinical Document Architecture • Defined by HL7 • Available at http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7 • Version 1: November 2000 • Current version 2: May 2005 (ISO standard „ISO/HL7 27932:2009“) • Specification of structure and semantics • XML based • Usage of HL7 RIM (Reference Implementation Model) data types • Purpose: exchange data between providers and patients

  3. Medical Data Models HL7 CDA - Structure • CDA-Header: Meta information • CDA-Body: Document itself • Level 1: textual information (discharge letters) • Level 2: separation and annotation of segments • Level 3: computable data (lab values)

  4. Archetypes • Mentioned by T. Beale 2002 • Core part of EN 13606 • Actively researched and published by D. Kalra [1] • Commonly known: openEHR archetypes • Definition in Archetype Definition Language (ADL) • Available at http://www.openehr.org • Purpose: Definition of small (10-50), domain specific unit • Re-usable, combinable • Based on reference model [1] Kalra D, Tapuria A, Austin T, De Moor G. Quality requirements for EHR archetypes. Stud Health Technol Inform. 2012;180:48–52.

  5. Archetypes • Commonly known: openEHR archetypes Figure 2: Blood Pressure, Big Model Figure 1: Blood Pressure, Unstructured Figure 3: Blood Pressure, Generic Model

  6. ODM • ODM = Operational Data Model • Defined by CDISC • Available at http://www.cdisc.org/odm • Version 1: October 2000 • Current version 1.3.1: 2010, only registered users • XML schema definition (ODM1-3-1.xsd and ODM1-3-1-foundation.xsd) • Purpose: clinical studies (Study events + patient data) • Study Events (Visit, Follow Up, …): CRFs • CRF = medical form + detailed definition • Principle: Definitions (“Def”) and References (“Ref”)

  7. ODM – important elements <FormDefOID="F.0000" Name=“Medical History" Repeating="No"> <Description> <TranslatedTextxml:lang="en"> Medical History </TranslatedText> <TranslatedTextxml:lang="de"> Anamnese </TranslatedText> </Description> <ItemGroupRefItemGroupOID="IG.0000" Mandatory="Yes" OrderNumber="1"/> […] </FormDef>

  8. ODM – important elements <FormDefOID="F.0000" Name=“Medical History" Repeating="No"> <Description> <TranslatedTextxml:lang="en"> Medical History </TranslatedText> <TranslatedTextxml:lang="de"> Anamnese </TranslatedText> </Description> <ItemGroupRefItemGroupOID="IG.0000" Mandatory="Yes" OrderNumber="1"/> […] </FormDef>

  9. ODM – important elements <FormDefOID="F.0000" Name=“Medical History" Repeating="No"> <Description> <TranslatedTextxml:lang="en"> Medical History </TranslatedText> <TranslatedTextxml:lang="de"> Anamnese </TranslatedText> </Description> <ItemGroupRefItemGroupOID="IG.0000" Mandatory="Yes" OrderNumber="1"/> […] </FormDef>

  10. ODM – important elements (2) <ItemGroupDefOID="IG.0000" Name=“Admin Dates" Repeating="No"> <ItemRefItemOID="I.0000" Mandatory="Yes" OrderNumber="1"/> <ItemRefItemOID="I.0001" Mandatory="Yes" OrderNumber="2"/> </ItemGroupDef> […]

  11. ODM – important elements (3) <ItemDefOID="I.0000" Name="Admission Date" DataType="date"> <Question> <TranslatedTextxml:lang="en">Admission date </TranslatedText> <TranslatedText xml:lang="de"> Aufnahmedatum </TranslatedText> </Question> <Alias Context="Code-1" Name="Date of admission"/> <Alias Context="UMLS CUI-1" Name="C1302393" /> <Alias Context="SNOMED CT-1" Name="399423000" /> <Alias Context="LOINC-1" Name="MTHU029790 " /> </ItemDef> […]

  12. ODM – important elements (3) <ItemDefOID="I.0000" Name="Admission Date" DataType="date"> <Question> <TranslatedTextxml:lang="en">Admission date </TranslatedText> <TranslatedText xml:lang="de"> Aufnahmedatum </TranslatedText> </Question> <Alias Context="Code-1" Name="Date of admission"/> <Alias Context="UMLS CUI-1" Name="C1302393" /> <Alias Context="SNOMED CT-1" Name="399423000" /> <Alias Context="LOINC-1" Name="MTHU029790 " /> </ItemDef> […]

  13. Contact Benjamin.Trinczek@uni-muenster.de Bernhard.Breil@uni-muenster.de dugas@uni-muenster.de Institute of Medical Informatics University Münster http://imi.uni-muenster.de

More Related