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

Difference between revisions of "Value Set Definition Standard Project"

From HL7Wiki
Jump to navigation Jump to search
Line 44: Line 44:
 
  ''Remember US ET has returned to Daylight Savings Time, so EDT is -4 UTC''
 
  ''Remember US ET has returned to Daylight Savings Time, so EDT is -4 UTC''
  
===Upcoming Agenda for July 21, 2015 ===
+
===Upcoming Agenda for Aug 4, 2015 ===
 
# Agenda:
 
# Agenda:
 
## Confirm modeling diagram changes (clarifications and name changes) done 7/21 and put new diagrams into diocument.
 
## Confirm modeling diagram changes (clarifications and name changes) done 7/21 and put new diagrams into diocument.

Revision as of 22:34, 21 July 2015

A New Normative Standard for Value Set Definitions

Overview

DSTU ballot has officially PASSED but we have many comments to resolve. Please attend the weekly meeting to help

[From the PSS] Describe the elements that make up a “Value Set Definition”, and ballot this as a normative HL7 specification, including a demonstration of how this is met in FHIR profiles and HL7 Model Interchange Format (MIF).

The definition of value sets is a required activity in completing the specification of most health information technology artefacts. To date, the approach for doing so has not been consistent within HL7 constructs and elsewhere. Many of the required elements and approaches are embedded in existing HL7 artefacts but not consistently. Currently, an explicit list of all the fields in an HL7 value set definition are surfaced only in the informative balloted MIF, with a general description of them in the normative Core Principles specification. A more accessible and standardized list of these fields is required to facilitate interoperability and sharing of value set definitions across HL7 artefacts and the Health IT community at large.

Success criteria: Publishing of the normative standard, and a demonstration of value set definitions that conform to this published normative specification.

Project Processes

This project is using DropBox as a collaborative document sharing process during the formative draft development process. If you are interested in viewing the current draft please attend the meetings. If you are interested in participating in the editing and review of the drafts, please send a request to get access to the dropbox folder to Rob McClure ( rmcclure AT mdpartners.com ).

Project Participants

Preparation Tooling

Conference Call Schedule and Minutes

Meetings were changed to every other week at San Antonio WGM, occurring at the same time as before - Tuesdays @ 3:30 ET for 90 min.
SAME Mikogo ID


Telephone uses standard HL7 Vocab number: 1 (770) 657-9270,,,598745#

Topic: VSD Regular bi-weekly Meeting Date & Time: Tuesday at 13:30 UTC-06 Duration: 1 hour 30 min

Please click on the link below to join my Mikogo session https://go.mikogo.com/?sp=&sid=073003565

If the above link does not work, you can follow these steps instead to join a session:

  1. Go to http://go.mikogo.com
  2. Enter the Session ID: 073-003-565
  3. Enter your name
  4. Click "Join Session"

Click on the following link to download a quick reference guide for participants: http://www.mikogo.com/jump/quickguide?uilang=en

Remember US ET has returned to Daylight Savings Time, so EDT is -4 UTC

Upcoming Agenda for Aug 4, 2015

  1. Agenda:
    1. Confirm modeling diagram changes (clarifications and name changes) done 7/21 and put new diagrams into diocument.
      1. Perhaps begin wording on the document text
    2. Review IHTSDO negs to confirm they are all resolved. This should finish all negatives.
  2. Look at Affirmatives
  1. Current VSD Spec doc HERE
  2. Current Ballot Comment doc HERE

___

  1. Running list of Completed Issues:
    1. Will submit as DSTU in Normative track and not as Normative in first ballot. [2014-07-22]
    2. We completed the review of the Logical Elements/Functions to define Content Logical Definition based on the MIF
      1. See Valueset MIF ContentDefinition for updated comments.
    3. Discussion on how to control use of DYNAMIC defined value sets continued on 12/20 meeting.
      1. Rob and Lloyd still have to create document and use cases to explain approach to "STATUS" / DYNAMIC stability.
    4. Metadata sheet review now complete
      1. Completed discussion of Value Set Expansion metadata with changes added to end of spreadsheet.
        1. A Value Set Definition can reference 0..* "Trusted Value Set Expansion Reference" that can be a service or an actual expansion
        2. An Expansion can be characterized by a date (required), a time (optional) and an identifier (optional)
    5. As of VSDSpec v18, UML model accurately describes those elements that are "definitional" in that if they change, a new value set or value set version should be created.
    6. 4/22/14 Completed documentation of determination of VSD version STATUSes
    7. This initial ballot will leave inclusion of concept expressions as value set members as OUT OF SCOPE. This remains highly important but will be addressed in the following ballot.
    8. This document has the abstracted decisions from minutes. [1]
    9. We will allow the use of slightly more complex datatypes (DSET and EN are currently used) [Example content attribute was discussed when this decision was reached]
    10. Purpose changed to Scope in v24
    11. We allow NonComputableContent CE to be included in a general CLD, therefore some CLD may have both computable and non-computable content.
    12. Clarified that Value Set Reference CE should not also allow Code System Constraint Parameters as such a thing could be inconsistent with the actual referenced value set.
    13. Clarified that the CLD “slot” in the value set version actually should hold, in essence, a “UnionwithContent” operation on the included content expressions. This can either be an implicit description of how to manage the CEs listed, or we can explicitly have a CLD point to 1..1 UnionWithContent
    14. NCC will remain as part of the MIF-based syntax as a type of Code System Content with LOTS of best practice guidance by Lloyd and Ted. This DOES MEAN that MIF-based syntax CLD is not always computable 2015-06-09

  1. Items for discussion at upcoming Work Group Meeting
    1. Acceptable modeling approach to add additional syntax types for CLD (see meeting notes Sept 23rd).
    2. discussion of Jay Lyle's alternative model approach - he is to identify elements that he has left out and/or added before the WG meeting. Discussion Tuesday Q4.


Final version of the Ballot - here.


Minutes documents:

20131016_VSD_Minutes
20131022_VSD_Minutes
20131030_VSD_Minutes
20131106_VSD_Minutes
20131113_VSD_Minutes
20131120_VSD_Minutes
20131122_VSD_Minutes
20131127_VSD_Minutes
20131129_VSD_Minutes
20131204_VSD_Minutes
20131206_VSD_Minutes
20131211_VSD_Minutes
20131213_VSD_Minutes
20131218_VSD_Minutes
20131220_VSD_Minutes
20140103_VSD_Minutes
20140108_VSD_Minutes
20140115_VSD_Minutes
20140128_VSD_Minutes
20140204_VSD_Minutes
20140211_VSD_Minutes
20140218_VSD_Minutes
20140225_VSD_Minutes
20140304_VSD_Minutes
20140311_VSD_Minutes
20140318_VSD_Minutes
20140325_VSD_Minutes
20140401_VSD_Minutes
20140408_VSD_Minutes
20140415_VSD_Minutes
20140422_VSD_Minutes
20140429_VSD_Minutes
20140513_VSD_Minutes
20140520_VSD_Minutes
20140527_VSD_Minutes
20140603_VSD_Minutes
20140610_VSD_Minutes
20140617_VSD_Minutes
20140701_VSD_Minutes
20140702_VSD_Minutes
20140708_VSD_Minutes
20140722_VSD_Minutes
20140729_VSD_Minutes
20140910_VSD_Minutes
20140923_VSD_Minutes
20140930_VSD_Minutes
20141014_VSD_Minutes
20141021_VSD_Minutes
20141028_VSD_Minutes
20141104_VSD_Minutes
20141125_VSD_Minutes
20141202_VSD_Minutes
20141216_VSD_Minutes
20141223_VSD_Minutes
20141230_VSD_Minutes
20150106_VSD_Minutes
20150113_VSD_Minutes
20150203_VSD_Minutes
20150217_VSD_Minutes
20150303_VSD_Minutes
20150317_VSD_Minutes
20150331_VSD_Minutes
20150414_VSD_Minutes
20150428_VSD_Minutes
20150526_VSD_Minutes
20150609_VSD_Minutes

Key Target Dates

Resubmission of updated content hopefully right after Jan. 2015 meeting.
No need for re-ballot given DSTU status unless we want to do so.

Project Documents

The project working documents are being maintained using Google Docs. These can be found at: Links to project documents