Use of translationCode and Combination Code Proposal

Slides:



Advertisements
Similar presentations
RSNA Reporting Templates: Representation of Findings in CDA R2 Instances Helmut Koenig Co-Chair DICOM WG20.
Advertisements

C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
Tumour Matching N.Ireland Experience Colin Fox (IT Manager) Richard Middleton (Data Manager)
CIMI Modelling Taskforce Progress Report
Archetypes in HL7 2.x Snomed-CT “Computable Medical Records” Andrew McIntyre Medical-Objects NEHTA Snomed-CT Workshop.
Implementing a Clinical Terminology David Crook Subset Development Project Manager SNOMED in Structured electronic Records Programme NHS Connecting for.
Terminology in Health Care and Public Health Settings
NHIN Direct Project Communications Work Group Messages for Physicians August 24, 2010.
Public Health Data Element Standardization - A Framework for Modeling Data Elements Used for Public Health Case Reporting Case Reporting Standardization.
CIMI + FHIR Grahame Grieve 10-August 2015 Salt Lake City.
Quality Improvements Based on Detailed and Precise Terminology EFMI on Iceland June 2010 Kirsten Bredegaard, Senior Manager Connected Digital Health in.
(Business) Process Centric Exchanges
Distributed Java Programming Distributed Java Programming Class #2 August 22, 2002.
Correlating Knowledge Using NLP: Relationships between the concepts of blood cancers, stem cell transplantation, and biomarkers Katy Zou and Weizhong Zhu.
Mandatory Payload = MU2 Consolidated CDA. Qualifier: "leniency" (allowance for null or alternative codes) should be allowed in the following areas of structured.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
Electronic Submission of Medical Documentation (esMD) electronic Determination of Coverage (eDoC) PMD Discrete Data Definition October 30, 2013.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
SNOMED mapping for Pan-Canadian Surgery Templates Elaine Maloney January 27, 2015 ITHSDO Implementation SIG.
SNOMED CT Family of Languages Dr Linda Bird, IHTSDO Implementation Specialist.
Electronic CAP Cancer Checklists and Cancer Registries – A Pilot Project 2009 NAACCR Conference Ken Gerlach, MPH, CTR Castine Verrill, MS, CTR CDC-National.
Oncology in SNOMED CT NCI Workshop The Role of Ontology in Big Cancer Data Session 3: Cancer big data and the Ontology of Disease Bethesda, Maryland May.
Developments in The Netherlands focussed on the IHTSDO Workbench Jos Baptist, senior advisor standardisation processes IHTSDO, Stockholm, October, 2012.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
SNOMED CT and Genomics Mike Bainbridge Clinical lead, AsiaPac Peter Hendler Clinical lead, Americas.
Laura Bright, LJB Consulting, Inc. Gila Pyke, Cognaissance, Inc.
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
SNOMED CT and Surgical Pathology
Functional EHR Systems
Public Health Data Standards Consortium
FHIRForms – Viewing and Editing FHIR Data
Contemporary Engineering Economics
11th HL7 Australia Conference, 13th December 2006
Event-driven accounting information systems
Combination Codes Discussion.
UDI Key Features: Medical Device Integration
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
Achieving Semantic Interoperability of Cancer Registries
SNOMED CT and Surgical Pathology
Chapter 9 Bank Master Records
What is Useful? Publishing Support for Precision Medicine
ICD 11 FC and SNOMED CT – finding as Ontologies of Clinical Situations
The Needs for Coding and Classification Systems
CDA Document ‘Executive’ Summary Section
IHE DEC and Continua WAN Interface Proposals for Remote Monitoring
Functional status and activities of daily living concepts
Chapter 1 - An Introduction to Computers and Problem Solving
Efficient Remediation of Terms Inactivated by Dictionary Updates
Mapping Special Interest Group SNOMED IHTSDO
Protocols and Layering
ICD-10 and Clinical Documentation
Research on FHIR Fast Healthcare Interoperability Resources
Somerset Cancer Register
Electronic Health Record
Terminology and HL7 Dr Colin Price
سرطان الثدي Breast Cancer
Functional EHR Systems
IMO as Clinical Foundation Terminology in your MEDITECH System
Integrated Health System Planning
Face2Gene- DPDL integration
Electronic Health Record Access Control 7
Syndromic Surveillance and EHR Incentive Programs
Clinical Element Models
Topic 1: Be able to combine functions and determine the resulting function. Topic 2: Be able to find the product of functions and determine the resulting.
Portfolio project Reflection
The Importance of April 16, 2003: Where You Should be in HIPAA Data Code Sets/Transactions Testing and Compliance Presented by: Steven S. Lazarus, PhD,
Simple Yet Sophisticated Healthcare Solutions
Do not use a calculator for the following!!.
Extending OMOP CDM to Support Observational Cancer Research
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

Use of translationCode and Combination Code Proposal Discussion

Discussion Points TranslationCode “Combination” Codes Observation/value cardinality

Translation Codes - Desire Some Vendors/Implementers want a simple way to: Reliably send in more granular coded information in CDA That correlates with the way clinicians document problems That doesn’t require extensive (and unlikely) post-coordination

Translation Codes - Problem CDA R2 does not allow for the notion of “equivalence” in translationCode (side note: FHIR has this notion*) *http://hl7.org/fhir/2016Sep/conceptmap.html *http://hl7.org/fhir/2016Sep/conceptmap-definitions.html#ConceptMap.group.element.target.equivalence *http://hl7.org/fhir/2016Sep/valueset-concept-map-equivalence.html

Current Use of TranslationCode in CDA (equivalent only)

Proposed informal loosening of translationCode “same-as” Best available SNOMED CT code is in observation/value OriginalText may capture the text the clinician captured in the EHRs UI In TranslationCode trading partners could use custom (interface) terminology code OR their local system code/identifier that represents the code for the originalText the clinician captured This code could be more specific than the best available standardized code but it reflects clinical intent of the clinician This allows machine computability of more specific term local term in a simple manner Will communicate more complete information about the patient

Proposed informal loosening of translationCode “same-as” example

Problem – Multiple codes for single concept Many EHRs have the capability to map multiple codes to a single concept Some EHRs have the capability to map related codes (not “same-as”) How to easily send? *http://hl7.org/fhir/2016Sep/conceptmap.html *http://hl7.org/fhir/2016Sep/conceptmap-definitions.html#ConceptMap.group.element.target.equivalence *http://hl7.org/fhir/2016Sep/valueset-concept-map-equivalence.html

Combinatorial Codes – Problem – Text example Local Term: Breast Cancer, stage 1, estrogen receptor positive SNOMED-CT 254837009 Malignant tumor of breast 416053008 Estrogen receptor positive tumor ICD-10-CM C50.912 Malignant neoplasm of unspecified site of left female breast Z17.0 Estrogen receptor positive status [ER+]

Combinatorial Codes - Problem Common practice when more than one translationCode exists Some vendors may parse only to first one found Therefore: *http://hl7.org/fhir/2016Sep/conceptmap.html *http://hl7.org/fhir/2016Sep/conceptmap-definitions.html#ConceptMap.group.element.target.equivalence *http://hl7.org/fhir/2016Sep/valueset-concept-map-equivalence.html

Combinatorial Codes – Proposal (Problem Example) If the EHR is able to associate multiple related codes the combined effect would be equal or nearly equal to the local term Codes would be represented in translation and qualifier/value Will need a new or find best available code for translation/translation/@code

Combinatorial Codes – Proposal Example SUMM Summarized by: An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period. http://www.hl7.org/v3ballotarchive_temp_08B0CDD4-1C23-BA17-0C1CF9B11A2BB964/v3ballot/html/infrastructure/vocabulary/ActRelationshipType.html

Observation/value Cardinality In base CDA observation/value is 1…* In C-CDA observation/value is restricted to 1…1 Could this be considered an errata/enhancment? Could be a solution for the previous issue (combination/multiple related not same-as codes) could be solved Are there rules for what the relationship/type of codes allowed in observation/value in an observation