Difference between revisions of "Value Set Definition Standard Project"
Line 42: | Line 42: | ||
− | ===Upcoming Meeting Agenda=== | + | ===Upcoming Meeting Agenda=== (12/6/13) |
# 10 min: Logistics | # 10 min: Logistics | ||
## Confirm folks are working on documenting approaches to VSD from other artifacts | ## Confirm folks are working on documenting approaches to VSD from other artifacts | ||
## Additions to agenda? | ## Additions to agenda? | ||
− | # | + | # 45 min: Content work |
− | ## | + | ## Review of Logical Elements/Functions to define Content Logical Definition |
− | # | + | ### LM to do a review of functions in MIF - look for initial document soon |
− | ## | + | ## Any remaining time: Continued review current value set metadata document [https://docs.google.com/spreadsheet/ccc?key=0AqUpA50mwuwsdGFuanRlZ2tMX2YtY1IyazBCT010MVE&usp=sharing#gid=0] |
− | ### Review last discussion ( | + | ### Start at the top, work our way down |
− | ### | + | ## Versioning (essentially complete as of 12/4/13) |
− | ## | + | ### Review last discussion (12/04/13 minutes) |
− | ## | + | ### Four Identifiers for a value set, one that identifies the VS, 3 that identify changes |
− | ## | + | #### VS ID |
+ | #### Logical Definition ID | ||
+ | ##### Change in the Content Logical Definition | ||
+ | ##### Change in VS Stability | ||
+ | #### Expansion Set ID | ||
+ | ##### New ID when the generated list of members differs from the last generated list | ||
+ | #### Comprehensive VS ID (need better name?) | ||
+ | ##### Changed when any element changes in any way. | ||
+ | ## Continue to clarify questions noted in Minutes on LM additions | ||
---- | ---- | ||
Line 67: | Line 75: | ||
[https://www.dropbox.com/s/ckeg7e9u5yqxy9u/20131127_VSD_Minutes.docx 20131127_VSD_Minutes] | [https://www.dropbox.com/s/ckeg7e9u5yqxy9u/20131127_VSD_Minutes.docx 20131127_VSD_Minutes] | ||
[https://www.dropbox.com/s/oo6mg3jel5ca6j5/20131129_VSD_Minutes.docx 20131129_VSD_Minutes] | [https://www.dropbox.com/s/oo6mg3jel5ca6j5/20131129_VSD_Minutes.docx 20131129_VSD_Minutes] | ||
+ | [https://www.dropbox.com/s/cntjwlrqd3fznsg/20131204_VSD_Minutes.docx 20131204_VSD_Minutes] | ||
==Key Target Dates== | ==Key Target Dates== |
Revision as of 21:34, 4 December 2013
A New Normative Standard for Value Set Definitions
Contents
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 Wednesdays 3-4pm ET
Remember that we are in Daylight Savings Time transitions - US ET is now -5 UTC
Phone: +1 770-657-9270, Participant Code: 598745 Webmeeting Info: Topic: HL7 VSD weekly meeting Date & Time: Wednesday at 13:00 UTC-07 Duration: 1 hour To participate, click on the link: https://go.mikogo.com/?sp=HL7vsd&sid=559756147 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-756-147 3. Enter your name 4. Click "Join Session" 5. Enter the Session Password: HL7vsd
Second Weekly meeting to occur on Fridays 10am EST
Note different screen sharing utility for the first Friday call on November 22, 2013 10AM EST UTC-5 Duration: 1 hour Regular HL7 Vocab Phone: +1 770-657-9270, Participant Code: 598745 To participate, click on the link: https://join.me/474-238-263 On PC or Mac, use any browser with Flash. Nothing to download. On a phone or tablet, launch the join.me app and enter meeting code: 474-238-263 Or browse to http://join.me and enter the code 464-238-263 into the box under "join meeting", and click on the arrow. There is no password for this meeting.
===Upcoming Meeting Agenda=== (12/6/13)
- 10 min: Logistics
- Confirm folks are working on documenting approaches to VSD from other artifacts
- Additions to agenda?
- 45 min: Content work
- Review of Logical Elements/Functions to define Content Logical Definition
- LM to do a review of functions in MIF - look for initial document soon
- Any remaining time: Continued review current value set metadata document [1]
- Start at the top, work our way down
- Versioning (essentially complete as of 12/4/13)
- Review last discussion (12/04/13 minutes)
- Four Identifiers for a value set, one that identifies the VS, 3 that identify changes
- VS ID
- Logical Definition ID
- Change in the Content Logical Definition
- Change in VS Stability
- Expansion Set ID
- New ID when the generated list of members differs from the last generated list
- Comprehensive VS ID (need better name?)
- Changed when any element changes in any way.
- Continue to clarify questions noted in Minutes on LM additions
- Review of Logical Elements/Functions to define Content Logical Definition
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
Key Target Dates
December 20, 2013 - must have final document to HL7 HQ
Project Documents
The project working documents are being maintained using Google Docs. These can be found at: Links to project documents