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 59: Line 59:
 
## Ted leads and will review for discussion the draft ballot
 
## Ted leads and will review for discussion the draft ballot
 
### Ted may also continue review of abstracted "decisions" from minutes [https://www.dropbox.com/s/z5xwb8lswbvt3fi/Primary%20VSD%20decisions%20in%20Minutes.docx]
 
### Ted may also continue review of abstracted "decisions" from minutes [https://www.dropbox.com/s/z5xwb8lswbvt3fi/Primary%20VSD%20decisions%20in%20Minutes.docx]
 +
### Ted will lead review of overall structure of draft
 +
### Ted will lead review of format and items for metadata for elements
 
# Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. May give some time to WG discussion but limited....
 
# Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. May give some time to WG discussion but limited....
  

Revision as of 20:30, 11 February 2014

A New Normative Standard for Value Set Definitions

Overview

[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

Project Participants

Preparation Tooling

Conference Call Schedule and Minutes

Weekly meeting to occur Tuesdays 4-5:30pm ET

This was changed in San Antonio
Remember US ET is now -5 UTC
Phone: +1 770-657-9270, Participant Code: 598745

Webmeeting Info - Note - no password is needed anymore:

Topic: Value Set Definition (VSD) weekly call
Date & Time: Tuesday at 16:00 UTC-05
Duration: 1 hour 30 min
To participate, click on the link below:
https://go.mikogo.com/?sp=&sid=559867466
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: 559-867-466
3. Enter your name
4. Click "Join Session"

===Upcoming Meeting Agenda=== (2/11/14)

  1. 15 min: Logistics and key prior discussions
    1. Ted (but not Rob) will be in attendance
      1. Rob still not be available on Thursdays or Fridays.
    2. Schedule for remaining meetings (one per week on Tuesday):
      1. We have 5 weeks of work time and two weeks for draft review.
      2. (2/11) Ted will continue review of documents created (his documents and any remaining from Rob's abstraction). Also continue metadata review if abstractions of this content are not complete.
        1. Woody has agreed to pull some of the google spreadsheet content into the Draft3 version of the ballot
      3. 2/18 – Rob will not be available – Ted to lead. Review of draft
      4. 2/25 and 3/4 will be devoted to finalizing the draft content for review starting the next week.
    3. Additions to agenda?
  2. Running list of Completed Issues:
    1. 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.
    2. 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.
    3. 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)
    4. 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.
    5. This document has the abstracted decisions from minutes. [1]
    6. Please continue to review current value set metadata document and add comments. [2]
  3. 75 min: Content work
    1. Ted leads and will review for discussion the draft ballot
      1. Ted may also continue review of abstracted "decisions" from minutes [3]
      2. Ted will lead review of overall structure of draft
      3. Ted will lead review of format and items for metadata for elements
  4. Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. May give some time to WG discussion but limited....

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

Key Target Dates

Now targeting May 2014 ballot submission
Feb. 16, 2014 - intention to ballot final day
March 2, 2014 - initial content deadline
March 23, 2014 - Final deadline for content.

Project Documents

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