Difference between revisions of "P 569 make xAD7 required"
m |
m |
||
| Line 7: | Line 7: | ||
== Description == | == Description == | ||
Make XAD-7 Address Type required.. | Make XAD-7 Address Type required.. | ||
| − | == Disposition | + | == Disposition == |
Accepted by INM on motion by __/__ (00-00-00) | Accepted by INM on motion by __/__ (00-00-00) | ||
==Justification:== | ==Justification:== | ||
This is a resubmission of a portion of the original proposal #514 and is a joint proposal from Quest Diagnostics and Kaiser Permanente seeking to take full advantage of the structure of the XAD data type. The change we seek is to make XAD-7 Address Type component,required. This change eliminates the need for sequence-based interpretation. Currently a number of fields state that the first iteration must be the �primary address.� However, given the current values in table 0190, no realistic assumption can be made as to what might be construed as the primary address. There is no value �primary address.� | This is a resubmission of a portion of the original proposal #514 and is a joint proposal from Quest Diagnostics and Kaiser Permanente seeking to take full advantage of the structure of the XAD data type. The change we seek is to make XAD-7 Address Type component,required. This change eliminates the need for sequence-based interpretation. Currently a number of fields state that the first iteration must be the �primary address.� However, given the current values in table 0190, no realistic assumption can be made as to what might be construed as the primary address. There is no value �primary address.� | ||
Revision as of 15:46, 16 January 2008
This is a page of type Category:InM Open Action Items.
P514 Make XAD-7 Address Type required.
Sponsoring Person
Joann Larson
Description
Make XAD-7 Address Type required..
Disposition
Accepted by INM on motion by __/__ (00-00-00)
Justification:
This is a resubmission of a portion of the original proposal #514 and is a joint proposal from Quest Diagnostics and Kaiser Permanente seeking to take full advantage of the structure of the XAD data type. The change we seek is to make XAD-7 Address Type component,required. This change eliminates the need for sequence-based interpretation. Currently a number of fields state that the first iteration must be the �primary address.� However, given the current values in table 0190, no realistic assumption can be made as to what might be construed as the primary address. There is no value �primary address.�
