Id1.3.182.11.22
ref
lux-gh-
Effective Date2017‑11‑14 17:13:03
Statusdraft DraftVersion Label1.0
NameCDAtelecomDisplay NameCDA telecom
Description

The telecom element is used in different classes of the CDA-RMIM to provide contact data of persons and organizations. It is defined by the RFC 2806. 

Format conventions for telecom values

 

To be able to distinguish between different types of communications, the @value attribute must contain as a prefix the identifier of the communication scheme, e.g. “tel”, “mailto”, … followed by an “:” and the communication URL.

If telephone or fax numbers are provided (“tel:” or “fax:”), they should contain the country code for which this number is valid e.g. “+352, +49, +33, …”. If the country code is omitted, the number provided is assumed as a number valid for the country related to the realmCode (see 3.3.1), which must be “LU” for documents which are conformant to this specification.

So the general layout is: “<communication_scheme>:<URL>”

The different communication schemes which are supported shall be from value set: eSanté_URLScheme.

ClassificationCDA Header Level Template
Open/ClosedClosed (only defined elements are allowed)
Used by / Uses
Used by 2 transactions and 24 templates, Uses 0 templates
Used by as NameVersion
1.3.182.7.4.1.4.2Transactiondraft Send déclaration2018‑11‑14 16:42:24
1.3.182.7.6.1.4.6Transactiondraft Send MH2020‑10‑28 09:30:36
1.3.182.7.3.2.10.5Includedraft CDA AssignedEntity simple (1.0)2019‑11‑21 13:13:15
1.3.182.7.6.1.10.1Includedraft CDA author A22020‑05‑26 07:28:48
1.3.182.11.1.2Includedraft CDA AssignedEntity (1.0)2014‑10‑09 10:05:34
1.3.182.11.1.4Includedraft CDA author (1.0)2014‑10‑06 11:42:26
1.3.182.11.1.4.1Includedraft CDA author A1 (1.0)2018‑01‑16 11:14:50
1.3.182.11.1.7Includedraft CDA custodian (1.0)2014‑10‑09 10:08:39
1.3.182.11.1.10Includedraft CDA informationRecipient (1.0)2014‑10‑09 10:11:44
1.3.182.11.1.13Includedraft CDA Organization (1.0)2014‑10‑09 14:29:56
1.3.182.11.1.14Includedraft CDA participant (1.0)2014‑10‑09 10:21:56
1.3.182.11.1.16Includedraft CDA recordTarget (1.0)2014‑10‑08 16:45:14
1.3.182.11.1.16.1Includedraft CDA recordTarget A1 (1.0)2018‑01‑16 10:38:43
1.3.182.11.1.21Includedraft CDA RelatedEntity (1.0)2014‑10‑09 10:06:16
1.3.182.11.3.1.1Includedraft CDA recordTarget LAB (1.0)2018‑09‑21 11:39:42
1.3.182.11.3.1.2Includedraft CDA author LAB (1.0)2018‑09‑21 12:00:52
1.3.182.11.3.1.3Includedraft CDA custodian LAB (1.0)2018‑09‑21 12:28:32
1.3.182.11.3.1.4Includedraft CDA informationRecipient LAB (1.0)2018‑09‑25 19:01:06
1.3.182.11.3.1.5Includedraft CDA Organization LAB (1.0)2018‑09‑25 19:10:14
1.3.182.11.3.1.6Includedraft CDA AssignedEntity LAB (1.0)2018‑09‑25 19:15:07
1.3.182.11.3.1.9Includedraft CDA participant LAB (1.0)2018‑09‑25 19:44:41
1.3.182.11.10.3.14Includedraft eHDSI Author (Body)2018‑12‑18 11:38:21
1.3.182.11.12Includeactive Declaration Labo (Version1)2018‑11‑14 13:33:33
1.3.182.11.12Includedraft Declaration Labo (Version2)2020‑05‑05 08:04:02
1.3.182.11.14.1.1Includedraft CDA recordTarget A22020‑05‑26 06:35:46
1.3.182.11.15Includedraft eDocument MH (1.0)2020‑10‑28 08:15:42
Example
Example
<!-- Telephone number -->
<telecom value="tel:+352-12345" use="H"/><!-- E-mail -->
<!-- <telecom value="mailto:John.Doe@doe.com"/> -->
<!-- FTP -->
<!-- <telecom value="ftp://serveur/dossiermedicalpartagé/"/> -->
<!-- Unknown telecom value -->
<!-- <telecom nullFlavor="UNK" /> -->
ItemDTCardConfDescriptionLabel
hl7:telecom
CDAtdotsecom
@use
set_cs0 … 1 
 CONF
The value of @use shall be drawn from value set 1.3.182.10.28.1 eSante_TelecomAddressUse (DYNAMIC)
@value
st1 … 1R
 Variable letNamemyAttValue 
 Valuesubstring-before(@value,':') 
 Variable letNamemyAttCheck 
 Valuedistinct-values(doc('include/voc-1.3.182.10.29.1-DYNAMIC.xml')/*/valueSet/conceptList/concept[@code = $myAttValue]) 
 Schematron assertrolered error 
 testcount($myAttValue)=count($myAttCheck) 
 MessageValue must start with communication - scheme from value set eSanté_URLScheme