Difference between revisions of "Value Set Definition Standard Project"
Line 46: | Line 46: | ||
− | ===Upcoming Meeting Agenda=== (12/ | + | ===Upcoming Meeting Agenda=== (12/20/13) |
# 10 min: Logistics | # 10 min: Logistics | ||
## We completed the review of the Logical Elements/Functions to define Content Logical Definition based on the MIF | ## We completed the review of the Logical Elements/Functions to define Content Logical Definition based on the MIF | ||
### See [https://www.dropbox.com/s/30xaaeca1c0q32e/Valueset%20MIF%20ContentDefinition.docx Valueset MIF ContentDefinition] for updated comments. | ### See [https://www.dropbox.com/s/30xaaeca1c0q32e/Valueset%20MIF%20ContentDefinition.docx Valueset MIF ContentDefinition] for updated comments. | ||
## See Vocab Listserv for continued discussion on use of STATUS | ## See Vocab Listserv for continued discussion on use of STATUS | ||
+ | ### Listserv discussion resolved through the use of: | ||
+ | #### effectiveDate & endDate | ||
+ | ##### This essentially becomes a date range during which the definition can be used to create expansions that may be used to create new instances of data. The endDate can be added without efecting the version of the definition. | ||
+ | #### A TBD characteristic that can be used to identify code system versions for which the definition can be applied. | ||
+ | ##### This "set" must be defined at the time the definition is created. It can not be modified later. | ||
## Holiday schedule: | ## Holiday schedule: | ||
− | ### | + | ### Rob will run 12/20. |
### No meeting 12/25 - 1/1. Next meeting will be 1/3 | ### No meeting 12/25 - 1/1. Next meeting will be 1/3 | ||
### Schedule will change in Jan and beyond. Rob will not be available on Thursdays or Fridays. | ### Schedule will change in Jan and beyond. Rob will not be available on Thursdays or Fridays. | ||
Line 59: | Line 64: | ||
# 45 min: Content work | # 45 min: Content work | ||
## Continue discussion on [https://docs.google.com/spreadsheet/ccc?key=0AqUpA50mwuwsdGFuanRlZ2tMX2YtY1IyazBCT010MVE&usp=drive_web#gid=0 Value_Set_Metadata] spreadsheet | ## Continue discussion on [https://docs.google.com/spreadsheet/ccc?key=0AqUpA50mwuwsdGFuanRlZ2tMX2YtY1IyazBCT010MVE&usp=drive_web#gid=0 Value_Set_Metadata] spreadsheet | ||
− | ### We will continue to review the content of this sheet | + | ### We will continue to review the content of this sheet. |
### Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. This may not be included in initial standard. | ### Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. This may not be included in initial standard. | ||
Line 77: | Line 82: | ||
[https://www.dropbox.com/s/y6o8x497q2a26u3/20131211_VSD_Minutes.docx 20131211_VSD_Minutes] | [https://www.dropbox.com/s/y6o8x497q2a26u3/20131211_VSD_Minutes.docx 20131211_VSD_Minutes] | ||
[https://www.dropbox.com/s/yfzaiqsr2oru8y9/20131213_VSD_Minutes.docx 20131213_VSD_Minutes] | [https://www.dropbox.com/s/yfzaiqsr2oru8y9/20131213_VSD_Minutes.docx 20131213_VSD_Minutes] | ||
− | [https://www.dropbox.com/s/ | + | [https://www.dropbox.com/s/ojz102c6j97ixh8/20131218_VSD_Minutes.docx 20131218_VSD_Minutes] |
==Key Target Dates== | ==Key Target Dates== |
Revision as of 07:23, 20 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 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
Duration: 1 hour Regular HL7 Vocab Phone: +1 770-657-9270, Participant Code: 598745 Web session: https://go.mikogo.com/?sp=VSD-2ndcall&sid=277184318 If the above link does not work, you can follow these steps instead to join a session: Go to http://go.mikogo.com, Enter the Session ID: 277-184-318, Enter your name, Click "Join Session", Enter the Session Password: VSD-2ndcall If MIkogo is not available, we will use the following: 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/20/13)
- 10 min: Logistics
- We completed the review of the Logical Elements/Functions to define Content Logical Definition based on the MIF
- See Valueset MIF ContentDefinition for updated comments.
- See Vocab Listserv for continued discussion on use of STATUS
- Listserv discussion resolved through the use of:
- effectiveDate & endDate
- This essentially becomes a date range during which the definition can be used to create expansions that may be used to create new instances of data. The endDate can be added without efecting the version of the definition.
- A TBD characteristic that can be used to identify code system versions for which the definition can be applied.
- This "set" must be defined at the time the definition is created. It can not be modified later.
- effectiveDate & endDate
- Listserv discussion resolved through the use of:
- Holiday schedule:
- Rob will run 12/20.
- No meeting 12/25 - 1/1. Next meeting will be 1/3
- Schedule will change in Jan and beyond. Rob will not be available on Thursdays or Fridays.
- Additions to agenda?
- Folks should continue to review current value set metadata document but we will come back to this once Content Logical Definition function review is complete. [1]
- We completed the review of the Logical Elements/Functions to define Content Logical Definition based on the MIF
- 45 min: Content work
- Continue discussion on Value_Set_Metadata spreadsheet
- We will continue to review the content of this sheet.
- Need to plan an entire meeting on constraints/approach for allowing expressions as members of a value set. This may not be included in initial standard.
- Continue discussion on Value_Set_Metadata spreadsheet
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
Key Target Dates
Now targeting May 2014 ballot submission Feb. 2014 - intention to ballot
Project Documents
The project working documents are being maintained using Google Docs. These can be found at: Links to project documents