COI: Representing Mock Patient Data in HL7 Standards An example

Slides:



Advertisements
Similar presentations
September, 2005What IHE Delivers 1 CDA-based content integration profiles Philippe Lagouarde, Cegedim Co-chair Vendor, IHE-France.
Advertisements

Helmut König, Siemens Medical Solutions
HL7 Quality Reporting Document Architecture DSTU
Concern Tracking What is it and why??. Concern Tracking time Patient Symptoms Concern Problem Observation Chest Pain, severe Visit I already have observation.
HL7 Templates A means to Manage Complexity. Objectives What is an HL7 Template? What types of constraints can HL7 Templates define? What types of HL7.
Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
Query Health QRDA Requirements
Dogac, Kabak, YukselOASIS SET TC Working Document The Use of CCTS in HL7 CDA Asuman Dogac, Yildiray Kabak, Mustafa Yuksel METU, Ankara, Turkey.
A brief HL7 Version 3 Introduction for CIMI
HL7 V3 API What is happening behind the scenes…. Presentation Goals Familiarize developers and other interested parties with various concepts and classes.
Group C – HL7 France Objective : Definition of CDA implementation guides. 17 participants Public entities DHOS, GIP-CPS, GIP-GMSIH Primary care sector.
Use and Transformation of DICOM SR and CDA Release 2 Diagnostic Imaging Reports Helmut Koenig, MD Siemens Healthcare Co-Chairman DICOM WG20 and HL7 Imaging.
IHE Retrieve Form for Data Capture (RFD) Profile IHE Retrieve Form for Data Capture (RFD) Profile Presented at NCDR.11.
1 Web Data Management XML Schema. 2 In this lecture XML Schemas Elements v. Types Regular expressions Expressive power Resources W3C Draft:
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
Electronic Submission of Medical Documentation (esMD) Clinical Document Architecture R2 and C-CDA Comparison April 24, 2013.
Ekagra caDSR Forms Interchange Feasibility of using ODM & CDA Nov 13, 2008 Ashwin Mathur
QRDA Category I Ballot Development Spring Ballot QRDA Category I: Release 2 Ballot Development HL7 Structured Documents Sub Workgroup for Developing the.
XML Schemas Lecture 10, 07/10/02. Acknowledgements A great portion of this presentation has been borrowed from Roger Costello’s excellent presentation.
The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management Fall 2003 * Bob Boiko * MSIM Associate Chair XML Schemas.
Query Health Technical WG 8/2/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm Specification, RI and Pilot Updates2:05 – 2:20 pm Comparison between.
13 Dec. 2006CmpE 583 Fall 2006 OWL Lite- Property Char’s. 1 OWL Lite: Ch. 13- Property Characteristics Atilla ELÇİ.
Model-Driven Health Tools (MDHT) CDA Tools Overview
1 XML Schemas. 2 Useful Links Schema tutorial links:
Dr. Azeddine Chikh IS446: Internet Software Development.
December 15, 2011 Use of Semantic Adapter in caCIS Architecture.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
1 HL7: An Introduction for Ontologists Barry Smith
SQL Databases are a Moving Target Juan F. Sequeda – Syed Hamid Tirmizi –
OWL 2 in use. OWL 2 OWL 2 is a knowledge representation language, designed to formulate, exchange and reason with knowledge about a domain of interest.
© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 13 June 2013 Meeting #3 hData Record Format Taskforce 1 © 2012 The MITRE Corporation.
HL7 RIM June 2010 Entity class_cd : CS cd: CE determiner_cd : CS status_cd : CS id : II Role class_cd : CS cd: CE effective_time : IVL status_cd : CS id.
CDA Clinical Document Architecture Charlie Bishop.
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
Key Issues of Interoperability in eHealth Asuman Dogac, Marco Eichelberg, Tuncay Namli, Ozgur Kilic, Gokce B. Laleci IST RIDE Project.
Description of some multimedia ontologies Rapha ë l Troncy Thursday 1 st of December, 2005.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Introduction to HL7 Version 3 W. Ed Hammond February 25, 2008.
Applying the RIM/VMR to Elimination of the “{ }” Robert A. Jenders, MD, MS 14 January 2003.
DICOM SR / CDA Rel.2 Mapping San Antonio WGM, May 2006 Helmut König Co-Chair II SIG / DICOM WG20 Siemens Medical Solutions.
Practical RDF Chapter 12. Ontologies: RDF Business Models Shelley Powers, O’Reilly SNU IDB Lab. Taikyoung Kim.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
Query Health Technical WG 6/14/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm QRDA Discussion2:10 – 3:00 pm.
FHIR and ontology Barry Smith Charleston, September 24,
Title “syngo” and ”we speak syngo” are registered trademarks of Siemens AG. Relevant Patient Information Queries: Extending the.
NAACCR Clinical Data Work Group - Pilot to Transmit the Cancer Abstract Using HL7 Clinical Document Architecture (CDA) 2007 NAACCR Conference Ken Gerlach,
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
CITA 330 Section 2 DTD. Defining XML Dialects “Well-formedness” is the minimal requirement for an XML document; all XML parsers can check it Any useful.
Creating RDF Representations of Patient Data
RDF Representation using POMR of Patient 1
An HL7-CDA2 standard template for the ICF-based
Procedure Note (V3) ** = Required sections
Networking and Health Information Exchange
QRDA I STU R5 Updates Since pre-ballot content Review
Dansk HL7 CDA profil til deling af aftaler CDA struktur
Survey of Medical Informatics
HL7 CDA and DICOM SR Diagnostic Imaging Reports
Allergy discussion I want to throw something else into the mix - recording of allergies using 'Allergy to X' as a concept from the Clinical Findings hierarchy.
What’s Next? Why HL7 Messages and HL7 CDA Documents are in our Future
Networking and Health Information Exchange
Occupational Data for Health
LD/SW Modelling and Linking Guide modelling styles Michel Böhms
Harvard Medical School
RDF Representation using Detailed Clinical Models of Patient 1
Use and Transformation of DICOM SR and CDA Release 2 Diagnostic Imaging Reports Helmut Koenig, MD Siemens Healthcare Co-Chairman DICOM WG20 and HL7 Imaging.
RDF Representation using POMR of Patient 1
CDA R2.0 Vs Clinical Statement vs RIM Acts
Daniel A. Pollock, M.D. & Robert H. Dolin, M.D.
Continuity of Care Document
Evidence of Infection (Dialysis) Reporting in CDA and greenCDA:
Presentation transcript:

COI: Representing Mock Patient Data in HL7 Standards An example Helen Chen February 12, 2008

Expressing RIM V3 in OWL Top-Level Classes

ACT This class hierarchy is constructed according to ACT Type code definition

Entity, Participation, Role These class hierarchies are constructed according to respective type code too

RoleLink and ActRelationship As Properties

HL7 Vocabulary And Code

HL7 Data Type

HL7 CDA For Clinical Document CDA are used as schemas for recording clinical events in documents Header: Global-unique identifiers Document Type Code Timestamp Confidentiality Code Patient Author Custodian Body: XML Content (such as tables, lists, etc.) Non-XML Content (such as sounds, video clips, etc.)

Translation of XDS Schema To OWL Constructs XSD OWL Definition xs:schema|targetNamespace rdf:RDF|xml:base Define the namespace. xs:schema|xmlns rdf:RDF|xmlns Define the default namespace. xs:complexType|name owl:Class Defines the class. xs:complexType//element or xs:element|attribute owl:DatatypeProperty owl:ObjectProperty owl:Restriction rdf:OnProperty Defines the properties and restrictions of the class. xs:attribute owl:DatatypeProperty Defines the datatype properties. xs:element@type rdfs:range Defines the range of class. xs:maxOccurs xs:minOccurs owl:maxCardinality owl:minCardinality Defines the number of class’ relationships. Note: not alll xds constructs used in CDA schema can be translated In OWL constructs, such as “optional” and “include”

HL7 CDA For Clinical Document Element Name (rdf:Property) Cardinality (owl:Restriction) RIM Source (rdfs:domain) Data Type (rdfs:range) 1 ClinicalDocument 0..1 Document 2 typeId 1..1 InfrastructureRoot II 3 classCode Act CS 4 moodCode 5 Id 6 code CE 7 title ST 8 effectiveTime TS 9 confidentialityCode 10 languageCode 11 setId ContextStructure 12 versionNumber INT 13 copyTime 14 recordTarget 1..* SET<RecordTarget> 15 typeCode Participation 16 contextControlCode 17 patientRole PatientRole 18 Role 19 SET<II> 20 addr 0..* SET<AD>

COI Mock Up Patient Data in CDA Document -1 On 19 April, 54-year-old man with diabetes was referred to the Hypertension Clinic in Jichi Medical School Hospital with symptoms of dizziness and orthostatic intolerance CDA header - where you can find the document <ClinicalDocument xmlns="urn:hl7-org:v3" xmlns:mif="urn:hl7-org:v3/mif" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hl7-org:v3 CDA.xsd"> <typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040"/> <id extension = "c266" root="2.16.840.1.113883.3933"/> <code code="11488-4" codeSystem="2.16.840.1.113883.6.1" displayName=“ReferNote"/> <Hypertension Clinica in JiChi Medical School Hospital</title> <effectiveTime value=“200704"/> <confidentialityCode code="N" codeSystem="2.16.840.1.113883.5.25"/> <setId extension="BB35" root="2.16.840.1.113883.3.933"> <versionNumber value="2"/> <legalAuthenticator> <author> <custodian> ……..

COI Mock Up Patient Data-2 CDA section - where to find specific patient information: patient <recordTarget> <patientRole> <id extension="12345" root="2.16.840.1.113883.3.933"/> <patient> <name> <given>Henry</given> <family>Levin</family> <suffix>the 7th</suffix> </name> <administrativeGenderCode code="M" codeSystem="2.16.840.1.113883.5.1" /> <birthTime value="19540924"/> </patient> <providerOrganization> <id extension="M345" root="2.16.840.1.113883.3.933"/> </providerOrganization> </patientRole> </recordTarget> ……..

COI Mock Up Patient Data-3 CDA section - patient present medical condition: debetes <section> <code code=“1234-5" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"/> <title>Present Medical Condition</title> <text> Patient has <content ID=“d1">Diebetes</content> </text> <entry> <observation classCode="OBS" moodCode="EVN"> <code code=“1234567" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" displayName=“Diebetes"> <originalText> <reference value="#d1"/> </originalText> </code> <statusCode code="completed"/> </observation> </entry> </section>

COI Mock Up Patient Data-3 CDA section - patient past medical history: Hypertension <section> <code code=“1234-5" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"/> <title>Present Medical History</title> <text> There is a history of <content ID=“d2">Hypertension</content> </text> <entry> <observation classCode="OBS" moodCode="EVN"> <code code=“1234567" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" displayName=“Hypertension"> <originalText> <reference value="#d2"/> </originalText> </code> <statusCode code="completed"/> <activityTime time=“20050629” /> </observation> </entry> </section>