BALLOT TITLE: HL7 Version 3 Data Types
SUBMITTED BY: Bob Dolin; 714-562-3456; Robert.H.Dolin@kp.org
SUBMISSION DATE: Aug 28, 2000
SUBMITTED BY IDENTIFIER: (assigned by HQ, used below to track individual line items)
OVERALL BALLOT VOTE: 
_XX_	AFFIRMATIVE 
___	NEGATIVE 
BLOCK VOTE by:  xx, xx, xx, xx, xx (indicate the names of those voting the same ballot.  The committee will only have to review one ballot since they are identical.  Please submit one copy of the ballot comments.)

Section	Vote	Type	Existing Wording	Proposed Wording	Comments	Disposition	
1	2	3	4	5	6	7	
0	N	Mi	Vocabulary domains		For each vocabulary domain, please state its name (because for instance, a CWE domain my change after ballot, and users need to know the latest values).	This issue is noted, yet deferred until it is clear how such reference should be made (i.e., by OID or by domain name?)	
0	N	Mi	Vocabulary domains		Please indicate CNE vs. CWE for each domain.	Noted and will be resolved with above before publication.	
0	A	S	Use of CS type		In some cases it seems that CS is overly restrictive. Please consider all uses of CS carefully. (A couple specific cases below.)	CS is generally used when the simplification can be done without harm. For all CNE domains, the data type specification uses CS because (1) the code system is always fixed and (2) local codes are not permitted.	
1.?	N	Mi	Figure 1		Figure needs to be consistent with textual declarations. (It looks like the figure needs to be updated) (A couple specific cases below.)	thanks, revised	
3	N	Mi	Figure 2	Change Figure 2 to show, for instance, that nullFlavor is of type CS as shown in the textual declaration.	Figure needs to be consistent with textual declarations. (It looks like the figure needs to be updated)	thanks, revised	
4	N	Mi	Figure 3		Figure needs to be consistent with textual declarations. (It looks like the figure needs to be updated)	revised, thanks	
5.1.1.10	A	Q	producer : II		There's no definition here. Did you mean to delete this?	yes, deleted	
5.1.3.1	A	Q	paragraph beginning with "CS can only be used for a coded attribute...", and following sentence beginning with "Such coded attributes that are designated..."	Delete this paragraph.	Appears that this paragraph was re-written above, and can therefore now be deleted. 	yes, deleted	
5.1.3.2	N	Mi	Coded Value	Coded Value should be a protected type.	Don't understand why CV isn't a protected type. Why ever declare CV at the RIM level? It's easy to just ignore translations, so why preclude them? This will simplify application of data types to RIM attributes.	because we were advised to provide a CV. Your comment seems reasonable. However, there is a general anti-featuristic tendency in parts of our voting membership. Suggest leaving CV for now and once we see no actual use, we can discuss its deletion.	
5.3.1.2	A	S	scheme : CS	scheme : CV	If "there are a number of URL schemes defined outside RFC documents", how can you make this a CS type?	This is a very good question. This same issue comes up with ED.type. The rationale is as follows: the code system is CNE for W3C URL shemes and IANA MIME media types. However, these code systems – which HL7 does not control – have internal ways to extend the domain (e.g. using x-… prefixes on MIME media types.) So, the code system indeed never changes and we always expect to have a valid code, so the values are CNE, and there is never a need to send an alternative code system or a code extended the HL7 way. Very practically, the URL scheme as used in a standard URL notation, has no room to mention any of the additional properties that come with the CV. So, we must in fact cut it to CS to assure interoperability with the URL standard.	
5.3.2.2	A	S	use: SET<CS>	use : SET <CV>	Suggest changing CS to CV.	This suggestion is reasonable, however, if we would heed, we had another point where one could potentially undermine interoperability with local codes. This is a CNE domain, and therefore, CS is a sufficient form of the code data type. Even more, the use code can be seen as a “structural code,” in which case our rules require us to use CS. 	
5.4.2.2	A	S	use: SET<CS>	use : SET<CV>	Suggest changing CS to CV.	see response to 5.3.2.2	
5.6.1.1	A	S	type : CS	type: CV	Suggest changing CS to CV.	see response to 5.3.2.2	

Legend:
1.	Section, e.g., 3.1.2.
2.	(A) Affirmative or (N) Negative
3.	(Mj) Major, (Mi) Minor, (S) Suggest, (Q) Query, (T) Typo
4.	Cut/paste from ballot.
5.	Use revision marks to denote desired changes.
6.	Reason for the change.
7.	Disposition, (Editors: e.g., Coordinate change with other TC, voted non-persuasive, etc.  This column can also be used by editors to track that approved edits have been applied to the chapter.)