This wiki has undergone a migration to Confluence found Here
Difference between revisions of "InM 29 R1 2a2c Reconciliation"
Jump to navigation
Jump to search
(Created page with "=InM Evote Cp 2a 2c=") |
|||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | =InM | + | ==TBD - Chapter 2.A== |
+ | === Persuasive with Mod=== | ||
+ | <table border="1"><tr><th>"Comment Number"</th><th>Ballot</th><th>Chapter</th><th>Section</th><th>Page #</th><th>Line #</th><th>Vote and Type</th><th>Existing Wording</th><th>Proposed Wording</th><th>Ballot Comment</th><th>Comment grouping</th><th>Disposition</th><th>"Disposition Comment or Retract/Withdraw details"</th></tr> | ||
+ | <tr><td>117</td><td></td><td>2.A</td><td>2.A.75</td><td>79</td><td></td><td>A-Q</td><td>String data is left justified (i.e., no leading blank space) with trailing blanks optional.</td><td></td><td>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?</td><td>InM-6</td><td>Persuasive with mod</td><td>Clarify Optional , add guidance to include /x20/ when you need to send only a blank.</td></tr> | ||
+ | <tr><td>124</td><td>Pub</td><td>2.A</td><td></td><td></td><td></td><td>NEG</td><td></td><td>CWE.2 - Descriptive Text is never required, but is recommended to be populated with either a text human-readable string published by the code system publisher from which the code in CWE.1 is drawn, or some other string which conveys a “reasonably synonymous” meaning with the semantics of the code. This may be a site or user defined string rather than one published with the code system, or may be one that is specified in an Implementation Guide; there are no hard and fast rules dictating its use. | ||
+ | </td><td></td><td></td><td>Persuasive with Mod</td><td>Please provide the policy</td></tr> | ||
+ | </table> | ||
+ | |||
+ | === Persuasive=== | ||
+ | <table border="1"><tr><th>"Comment Number"</th><th>Ballot</th><th>Chapter</th><th>Section</th><th>Page #</th><th>Line #</th><th>Vote and Type</th><th>Existing Wording</th><th>Proposed Wording</th><th>Ballot Comment</th><th>Comment grouping</th><th>Disposition</th><th>"Disposition Comment or Retract/Withdraw details"</th></tr> | ||
+ | <tr><td>118</td><td></td><td>2.A</td><td>2.A.75</td><td>79</td><td></td><td>A-T</td><td>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.</td><td>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.</td><td>This is a sentence fragment which contains no verb, and "ASCII" is misspelled.</td><td>InM-6</td><td>persuasive</td><td></td></tr> | ||
+ | <tr><td>119</td><td></td><td>2.A</td><td>2.A.75</td><td>79</td><td></td><td>NEG</td><td>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.</td><td>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.</td><td>ST values should no longer be limited to ASCII characters now that MSH-18 supports other character sets such as UNICODE UTF-8.</td><td>InM-7</td><td>Persuasive</td><td></td></tr> | ||
+ | </table> | ||
+ | |||
+ | === Pending input from submitter === | ||
+ | <table border="1"><tr><th>"Comment Number"</th><th>Ballot</th><th>Chapter</th><th>Section</th><th>Page #</th><th>Line #</th><th>Vote and Type</th><th>Existing Wording</th><th>Proposed Wording</th><th>Ballot Comment</th><th>Comment grouping</th><th>Disposition</th><th>"Disposition Comment or Retract/Withdraw details"</th></tr> | ||
+ | <tr><td>125</td><td>Pub</td><td>2.A</td><td>2.a.13.5Value Set OID</td><td></td><td></td><td>NEG</td><td></td><td></td><td>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.</td><td></td><td>Pending Input from Submitter</td><td>Please provide wording</td></tr> | ||
+ | </table> |
Latest revision as of 16:20, 8 March 2017
Contents
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. | |||
124 | Pub | 2.A | NEG | CWE.2 - Descriptive Text is never required, but is recommended to be populated with either a text human-readable string published by the code system publisher from which the code in CWE.1 is drawn, or some other string which conveys a “reasonably synonymous” meaning with the semantics of the code. This may be a site or user defined string rather than one published with the code system, or may be one that is specified in an Implementation Guide; there are no hard and fast rules dictating its use. | Persuasive with Mod | Please provide the policy |
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" |
---|---|---|---|---|---|---|---|---|---|---|---|---|
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 |