This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Datatypes R2 Issue 57"

From HL7Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
== Introduction ==
 
== Introduction ==
  
 +
original motion from MnM:
  
? backward compatible.
+
To ease the adoption of HL7 v3, MnM recommends INM to add “useCode” to II.  This would identify the intended scope/purpose/use of the identifier.  Example concepts to be included:
 +
* Issued by scoper/author
 +
* Verified by scoper/author
 +
* Used by scoper/author
 +
*
 +
* Non-player specific
 +
*
 +
* Real-world id
 +
* Record id
 +
* Version-specific (snapshot)
 +
* View id
 +
*
 +
* Reference
 +
* Definitional
 +
 
 +
MnM would like to participate in identifying requirements, appropriate contents, definitions and usage guidelines
 +
 
 +
Default values will be set to make the attribute backwards compatible
  
 
== Discussion ==
 
== Discussion ==

Revision as of 04:54, 16 May 2006

Data Types Issue 57: II.useCode

Introduction

original motion from MnM:

To ease the adoption of HL7 v3, MnM recommends INM to add “useCode” to II. This would identify the intended scope/purpose/use of the identifier. Example concepts to be included:

  • Issued by scoper/author
  • Verified by scoper/author
  • Used by scoper/author
  • Non-player specific
  • Real-world id
  • Record id
  • Version-specific (snapshot)
  • View id
  • Reference
  • Definitional

MnM would like to participate in identifying requirements, appropriate contents, definitions and usage guidelines

Default values will be set to make the attribute backwards compatible

Discussion

Links

Back to Data Types R2 issues