This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 57"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| − | + | This proposal is for a useCode on II. This idea was endorsed in principle by MnM (see motion below). | |
| + | |||
| + | == MnM Motion == | ||
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. See also the discussion around [[Types of Identifiers]]. Example concepts to be included: | 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. See also the discussion around [[Types of Identifiers]]. Example concepts to be included: | ||
Revision as of 08:42, 21 September 2006
Data Types Issue 57: II.useCode
Introduction
This proposal is for a useCode on II. This idea was endorsed in principle by MnM (see motion below).
MnM Motion
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. See also the discussion around Types of Identifiers. 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
see also Types of Identifiers
Discussion
Links
Back to Data Types R2 issues
