This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Datatypes R2 Issue 68"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
  
 
As Lloyd McKenzie suggested in a reply to my question, this will prevent variations from being invented to represent the same thing.
 
As Lloyd McKenzie suggested in a reply to my question, this will prevent variations from being invented to represent the same thing.
 +
 +
== Comment ==
 +
 +
there is a problem here. For datatypes R2, since W3C have deprecated
 +
the fax uri type - it's all the same protocol for making the connection - then
 +
we have added FAX as a use type (HL7 WGM May 2006). Adding x-text-tel is the wrong solution
 +
here for the same reason - it should be added to the use codes. (Grahame Grieve)
  
 
== Links ==
 
== Links ==
 
Back to [[Data Types R2 issues]]
 
Back to [[Data Types R2 issues]]

Revision as of 13:23, 8 September 2006

Data Types Issue 68: Text Telephone Number

Introduction

There is a business need within two NHS CFH domains to represent a number for a 'text telephone' (a telephone which is designed for use by the hearing-impaired).

Having posted a request for suggestions to the MnM list, it was suggested that the following format be used:

<telecom use="PUB" value="x-text-tel:01392251289"/>

I intend to follow this format and use the 'x-text-tel:' prefix, and I am proposing that this format be added to the TEL datatype in the next release of the specification.

As Lloyd McKenzie suggested in a reply to my question, this will prevent variations from being invented to represent the same thing.

Comment

there is a problem here. For datatypes R2, since W3C have deprecated the fax uri type - it's all the same protocol for making the connection - then we have added FAX as a use type (HL7 WGM May 2006). Adding x-text-tel is the wrong solution here for the same reason - it should be added to the use codes. (Grahame Grieve)

Links

Back to Data Types R2 issues