This wiki has undergone a migration to Confluence found Here
InM 29 R1 2a2c Reconciliation
InM Evote Cp 2a 2c
TBD - Chapter 2.A
- Persuasive with Mod
| "Comment Number" | Ballot | Chapter | Section | Page # | Line # | Vote and Type | Existing Wording | Proposed Wording | Ballot Comment | Comment grouping | Disposition | "Disposition Comment or Retract/Withdraw details" |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 117 | 2.A | 2.A.75 | 79 | A-Q | String data is left justified (i.e., no leading blank space) with trailing blanks optional. | What does "optional" mean in this context? Are trailing blanks significant, or can applications freely trim those off without changing the meaning of a message? Is it supposed to be consistent with TX in which trailing spaces should be removed? | InM-6 | Persuasive with mod | Clarify Optional , add guidance to include /x20/ when you need to send only a blank. |
* Persuasive
| "Comment Number" | Ballot | Chapter | Section | Page # | Line # | Vote and Type | Existing Wording | Proposed Wording | Ballot Comment | Comment grouping | Disposition | "Disposition Comment or Retract/Withdraw details" |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 118 | 2.A | 2.A.75 | 79 | A-T | Any displayable (printable) ACSII characters (hexadecimal values between 20 and 7E, inclusive, or ASCII decimal values between 32 and 126), except the defined escape characters and defined delimiter characters. | Any displayable (printable) ASCII characters (hexadecimal values between 20 and 7E, inclusive, or ASCII decimal values between 32 and 126), except the defined escape characters and defined delimiter characters, are allowed. | This is a sentence fragment which contains no verb, and "ASCII" is misspelled. | InM-6 | persuasive | |||
| 119 | 2.A | 2.A.75 | 79 | NEG | Any displayable (printable) ACSII characters (hexadecimal values between 20 and 7E, inclusive, or ASCII decimal values between 32 and 126), except the defined escape characters and defined delimiter characters. | Any displayable (printable) characters are allowed based on the character set identified in MSH-18. For the default ASCII characters set this is hexadecimal values between 20 and 7E, inclusive, or decimal values between 32 and 126, except the defined escape characters and defined delimiter characters. For Unicode this is any code point with a Basic Type of Graphic; see The Unicode Standard section 2.4 <http://www.unicode.org/versions/Unicode9.0.0/ch02.pdf> for details. | ST values should no longer be limited to ASCII characters now that MSH-18 supports other character sets such as UNICODE UTF-8. | InM-7 | Persuasive |
- Pending input from submitter
| "Comment Number" | Ballot | Chapter | Section | Page # | Line # | Vote and Type | Existing Wording | Proposed Wording | Ballot Comment | Comment grouping | Disposition | "Disposition Comment or Retract/Withdraw details" |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 124 | Pub | 2.A | NEG | The descriptions and Usage Notes for CWE and CNE do not reflect the Vocabulary WG policies adopted since 2.8 around use of the second component (display text) of the coded triplets. | Pending Input from Submitter | Please provide the policy | ||||||
| 125 | Pub | 2.A | 2.a.13.5Value Set OID | NEG | The text reads in such a way that all CWE fields must be bound to an HL7 Table with a number; this is not true when OBX-5 is used to carry CWE type result values, and the value set OID is a non-HL7 value set. Thus the Meaningful Use guides are non-compliant to the usage defined in this paragraph. Must be fixed. | Pending Input from Submitter | Please provide wording |
TBD - Chapter 2.C
- Chapter 2.c Negatives
| "Comment Number" | Ballot | Chapter | Section | Page # | Line # | Vote and Type | Existing Wording | Proposed Wording | Ballot Comment | Comment grouping | Disposition | "Disposition Comment or Retract/Withdraw details" |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3 | Pub | 2C | NEG | Unfortunately, the instructions to the ballot reviewers were not included for Ch. 2C. Since the chapter is now automatically generated and has new format this lack of guidance places an undue burden on reviewers to guess at what is being requested from them. I would suggest re-balloting with the guidance included. | ||||||||
| 14 | 2C | Table 0206 | 153 | NEG | "where usedCH2, RXA-21, RXV-22, LCH-2, IAM-6, ARV-2, IN1-55" | Table 0206 is now used in ORC-35 | Persuasive with Mod | |||||
| 15 | 2C | Table 0950 | NEG | This table is missing - is new for 2.9 - from chapter 4 - section 10.2.1.25 (for ORC-25) | Persuasive | |||||||
| 16 | 2C | Table 0949 | NEG | This table is missing - is new for 2.9 - from chapter 4 - section 10.2.1.16 (for ORC-16) | Persuasive | |||||||
| 26 | Pub | 2C | Introduction | 1 | n/a | NEG | Not all readers will understand the difference between a Code System and a Value Set. The introduction should contain a discussion of these two concepts and how to use them and the data contained in the various tables in this chapter. Otherwise, people will misuse names and OIDs because they don't understand the difference. If HL7's approach to vocabulary is documented elsewhere, then a URL reference would be sufficient | |||||
| 67 | 2C | All | NEG | Suggest that the Effective Date uses HL7's DT format YYYYMMDD to avoid any confusion of what, e.g., 04.05.2000 may mean. | ||||||||
| 122 | Pub | 2C | NEG | The header information, explanation of new format, and table of contents is missing from the chapter. Seems like a possible editorial issue when the ballot was put together. | ||||||||
| 150 | Vocab | 2C | NEG | No change log provided | "The entire layout of this chapter got re-done and an introduction about that may be good to have in the final standard, but if not there at least for the balloters to look at that as well as a list of changes approved via harmonization should be called out in the front of the chapter during ballot - this will make folks more aware of the requirement to send changes to harmonization as well as highlight what specifically should be reviewed chapter 2C also has no page numbers, no header or footers" |
- Chapter 2.c Affirmative
| Comment Number | Ballot | Chapter | Section | Page # | Line # | Vote and Type | Existing Wording | Proposed Wording | Ballot Comment | Comment grouping | Disposition | Disposition Comment or Retract/Withdraw details |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 28 | Pub | 2C | Table 0950 | n/a | n/a | A-T | Table 0948 Coded Content | Table 0950 Coded Content | The title of the last table in this section references the wrong table number (0948 rather than 0950) | |||
| 29 | Pub | 2C | Table 0951 | n/a | n/a | A-T | 948 | 951 | The table number in the Table Metadata table references 0948 rather than 0951 | |||
| 35 | Pub | 2C | 0206 | 152, 153 | A-S | Description of the table 0206 should mention that this table is also used in ORC-35, OBR-55, IPC-10, BPX-22, BTX-21, DON-34, BUI-13, OBX-31, SPM-35, CSR-17, CTI-4, SHP-12, PAC-9 | ||||||
| 66 | 2C | ToC | A-T | ToC is missing. | ||||||||
| 152 | Vocab | 2C | 0948 | A-S | HL7-defined code system of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4) and the Target Information Instance (REL-5). | HL7-defined code system used in REL-2 of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4) and the Target Information Instance (REL-5). | ||||||
| 153 | Vocab | 2C | 0950 | A-T | Table 0948 Coded Content | Table 0950 Coded Content | In the table meta data Table is listed as 0948; should be 0950 | |||||
| 154 | Vocab | 2C | 0951 | A-T | In the table meta data Table is listed as 0948; should be 0951 | |||||||
| 155 | Vocab | 2C | 0951 | A-T | Table 0948 Coded Content | Table 0951 Coded Content |
