This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

TermInfo Project

From HL7Wiki
Revision as of 21:45, 27 August 2013 by Rhausam (talk | contribs) (→‎Agendas)
Jump to navigation Jump to search

TermInfo 2 – Meeting Information

Leader: Rob Hausam, MD

Date / Time(s): Call is scheduled to last 1 hour Bi-weekly on Wednesdays 09:00 AM (Eastern Time, GMT -04 DST)

Teleconference information: Phone: +1 770-657-9270 Participant Code: 644843

Web Meeting Info (GoToMeeting and call-in details):

https://www1.gotomeeting.com/join/912947024

Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Denmark: +45 (0) 69 91 89 33 Australia: +61 2 8355 1031 Austria: +43 (0) 7 2088 1033 Belgium: +32 (0) 28 08 4342 Canada: +1 (647) 497-9371 Finland: +358 (0) 942 41 5770 France: +33 (0) 182 880 159 Germany: +49 (0) 811 8899 6925 Ireland: +353 (0) 19 030 050 Italy: +39 0 693 38 75 50 Netherlands: +31 (0) 208 080 208 New Zealand: +64 (0) 9 925 0481 Norway: +47 21 54 82 21 Spain: +34 911 82 9890 Sweden: +46 (0) 852 500 179 Switzerland: +41 (0) 435 0167 65 United Kingdom: +44 (0) 207 151 1806 United States: +1 (213) 493-0619

Access Code: 912-947-024 Audio PIN: Shown after joining the meeting Meeting ID: 912-947-024

TermInfo 2 – Meeting Agendas and Minutes

Agendas

Minutes

Link to TermInfo Project minutes on www.hl7.org

TermInfo 2 – Implementation Guide for Using SNOMED CT and LOINC Terminologies in HL7 Information Models

The new and expanded project officially began at the January 2012 WGM in San Antonio. The intent is to develop material for DSTU followed by normative ballot to address issues of overlap between the terminology and information models.

TermInfo 2 Project Scope Statement: File:HL7 Project Scope Statement Vocab Terminfo R2 01-15-2012 final.doc

The links below are to the content from the previous DSTU standard (expired May 2009), which will serve as the starting point for our new work:

  • Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5

Hot Topics

  • How to represent negation
  • Considering changes in use of ASSERTION
  • Discuss use of nesting in Problem Concern and Allergy Concern Acts
  • Post-coordination
  • Reporting negative assertions, ie No Growth, No Problems, No Results
  • Use of NULL flavors
  • Canonical sentences: a mechanism to reveal semantic meaning of coded clinical statements
  • Terminology binding

Use Cases

(Each use case needs to be given a meaningful name, then linked out to a page for that use case.)

Presentations

{Presentations given to explain TermInfo 2 will be posted here.)

Principles

(A summary will be posted here of any Principles which form the basis upon which TermInfo 2 is built.)

TermInfo 1.5 DSTU - Update Project

This section of the wiki contains the content of the TermInfo, Release 1.5, broken into individual word documents. There is one document per secondary section of the TOC. These files will be used to facilitate updating of the material from version 1.5 of the TermInfo Implementation Guide (Initially named, Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5) . Updates will be based on ballot comment reconciliations from the 2009 Ballot and other currently relevant improvements.

Audience

File:Terminfo Audience section-draft-prior to scoping.docx

TABLE OF CONTENTS

1 Introduction and Scope

1.1 Purpose of the guide

1.2 Overview

1.3 Future Work

1.4 Scope

1.5 How to read this document

1.6 Documentation conventions

1.7 Background

1.8 Requirements and Criteria

1.9 Asserting Conformance to this Implementation Guide


2 Principles and Guidelines

2.1 SNOMED CT Vocabulary Domain Constraints

2.2 Overlap of RIM and SNOMED CT Semantics


3 Common Patterns

3.1 Introduction

3.2 Allergies and Adverse Reactions

3.3 Introduction

3.4 Introduction

3.5 Introduction

3.6 Introduction


4 Normal Forms


A Appendices

A1 References

A2 Revision Changes

A3 SNOMED CT Open Issues

A4 SNOMED CT Version & History Information

A5 Detailed Aspects of issues with a vocabulary specification formalism


Endnotes