Contact Point

$10 / year

Contact Point includes the details for all kinds of technology-mediated contact points for a person or organization, including telephone, email, etc. The Contact Point Systems are the telecommunications form for contact point that communications system is required to make use of the contact.

Complexity

If capturing a phone, fax or similar contact point, the value should be a properly formatted telephone number according to (International Telecommunication Union-Telecommunication (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 Universal Resource Locator (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.

The rank element can be used to specify a preference for the order in which a set of contacts is used. Contact Points with lower rank values are more preferred than those with higher rank values. Note that rank does not necessarily follow the order in which the contacts are represented in the instance.

Contact Point is used in the following places:
– Contact Detail
– Care Team
– Device
– Device Definition
– Endpoint
– Healthcare Service
– Insurance Plan
– Location
– Message Header
– Organization
– Organization Affiliation
– Patient
– Person
– Practitioner
– Practitioner Role
– Related Person
– Subscription

Date Created

2018-09-20

Last Modified

2019-11-01

Version

4.0.1

Update Frequency

Annual

Temporal Coverage

N/A

Spatial Coverage

United States

Source

John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements

N/A

Source Citation

N/A

Keywords

FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Contact Point Datatype, Electronic Health Records Exchange Through FHIR

NameDescriptionTypeConstraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.stringrequired : 1
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
EnumThe enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.string-
Concept NameComputer Ready NameTypeDollar RefDescriptionItemsEnum
ContactPointid#/definitions/stringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
ContactPointextensionarrayMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension there is a set of requirements that SHALL be met as part of the definition of the extension.{'$ref': '#/definitions/Extension'}
ContactPointsystemTelecommunications form for contact point - what communications system is required to make use of the contact.['phone' 'fax' 'email' 'pager' 'url'
ContactPoint_system#/definitions/ElementExtensions for system
ContactPointvalue#/definitions/stringThe actual contact point details in a form that is meaningful to the designated communication system (i.e. phone number or email address).
ContactPoint_value#/definitions/ElementExtensions for value
ContactPointuseIdentifies the purpose for the contact point.['home' 'work' 'temp' 'old' 'mobile']
ContactPoint_use#/definitions/ElementExtensions for use
ContactPointrank#/definitions/positiveIntSpecifies 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_rank#/definitions/ElementExtensions for rank
Related Data Packages