ContactPoint
Overview
See also Examples, Detailed Descriptions, Mappings, Profiles and Extensions
Details for all kinds of technology-mediated contact points for a person or organization, including telephone, email, etc.
[%dt ContactPoint 12%]
If capturing a phone, fax or similar contact point, the value should be a properly formatted telephone number according to ITU-T E.123. However, this is frequently not possible due to legacy data and/or clerical practices when recording contact details. For this reason, phone, fax, pager, and email addresses are not handled as formal URLs. For other kinds of contact points, the system is "other" and the value SHOULD be a URL so that its use can be determined automatically. Typical URL schemes used in the value are http{s}: for web addresses, and URL schemes for various kinds of messaging systems. If the value is not a URL, then human interpretation will be required.
Constraints
[%dt.constraints ContactPoint%] [%tx ContactPoint%]
ContactPoint is used in the following places: [%dtusage ContactPoint%]
Elements
- ContactPoint.system [0..1]: code Telecommunications form for contact point - what communications system is required to make use of the contact
- ContactPoint.value [0..1]: string The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
- ContactPoint.use [0..1]: code Identifies the purpose for the contact point
- ContactPoint.rank [0..1]: positiveInt Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values
- ContactPoint.period [0..1]: Period Time period when the contact point was/is in use
Bindings
- ContactPoint.system:
ContactPointSystem| strength: code list | reference: #contact-point-system - ContactPoint.use:
ContactPointUse| strength: code list | reference: #contact-point-use
Modifiers
- ContactPoint.use: Is modifier
Requirements
- ContactPoint.value: Need to support legacy numbers that are not in a tightly controlled format
- ContactPoint.use: Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose
Comments
- ContactPoint.value: Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value
- ContactPoint.use: Applications can assume that a contact is current unless it explicitly says that it is temporary or old
- ContactPoint.rank: Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Ranks need not be unique. E.g. it's possible to have multiple contacts with rank=1. If the ranks have different systems or uses, this would be interpreted to mean "X is my most preferred phone number, Y is my most preferred email address" or "X is my preferred home email and Y is my preferred work email". If the system and use for equally-ranked contacts are the same, then the level of preference is equivalent for both repetitions. Ranks need not be sequential and not all repetitions must have a rank. For example, it's possible to have 4 contacts with ranks of 2, 5 and two with no rank specified. That would be interpreted to mean the first is preferred over the second and no preference stated for the remaining contacts.
Mappings
- ContactPoint.system: RIM Mapping: ./scheme
- ContactPoint.system: v2 Mapping: XTN.3
- ContactPoint.system: ServD Mapping: ./ContactPointType
- ContactPoint.value: RIM Mapping: ./url
- ContactPoint.value: v2 Mapping: XTN.1 (or XTN.12)
- ContactPoint.value: ServD Mapping: ./Value
- ContactPoint.use: RIM Mapping: unique(./use)
- ContactPoint.use: v2 Mapping: XTN.2 - but often indicated by field
- ContactPoint.use: ServD Mapping: ./ContactPointPurpose
- ContactPoint.rank: RIM Mapping: n/a
- ContactPoint.rank: v2 Mapping: n/a
- ContactPoint.period: RIM Mapping: ./usablePeriod[type="IVL<TS>"]
- ContactPoint.period: v2 Mapping: N/A
- ContactPoint.period: ServD Mapping: ./StartDate and ./EndDate