ContactPoint

Base StructureDefinition for ContactPoint Type: Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.

Schema

Elements

Name	Required	Type	Description
id		string	Unique id for inter-element referencing Details Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension		Extension[]	Additional content defined by implementations Details May 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
system		code	phone | fax | email | pager | url | sms | other Details Telecommunications form for contact point - what communications system is required to make use of the contact.
value		string	The actual contact point details Details The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
use		code	home | work | temp | old | mobile - purpose of this contact point Details Identifies the purpose for the contact point. Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
rank		positiveInt	Specify preferred order of use (1 = highest) Details 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. Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
period		Period	Time period when the contact point was/is in use Details Time period when the contact point was/is in use.