Ballot SubmissionTriage & Committee ResolutionBallot Comment Tracking
Comment NumberBallotChapterSectionPage #Line #Artifact IDResource(s)HTML Page name(s)URLVote and TypeSub-categoryTracker #Existing WordingProposed WordingBallot CommentSummaryIn person resolution requestedComment groupingScheduleTriage NotePubsDisposition WGDispositionDisposition Comment or Retract/Withdraw detailsDisposition/Retract/ Withdrawal DateMover / seconderFor AgainstAbstainRetracted / WithdrawnDisposition External OrganizationResponsible PersonChange AppliedSubstantive ChangeSubmitted ByOrganizationOn behalf ofCommenter EmailSubmitter Tracking IDReferred ToReceived FromNotes
1VocNEGSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Phillip_Burgher_20180507101938.xls' that was uploaded to to the ballot website.See uploaded spreadsheet**website comment**Persuasive with modSee item #84Rob M / Russ H600YesPhillip BurgherPhilips Healthcarephillip.burgher@philips.com
2VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesDave Carlson Ph.D.U.S. Department of Veterans Affairsdcarlson@xmlmodeling.com
3VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesKathleen ConnorU.S. Department of Veterans Affairskathleen_connor@comcast.net
4VocA-SSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Patricia_Craig_20180507235748.xls' that was uploaded to to the ballot website.Please see spreadsheet.**website comment**Not relatedUnrelated row based on upload of spreadsheetCarmela/Rob300YesPatricia Craig MS MISThe Joint Commissionpcraig@jointcommission.org
5VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesMike DavisU.S. Department of Veterans Affairsmike.davis@va.gov
6VocA-CSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_George_Dixon_20180417153008.xls' that was uploaded to to the ballot website.**website comment**Not relatedAll comments elsewhere in sheetCarmela/Rob300YesGeorge DixonAllscriptsgeorge.dixon@allscripts.com
7VocNEGSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Floyd_Eisenberg_20180504105511.xls' that was uploaded to to the ballot website.**website comment**Not relatedSee item #101Rob M/Ted K700YesFloyd Eisenberg MDiParsimony LLCFEisenberg@iParsimony.com
8VocA-SSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Peter_Gilbert1_20180420095715.xls' that was uploaded to to the ballot website.**website comment**Not relatedComment is actually #81 on sheetCarmela/Rob300YesPeter GilbertMeridian Health Planpeter.gilbert@mhplan.com
9VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesCatherine Hoang BSN, MSU.S. Department of Veterans AffairsCatherine.Hoang2@va.gov
10VocA-SSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Lindsey_Hoggle1_20180507220234.xls' that was uploaded to to the ballot website.Please refer to attached document for questions and suggestions.**website comment**Not relatedComments elsewhere in sheetCarmela/Rob300YesLindsey HoggleAcademy of Nutrition & Dieteticslhoggle@eatright.org
11VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesVannak Kann MHAU.S. Department of Veterans Affairsvannak.kann@va.gov
12VocNEGSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_t_klein_20180507153936.xls' that was uploaded to to the ballot website.Many small nits in the document that need to be fixed if it to be published as a normative standard.**website comment**Persuasive with modTed will identify then send to team for finalizing2018-05-15Rob McClure/Russ Hamm900YesWilliam Ted KleinKlein Consulting Informatics LLCkci@tklein.com
13VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesMichael Lincoln MDU.S. Department of Veterans Affairsmlincoln1@gmail.com
14VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesSean MuirU.S. Department of Veterans Affairssean.muir@jkmsoftware.com
15VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesGalen Mulrooney MBAU.S. Department of Veterans Affairsgalen.mulrooney@jpsys.com
16VocNEGSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Craig_Newman_20180412083954.xls' that was uploaded to to the ballot website.**website comment**Persuasive with modSee items #22 and #24Rob M / Russ H600YesCraig NewmanNorthrop Grummancsnewman88@gmail.com
17VocA-SSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_s_robertson_20180505222415.xls' that was uploaded to to the ballot website.**website comment**Not relatedComments elsewhere in sheetCarmela/Rob300YesScott Robertson PharmDKaiser Permanentescott.m.robertson@kp.org
18VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesKen RubinU.S. Department of Veterans Affairsken.rubin@utah.edu
19VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesChris ShawnU.S. Department of Veterans Affairschristopher.shawn2@va.gov
20VocNEGRefer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesIoana Singureanu MSCs, FHL7U.S. Department of Veterans Affairsioana.singureanu@bookzurman.com
21VocNEGSee document 'HL7_SPEC_VALUESETDEF_R1_N1_2018MAY_Greg_Staudenmaier_20180507195313.xls' that was uploaded to to the ballot website.Refer to the ballot comment spreadsheet submitted by Greg Staudenmaier.**website comment**Persuasive with modSee resolution noted for comment #76Carmela/Lou700YesGreg StaudenmaierU.S. Department of Veterans Affairsgreg.staudenmaier@va.gov
22Voc5Figure 219NEGIf I’m reading this figure right, Name Language and Preferred Name Indicator have data types of CD and BL respectively, but in sections 5.2.2.3.1.2 and 5.2.2.3.1.3 the data type is given as ST. I'm assuming these should be the same. I suggest you review the figure relative to the text sections and sync up all data types as other elements have similar discrepancies.Persuasive with modDuplicate of #89 and #90Rob M / Carmela C501YesCraig Newman
23Voc55.2.3.225A-TIf either of the elements within this section changes in any wayIf the elements within this section changes in any wayThe description says "either", but the CLD seems to be the only Definitional Element. I suggest removing the words "either of"Persuasiveremoved noted wordsCarmela/Lou700YesCraig Newman
24Voc55.2.3.3.227NEGWhen the Activity Status is set to “Active”, the Activity Status Date defines the Effective Date which is the first date-time the Value Set Definition Version becomes active. When the Activity Status is set to “Inactive”, the Activity Status Date is the first date-time when the Value Set Definition version becomes Inactive.Figure 3 includes an arrow from the "inactive" status back to the "active" status which implies that a Value Set Version can be "activated" multiple times, initially from a "preliminary" status but then afterwards from an "inactive" status. Presumarly, a version could also be "inactivated" multiple times. If this is the case, is the Activity Status Date really intended to be the first date-time a Value Set Definition Version Activity Status is set to either "active" or "inactive" or is it the most recent date-time the status was changed? If it is the first time the status is achieved, please including an explanation of why you want the first date-time rather than the most recent date-time. Either way, please clarify if the status can change multiple times and the impact that has on the date-time. Persuasive with modRemoved the word "first" from the usage note section and also clarified that this cycle can happen repeatedlyRob M/ Carol M600YesCraig Newman
25Voc55.2.3.3.227A-SThis is the date the associated status for this version is to begin.This is the date the associated status for this version began.The description of the activity status is that it is the "current state of the Value Set Definition", given that wording, having the Description of the Activity Status Date be future tense doesn't seem appropriate. I suggest updating the wording.Persuasive with modChanged to "began" but also improved the definition and usage notes to allow for setting the date in the future so as to define ac future change in the activity status.Carmela/Rob300YesCraig Newman
26Voc55.2.3.3.328A-SVSAC Value Set Definition versions are published at 00:01 (one minute after midnight) of the publish date morning (Eastern Time) and the earliest a Value Set Definition version can be published is the next day’s morning.I'm not sure I understand this sentence. Given that the workflow statuses are from VSAC, does this sentence refer to a Workflow Status VSAC Value Set Definition or does it refer to any Value Set Definition housed by VSAC? If the latter, are there restrictions on value sets published by other sources? Please clarify what you mean.Considered - Question AnsweredThe VSAC example is only meant to be a particular example of a specific approach to using this element, it is not a general standard approach for other implementations.Carmela/Rob300YesCraig Newman
27Voc55.2.3.430A-QElements in this section are not entered by the author, but are derived values based on other elements in the Value Set Definition metadata.Is "type" really a derived element? It feels like the type could be determined by and entered by the author, especially if the CLD is non-computable.Persuasive with modAgree that TYPE should not be a derived element since "deriving it" wuld be very difficult. If a CLD is non-computable then the TYPE would be likely unstated, or even, for some systems TYPE could be "non-computable." This means TYPE is non longer in the Derived section so the diagram must change.Carmela/Carol300Craig Newman
28VocNEGThe ballot does not indicate a position regarding value set content that may be "required" or "optional" - i.e., in a specific value set, all components must be available (required) Vs some may be used in some settings and not others (hence, "optional"). To meet a clinical decision support use case, value sets need to be constrained to meet the clincial scenario. Inclusion of extraneous values causes the CDS criteria to be met when it may not be appropriate. If there is a need to provide "required" elements and "optional" elements that might address jurisdictional variation, the two use cases should be met by producing two (or more) value sets rather than mixing concepts of different value into a single value set. These tenets should apply across all HL7 standards (V2, V3, FHIR).YesNot relatedThe use of Required and Optional in V2 value sets only occurs in non-implementable Igs, these concept attributes are only assigned to value set expansion members and are not a part of the value set definition so are not discussed in this spec. Further discussion on these attributes will occur in the forthcoming project on V2 datatype constraint project.Rob M/Ted K700YesFloyd Eisenberg
29Voc13A-TConcept Descriptor, CD, or those similer), Concept Descriptor, CD, or those similar), TypoNot relatedSee #34 - this is a copyCarmela/Rob300YesGeorge Dixon
30Voc14A-Thttp://www.hl7.org/documentcenter/public_temp_EA794C7B-1C23-BA17- 0CC107D16DBCA514/standards/V3/core_principles/infrastructure/coreprinciples/v3modelcoreprinciples. html#coreP_Coded_Properties-value-setsLink not functioningNot relatedSee #35 - this is a copyCarmela/Rob300YesGeorge Dixon
31VocA-Tforafor aTypoNot relatedSee #36 - this is a copyCarmela/Rob300YesGeorge Dixon
32Voc5.1.318A-C• Intensional Definition: • Intensional Definition: Please provide an example or a value set that uses this method, would UCUM be such a value set? Though UCUM as an example is confusing in that http://unitsofmeasure.org/ucum.html as a set of rules for defining and PHVS has a defined value set. Not relatedSee #37 - this is a copyCarmela/Rob300YesGeorge Dixon
33Voc37A-TFootnote 18 Using the HL7 Expression Grammar the appropriate function to use in a CLD clause is Error! Reference source not found. within Error! Reference source not found..Not relatedSee #38 - this is a copyCarmela/Rob300YesGeorge Dixon
34Voc13A-TConcept Descriptor, CD, or those similer), Concept Descriptor, CD, or those similar), TypoPersuasivefixedCarmela/Lou700YesGeorge Dixon
35Voc14A-Thttp://www.hl7.org/documentcenter/public_temp_EA794C7B-1C23-BA17- 0CC107D16DBCA514/standards/V3/core_principles/infrastructure/coreprinciples/v3modelcoreprinciples. html#coreP_Coded_Properties-value-setsLink not functioningPersuasive with modLink removed.Carmela/Lou700YesGeorge Dixon
36VocA-Tforafor aTypoPersuasivefixedCarmela/Lou700YesGeorge Dixon
37Voc5.1.318A-C• Intensional Definition: • Intensional Definition: Please provide an example or a value set that uses this method, would UCUM be such a value set? Though UCUM as an example is confusing in that http://unitsofmeasure.org/ucum.html as a set of rules for defining and PHVS has a defined value set. George Dixon
38Voc37A-TFootnote 18 Using the HL7 Expression Grammar the appropriate function to use in a CLD clause is Error! Reference source not found. within Error! Reference source not found..PersuasivefixedCarmela/Lou700YesGeorge Dixon
39Voc8A-CThe data types used by this specification are based upon HL7 Datatypes R2 and ISO 21090The data types used by this specification are based upon HL7 Datatypes R2 and ISO 21090. Note that these specifications describe a great deal of optional detail: the use of "string" does not imply, e.g., that all implementers must support a "translation" property.These types can be a source of consternation.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
40Voc8A-CThe set of ISO 21090-based data types used are: ST, ST*, CSThe set of ISO 21090-based data types used are: ST, CSST* not found in documentYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
41Voc22A-CValue Set Definition Naming . . . Data Type: COLLThis is a class; it's not clear that it needs a type other than itself.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
42Voc10A-CThis document is a normative track specificationWhat are the implications of this statement? For FHIR, CDA, etc.?YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
43Voc12A-CA concept is a unitary mental representation of a real or abstract thing; an atomic unit of meaning.A concept is a mental representation of a real or abstract thing; a unit of meaning.Concepts are fractal; attempts to define an elementary level tend to founder.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
44Voc12A-CIn structured vocabularies, these concepts are assigned codes.In structured vocabularies, concepts are assigned names and codes.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
45Voc12A-CThe context in which a concept is defined is called a code system. A code system is a maintained collection of uniquely identifiable concepts with associated representations, designations, associations and meanings, published by a single organization or authority.The context in which these assignemnts are made is called a code system. A code system is a maintained collection of uniquely identifiable concept identifiers, a.k.a. codes, with associated representations that tell us what they stand for and, optionally, associations and other infrastrucure, published by a single organization or authority.a lot of blurring between concepts and codesYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
46Voc12A-CA Value Set describes a collection of conceptsAn HL7 Value Set describes a collection of codes1. "value" and "set" are already words, and "value set" has a colloquial meaning that we can't usurp. We are defining a term of art, and it needs its own term. 2. concepts: see prior commentYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
47Voc12A-Cthe phrase “Value Set” usually is taken to mean both the Value Set Definition and the Value Set Expansionthe phrase “Value Set” can mean either the Value Set Definition or the Value Set Expansion, and when neither is specified, we take it to encompass both.But we want to specify wherever we can.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
48Voc12A-CConstrained lists of strings are not considered Value Sets,Constrained lists of strings are not considered HL7 Value Sets,Example provided for prior comment on terms of artYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
49VocA-CThe HL7 RIM is composed of classes with attributes that are data elements.The HL7 RIM is composed of classes that contain data elements.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
50Voc14A-Cmodel bindingTypeface approach should be applied uniformly (i.e., also to "concept," "code system," etc.) or not usedYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
51Voc14A-C4.3 Terminology bindingThis could be a lot shorter, as it doesn't seem to affect the content. Keep paragraph 1 and remove 2 & 3.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
52Voc14A-Cwhich are not necessarily Value Sets or Code Systemswhich do not conform to the design constraints developed here for HL7 Value Sets (or, for that matter, to commonly accepted criteria for Code Systems)YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
53Voc15A-CWhen most people think of a Value Set, they think of a list of codes or phrases. These lists may be called member list, code list, etc. While a critical part of the usefulness of a Value Set, the final set of Code System members used by implementers, which is called the Value Set Expansion in this specification, is only one part of the collective information that is a Value Set.This specification takes the natural language term "value set," indicating only a set of values, and enhances it with a set of expectations that allows it to be used across interpretive communities with common assumptions regarding its construction and use. This enhanced construct is the "HL7 Value Set." An HL7 Value Set is created as a "value set definition," which tells terminology managers and services what should be included in the set, but it is consumed as a "value set expansion," which tells terminology clients the members of the set. It is important to make this distinction explicit in discussions concerning the HL7 Value Set.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
54Voc16A-CRelationship Between the Value Set Definition and Value Set Expansion Code SetRelationship Between the Value Set Definition and Value Set Expansion undefined terms (code set) can confuse Ah, this is picked up later. I don't have a problem with "expansion code set" if it is used consistently Well, not a huge problem. Still a problem. It does imply some kind of difference between 'code set' and 'value set' that may be hard to explainYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
55Voc16A-Cwhich Code System Concept Representationswhich codesEither term is ok, but should be consistent. The shorter one introduces less complexityYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
56Voc16A-CTherefore a Value Set Definition is not the artifact that contains actual instance Value Set content.Therefore a Value Set Definition is not the artifact that terminology clients should use to ascertain HL7 Value Set membership.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
57Voc16A-COnly a Value Set Expansion Code Set (see Figure 1 and also Section 8 below) will containOnly a Value Set Expansion Code Set (see Figure 1 and also Section 8 below) can be relied on to containYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
58Voc16A-Cthe accurate Expansion Code Set Member Concept Representationsthe accurate Expansion [Code Set] member codesYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
59Voc17A-CBoth approaches are used frequentlyimport of this paragraph not clearYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
60Voc17A-CAdd: Figure 1 illustrates how a value set expansion may change over time whether its value set definition is written intensionally or extensionally.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
61Voc8A-CUML-datatype approximationsYou can put whatever types you want in UML. These look like V3.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
62Voc25A-CIf the string is intended to be encoded as a timestamp, the format should be TS.DATETIME.FULL to be consistent with HL7 Datatypes R2.If the string is intended to be encoded as a timestamp consistent with HL7 Datatypes R2., the format should be TS.DATETIME.FULL YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
63Voc25A-CThe Value Set Identifier does not change.In this case, the Value Set Identifier does not change.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
64Voc26A-CData Type: A COLL of a single Content Logical DefinitionWhy a collection if there's only one?YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
65Voc27A-CThe date-time is expected to be as of 0001 UTC of the Activity Status Date.Not sure what this is sayingYesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
66Voc28A-C5.2.3.3.3 Workflow StatusAdd: it is expected that this would be used to manage maintenance activities, but that a terminology service would not be expected to expose this information, and that different services might adopt different workflow status values reflecting their local practices.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
67Voc29A-CData Type: COLL (listed following)as elsewhere, "coll" seems to be used to "collect" properties of a class. Might be simpler to omit a type, as a class is its own type.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
68Voc32A-CThis should be captured down to the second.This should be captured precisely enough to prevent confusion. In most cases, a date may work, but particularly volatile cases may require greater precision.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
69Voc35A-Cwould be different in environment A and B.Would the behavior differ in environment A after the environment updates to the 7/17 distribution, or would "available" mean available on to the system on 8/1, irrespective of subsequent updates?YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
70Voc37A-CThis attribute is to be implemented independent of “LockedDate” such that if LockedDate is set, then this attribute defines if only active concepts or all concepts are placed into the Value Set Expansion Code Set.This attribute is to be implemented independent of “LockedDate”: i.e., if LockedDate is set, and a code is inactivated after the lock date, then activeOnly = true will exclude that code.Not sure, but this is one reading.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
71Voc37A-CIt is suggested that this element may be changed without being considered a change in the CLD.It is suggested that this element may be changed without being considered a change in the CLD, if the expand operation results in the same set.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
72Voc37A-CDefinition: a computable string that when evaluated using the appropriate syntax yields a set of Concept Representations from identified Code Systems.Definition: a computable string that when evaluated using the appropriate syntax yields a set of Concept Representations from identified Code Systems, or a human-readable description of the content . . . 1. Currently, this can be either; it doesn't have to be computable 2. But for the non-computable case, why do we need it? Is it any different from the Value Set Definition.scope?YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
73Voc39A-CAn HL7 Value Set Definition Expression SyntaxHL7 Value Set Definition Expression Syntax or, HL7 V3 Value Set Definition Expression Syntax or, MIF Value Set Definition Expression Syntaxit needs its own nameYesPersuasive with modChange name to VSD-Default Expression SyntaxJay/Carmela400Greg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
74Voc40A-Cseven typeseight in the prior paragraph; six, apparently, usable. If we need a "there are N ways to do this" statement, align them.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
75Voc54A-CA Value Set Expansion Code Set is the complete enumeration of the member list of Concept Representations as defined in a Value Set Content Logical Definition (CLD).A Value Set Expansion Code Set is the complete enumeration of the member list of Concept Representations as defined in a Value Set Content Logical Definition (CLD) and applied to a temporally specific set of assets.YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
76VocpassimNEGThese need consistent terms Code system (pretty consistent already) HL7 value set (not "value set" if avoidable) HL7 Value Set Definition, or Value Set Definition HL7 Value Set Expansion, or Value Set Expansion, or HL7 Value Set Expansion Code Set code, coded concept, concept representation (preferably not "concept"; "concepts or codes", "concepts/codes")YesPersuasive with modChanged the initial sentence in section 3.2 In Scope to: This document is a normative track specification that describes the data elements that formally define and characterize (describe) how to create an HL7 conformant Value Set. Lou/Rob H700YesGreg Staudenmaier US Department of Veterans AffairsJay Lylejay.lyle@jpsys.com
77VocChapter 33.19A-SThis specification is primarily intended for terminology system designers and individuals responsible for implementing standards that use terminology subsets.This specification is primarily intended for terminology system designers, individuals responsible for implementing standards that use terminology subsets, and domain subject matter experts.Appreciate the guidance in this document; question if this was created prior to the concept of VSAC, and of multiple domain authors and stewards who have less expertise in health IT standards and terminology. Suggest expanding scope of readers education and health IT standards and vocabulary skill level.YesPersuasive with modAdded requested phrasingCarmela/Rob300YesLindsey HoggleAcademy of Nutrition and Dietetics
78VocChapter 55.2.2.3.323A-QThis is intended to convey the restrictions, such as copyright, of the directly referenced Value Set Definition and Expansion, including Code System(s). It should also contain contact information. It is a text block of unlimited length and unspecified internal format although markdown is recommended so that specific information types, such as contact, are identified.This is intended to convey the restrictions, such as copyright, of the directly referenced Value Set Definition and Expansion, including Code System(s). It should also contain contact information. It is a text block of unlimited length and unspecified internal format although markdown is recommended so that specific information types, such as contact, are identified.Clarification requested on inclusion of copyright material and intellectual property specific to nutrition care process (NCP) descriptions which are intended to optimize nutrition specific care.Clarification requested on appropriate attribution.YesLindsey HoggleAcademy of Nutrition and Dietetics
79VocChapter 55.2.3.4.230A-SIntensional: Any CLD that is not either Extensional or Grouping.Intensional: (definition used previously in this document)Reader assumes this is in reference to VSAC but is confusing. Suggest consistency of defined terms.Persuasive with modChanged to "the CLD is an algorithm that, when executed by a machine (or interpreted by a human being), yields a set of concepts"Carmela/Rob300YesLindsey HoggleAcademy of Nutrition and Dietetics
80Voc33.310A-TImplications of the use of this Standard in evaluation of post-coordination concepts, even though support for inclusion of expressions is tacitly possible given the functionality described in the Content Logical Definition section, and the fact that such post=coordinated expressions can be communicated in a string. Implications of the use of this Standard in evaluation of post-coordination concepts, even though support for inclusion of expressions is tacitly possible given the functionality described in the Content Logical Definition section, and the fact that such post-coordinated expressions can be communicated in a string.Suggest post=coordinated be changed to post-coordinatedNoPersuasiveFixedCarmela/Rob300YesPatty Craigpcraig@jointcommission.orgLisa Andersonlanderson2@jointcommission.org
81Voc4.4A-SValue Sets are used throughout HL7 models including Version 2 models, although in Version 2 artifacts they have to date (this is under review) been represented in V2 tables which are not necessarily Value Sets or Code Systems.Value Sets are used throughout HL7 models. However, in Version 2 models artifacts that have been defined until now have been represented in V2 tables which are not necessarily Value Sets or Code Systems.Not quite sure what "although in Version 2 artifacts they have to date" means. Are you trying to day that v2 artifacts that have been defined to so far? If so, then the proposed wording is given to make this clearer.Persuasive with modChanged to: Value Sets are used throughout HL7 models including Version 2 models. Version 2 terminology artifacts are traditionally represented using “V2 tables” which are a combination of a Code System and a Value Set. As of Version 2.9 these tables will no longer be the official Version 2 terminology artifact, instead they are published as separate Value Sets and Code Systems. Carmela/Lou700YesPete GilbertMeridian Health Plan
82Voc52.3.3.127A-QWho would be the external governance to make sure there aren't overlapping active value sets for the same concept?Considered - Question AnsweredGovernanace of value set content is not a part of the standard.Carmela/Carol300Phillip BurgherPhilips
83Voc52.3.4.130A-QWhy would a value set include a code system in its code system source list, but not actually have any codes from that code system in its expansion set? That seems like it may be confusingConsidered - Question AnsweredChanged Usage Notes: This list of Code System Identifiers should be derived from the Content Logical Definition to ensure that it is accurate. When the Content Logical Definition does not specify any content types based on Code Systems, this is not populated. It is possible that a Code System will be in the CLD but not generate a concept in the Value Set Expansion Code Set if codes specified in the CLD are inactive or if an expression does not identify any codes; therefore, this may list Code Systems that are not resident in a specific Value Set Expansion Code Set.Carmela/Carol300Phillip BurgherPhilips
84Voc62.337NEGForgive the potential misunderstanding, but in general I believe users to understand a value set as defined by the set of codes included in it, i.e. the expansion. Changing the CLD to get a completely new expansion and not requiring a version upgrade seems like it will be prone to significant downstream effects without proper provenanceNot persuasiveThe commenter misunderstands the requiremnts defineds in the spec with regards to when a new value sset definition is required. Please see section 5.2.3.2 Value Set Definition Version — Definitional ElementsRob M / Russ H600YesPhillip BurgherPhilips
85Voc3.19A-SThank you for linking sections names in narrative to the section in the document. It would be even more helpful if the section name links were a different font, in italics, or otherwise distinguishable.Request regarding section linksConsidered - No action requiredWe are slaves to the microsoft godsCarmela/Lou700YesScott M RobertsonKaiser Permanente
86Voc4.414A-S… although in Version 2 artifacts they have to date (this is under review) been represented …… although in Version 2 artifacts they have, to date, been represented …"this is under review" isn't necessary when noting the current casesentence clarificationPersuasive with modsee #81Carmela/Lou700YesScott M RobertsonKaiser Permanente
87Voc5.1.317A-SAs such, the difference between Intensional and Extensional becomes essentially a description of the style used to determine the Value Set Expansion Code Set with one important distinction when considering Value Set maintenance and the Value Set Expansion Code Sets that will occur with subsequent allowed Code System versions.As such, the difference between Intensional and Extensional becomes essentially a description of the style used to determine the Value Set Expansion Code Set. An important is when considering Value Set maintenance and the Value Set Expansion Code Sets that will occur with subsequent allowed Code System versions.long sentence was difficult to parse. Suggested text is marginally betterlong sentence editPersuasive with modremoved half of sentence. Other changes tooCarmela/Lou700YesScott M RobertsonKaiser Permanente
88Voc5.2.2.120A-CIf an implementation allows multiple identifiers that can be evaluated to obtain the single Value Set Definition, one identifier is to be selected as the persistent single identifier.How is "one, persistent" identifier identified?How is "one, persistent" identifier identified?Scott M RobertsonKaiser Permanente
89Voc5.2.2.3.1.322NEGData Type: STData type in the diagram is BL. Since it is, essentially, a true/false flag, BL seems more appropriate. If BL is correct, then strike the sentence "the only permissible value …"Preferred Name Indicator Data Typediagram fixPersuasive with modKeep the datatype ST and change the diagram to match to not force a change in cardinality to 1..1 or allow the BL to be a "nullable BL"2018-05-15Rob McClure / Ted Klein900Scott M RobertsonKaiser Permanente
90Voc5.2.2.3.423NEGData Type: STData type in the diagram is BL. Since it is, essentially, a true/false flag, BL seems more appropriate. If BL is correct, then revise the description to "When set to 'true' …"Experimental Data Typediagram fixPersuasive with modKeep the datatype ST and change the diagram to match to not force a change in cardinality to 1..1 or allow the BL to be a "nullable BL"2018-05-15Rob McClure / Ted Klein900Scott M RobertsonKaiser Permanente
91VSD4.2 Coded Data Types in HL713NEGA data type can be defined by intension, by extension or…A set of coded concepts that represent the allowable values for a data element of a coded data type can be defined by intension, by extension or…worded incorrectlyPersuasiveRemoved offending words2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
92VSD4.3 Terminology Binding13NEGHL7 has defined two types of binding, Model Binding and Context Binding, and a separate project has been underway to fully define all details of these, with a Standard to be developed at some point in the future.HL7 has defined two types of binding, Model Binding and Context Binding in Version 3, and other types in FHIR and Version 2. A separate project has been underway to fully define all details of these, with a Standard to be developed at some point in the future.clarify that HL7 has multiple kinds of stuff defined and used, and the two mentioned here are explicitly for Version 3.PersuasiveMade change as specified.2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
93VSD4.3 Terminology Binding14A-QWe go to some length to describe the V3 Core Principles binding, but don't mention FHIR binding and what has been used and defined in the Conformance Chapter of V2. Suggesty that this be replaced with a paragraph that just indicates that there arae multiple different approaches currently, and the individual product famlies should be examined for the details. And that the separate project to unify them is under way.Considered - Question AnsweredSection re-written. Also mentions binding project.Carmela/Carol300Ted KleinKCILLC
94VSD5.1.2 Relationship between the Value Set Definition and the Value Set Expansion Code SetNEGTherefore a Value Set Definition is not the artifact that contains actual instance Value Set content.This will cause confusion, since the FHIR ValueSet resource actually contains BOTH the VSD and the VSE. Sentence needs to be reworked. Perhaps add the phrase "but may be packaged together for convenience by some systems." or something like that.PersuasiveText clarified2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
95VSDmany sectionsA-SIn reading this through, it occurs to me that it might be clearer to instead of saying "definitional" vs. "non-definitional" we say "definitional" vs. "descriptive".Not persuasiveSuggested change in wording does not improve the documentCarmela/Lou700YesTed KleinKCILLC
96VSD5.2.2.2.1 ScopeNEGdescribe “the semantic space” to be included in the Value Set Expansion.describe “the semantic space” covered by the coded concepts included in the Value Set Expansion.We don't include semantic spaces in the VSE. Persuasive with modText clarified2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
97VSD5.2.2.3.1.2 Name LanguageNEGCardinality: 1..1Cardinality: 0..1This should not be required unless more than one language is in use; the default should be the 'usual' language in the jurisdiction or organization where it is used. Persuasivechanged to 0..12018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
98VSD5.2.2.3.7 UseNEGWhen initially conceived (and in the initial publication) this was a linked set of entries to describe a User who is employing the Value Set for a particular Usage. In the comment review process a linked set of “User” and “Usage” was deemed too complex, so this element is now a general data type.Remove. A Normative specification that is being released as a Normative document the first time should not have this descriptive history in it.PersuasiveRemovede text describing prior approach2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
99VSD6.2.3 CLDSyntaxReferenceNEGCardinality: 0..1The description ans Usage Notes are silent on what it to be used if this is omitted. This needs clarification.Not persuasiveLack of information can not be assumed to be a single approach2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC
100VSD7.1 Content Defining Element TypesNEGany one of the following seven typesany one of the following six typesonly six are listed :-)PersuasiveCorrected to six2018-05-15Rob McClure/Russ Hamm900YesTed KleinKCILLC