ContactPoint

General information

See HL7 ContactPoint for general information regarding the ContactPoint data type.

Scope and Usage

This profile defines how ContactPoint should be used to represent contact information for persons and personnel in Swedish healthcare contexts. It specifies which elements are mandatory, optional, or repeatable, and provides guidance on terminology bindings for system and use. The profile is intended for use in multiple FHIR resources that include contact details, such as Patient, Practitioner, Person, and RelatedPerson. It ensures consistent representation, supports validation, and promotes interoperability across systems and organizations.

Boundaries and Relationships

The profile focuses solely on communication channels and does not include names, addresses, or identifiers. ContactPoint entries may be associated with other demographic information via the containing resource (e.g., Patient.telecom or Practitioner.telecom).

In some resources the ContactPoint data type is found nested inside the HL7 ExtendedContactDetail data type, along with NPPRAddress. The ExtendedContactDetail data type allows for supplying the purpose of the contact detail which allows for more flexibility than the ContactPoint.use element.

Background and Context

The ContactPoint data type is widely used across healthcare and administrative resources in FHIR to standardize communication information. Standardizing its use in Sweden ensures that contact details are represented consistently in local, regional, and national systems, supporting data exchange, interoperability, and compliance with national guidelines. This profile builds on the core HL7 FHIR definition while adding guidance specific to Swedish healthcare practice, including requirements for cardinality, usage, and preferred communication channels.

Profile

NPPRContactPoint (ContactPoint)	C		ContactPoint	Element id ContactPoint Short description Details of a Technology mediated contact point (phone, fax, email, etc.) Definition Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. Data type ContactPoint Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2: A system is required if a value is provided. `value.empty() or system.exists()` nppr-telecom-phone-1: If telecom.system = #phone, value should follow format +46123456789 `value.matches('^\\+[1-9][0-9]+$') or system != 'phone'` nppr-telecom-url-1: If telecom.system = #url, value should follow valid format. Example: https://example.com `value.matches('(https?\|ftp)://(-\\.)?([^\\s/?\\.#-]+\\.?)+(/[^\\s])?$') or system != 'url'` nppr-telecom-email-1:* If telecom.system = #email, value should follow valid format Example: test@test.com `value.matches('^[\\w.-]{1,64}@(?!.{254})[\\w.-]+\\.[A-Za-z]{2,4}$') or system != 'email'` Mappings rim: n/a v2: XTN rim: TEL servd: ContactPoint
id		0..1	string	There are no (further) constraints on this element Element id ContactPoint.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Conditions The cardinality or value of this element may be affected by these constraints: ele-1 Mappings rim: n/a
extension	C	0..*	Extension	There are no (further) constraints on this element Element id ContactPoint.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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 managable, 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. Comments 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. Data type Extension Slicing Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	S Σ C	1..1	codeBinding	Element id ContactPoint.system Short description phone \| fax \| email \| pager \| url \| sms \| other Definition Telecommunications form for contact point - what communications system is required to make use of the contact. Comments Note that FHIR strings SHALL NOT exceed 1,048,576 (10241024) characters in size Data type* code Binding Telecommunications form for contact point. ContactPointSystem (required) Conditions The cardinality or value of this element may be affected by these constraints: cpt-2 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: XTN.3 rim: ./scheme servd: ./ContactPointType
value	S Σ C	1..1	string	There are no (further) constraints on this element Element id ContactPoint.value Short description The actual contact point details Definition The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data type string Conditions The cardinality or value of this element may be affected by these constraints: cpt-2 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: XTN.1 (or XTN.12) rim: ./url servd: ./Value
use	S Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id ContactPoint.use Short description home \| work \| temp \| old \| mobile - purpose of this contact point Definition Identifies the purpose for the contact point. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data type code Binding Use of contact point. ContactPointUse (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: XTN.2 - but often indicated by field rim: unique(./use) servd: ./ContactPointPurpose
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition 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. Comments 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. Data type positiveInt Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: n/a
period	S Σ C	1..1	Period	There are no (further) constraints on this element Element id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower or equal value than end `start.hasValue().not() or end.hasValue().not() or (start.lowBoundary() <= end.highBoundary())` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: N/A rim: ./usablePeriod[type="IVL<TS>"] servd: ./StartDate and ./EndDate
id		0..1	string	There are no (further) constraints on this element Element id ContactPoint.period.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Conditions The cardinality or value of this element may be affected by these constraints: ele-1 Mappings rim: n/a
extension	C	0..*	Extension	There are no (further) constraints on this element Element id ContactPoint.period.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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 managable, 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. Comments 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. Data type Extension Slicing Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
start	S Σ C	1..1	dateTime	There are no (further) constraints on this element Element id ContactPoint.period.start Short description Starting time with inclusive boundary Definition The start of the period. The boundary is inclusive. Comments If the low element is missing, the meaning is that the low boundary is not known. Data type dateTime Conditions The cardinality or value of this element may be affected by these constraints: per-1 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: DR.1 rim: ./low
end	S Σ C	0..1	dateTime	There are no (further) constraints on this element Element id ContactPoint.period.end Short description End time with inclusive boundary, if not ongoing Definition The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. Comments The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. Meaning when missing If the end of the period is missing, it means that the period is ongoing Data type dateTime Conditions The cardinality or value of this element may be affected by these constraints: per-1 Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: DR.2 rim: ./high

ContactPoint
Short	Details of a Technology mediated contact point (phone, fax, email, etc.)
Definition	Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
Cardinality	0..*
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2: A system is required if a value is provided. `value.empty() or system.exists()` nppr-telecom-phone-1: If telecom.system = #phone, value should follow format +46123456789 `value.matches('^\\+[1-9][0-9]+$') or system != 'phone'` nppr-telecom-url-1: If telecom.system = #url, value should follow valid format. Example: https://example.com `value.matches('(https?\|ftp)://(-\\.)?([^\\s/?\\.#-]+\\.?)+(/[^\\s])?$') or system != 'url'` nppr-telecom-email-1:* If telecom.system = #email, value should follow valid format Example: test@test.com `value.matches('^[\\w.-]{1,64}@(?!.{254})[\\w.-]+\\.[A-Za-z]{2,4}$') or system != 'email'`
Mappings	rim: n/a v2: XTN rim: TEL servd: ContactPoint
ContactPoint.id
Short	Unique id for inter-element referencing
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0..1
Type	string
Conditions	The cardinality or value of this element may be affected by these constraints: ele-1
Mappings	rim: n/a
ContactPoint.extension
Short	Additional content defined by implementations
Definition	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 managable, 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.
Cardinality	0..*
Type	Extension
Alias	extensions, user content
Comments	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.
Slicing	Unordered, Open, by url(Value) Extensions are always sliced by (at least) url
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
ContactPoint.system
Short	phone \| fax \| email \| pager \| url \| sms \| other
Definition	Telecommunications form for contact point - what communications system is required to make use of the contact.
Cardinality	1..1
Type	code
Binding	Telecommunications form for contact point. ContactPointSystem (required)
Must Support	True
Summary	True
Comments	Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
Conditions	The cardinality or value of this element may be affected by these constraints: cpt-2
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: XTN.3 rim: ./scheme servd: ./ContactPointType
ContactPoint.value
Short	The actual contact point details
Definition	The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
Cardinality	1..1
Type	string
Must Support	True
Summary	True
Requirements	Need to support legacy numbers that are not in a tightly controlled format.
Comments	Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Conditions	The cardinality or value of this element may be affected by these constraints: cpt-2
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: XTN.1 (or XTN.12) rim: ./url servd: ./Value
ContactPoint.use
Short	home \| work \| temp \| old \| mobile - purpose of this contact point
Definition	Identifies the purpose for the contact point.
Cardinality	0..1
Type	code
Binding	Use of contact point. ContactPointUse (required)
Must Support	True
Modifier	True
Summary	True
Requirements	Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
Comments	Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: XTN.2 - but often indicated by field rim: unique(./use) servd: ./ContactPointPurpose
ContactPoint.rank
Short	Specify preferred order of use (1 = highest)
Definition	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.
Cardinality	0..1
Type	positiveInt
Summary	True
Comments	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.
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: n/a
ContactPoint.period
Short	Time period when the contact point was/is in use
Definition	Time period when the contact point was/is in use.
Cardinality	1..1
Type	Period
Must Support	True
Summary	True
Comments	A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1: If present, start SHALL have a lower or equal value than end `start.hasValue().not() or end.hasValue().not() or (start.lowBoundary() <= end.highBoundary())`
Mappings	rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: N/A rim: ./usablePeriod[type="IVL<TS>"] servd: ./StartDate and ./EndDate
ContactPoint.period.id
Short	Unique id for inter-element referencing
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0..1
Type	string
Conditions	The cardinality or value of this element may be affected by these constraints: ele-1
Mappings	rim: n/a
ContactPoint.period.extension
Short	Additional content defined by implementations
Definition	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 managable, 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.
Cardinality	0..*
Type	Extension
Alias	extensions, user content
Comments	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.
Slicing	Unordered, Open, by url(Value) Extensions are always sliced by (at least) url
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
ContactPoint.period.start
Short	Starting time with inclusive boundary
Definition	The start of the period. The boundary is inclusive.
Cardinality	1..1
Type	dateTime
Must Support	True
Summary	True
Comments	If the low element is missing, the meaning is that the low boundary is not known.
Conditions	The cardinality or value of this element may be affected by these constraints: per-1
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: DR.1 rim: ./low
ContactPoint.period.end
Short	End time with inclusive boundary, if not ongoing
Definition	The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
Cardinality	0..1
Type	dateTime
Must Support	True
Summary	True
Comments	The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
Meaning when missing	If the end of the period is missing, it means that the period is ongoing
Conditions	The cardinality or value of this element may be affected by these constraints: per-1
Constraints	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: DR.2 rim: ./high

<id value="NPPRContactPoint" />
<url value="http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint" />
<name value="NPPRContactPoint" />
<status value="active" />
<description value="Profile for expressing telecom details with valid value formats" />
<fhirVersion value="5.0.0" />
<kind value="complex-type" />
<abstract value="false" />
<type value="ContactPoint" />
<baseDefinition value="http://hl7.org/fhir/StructureDefinition/ContactPoint" />
<derivation value="constraint" />
<differential>
<element id="ContactPoint">
<path value="ContactPoint" />
<constraint>
<key value="nppr-telecom-phone-1" />
<severity value="warning" />
<human value="If telecom.system = #phone, value should follow format +46123456789" />
<expression value="value.matches('^\\+[1-9][0-9]+$') or system != 'phone'" />
<source value="http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint" />
</constraint>
<constraint>
<key value="nppr-telecom-url-1" />
<severity value="warning" />
<human value="If telecom.system = #url, value should follow valid format. Example: https://example.com" />
<expression value="value.matches('(https?|ftp)://(-\\.)?([^\\s/?\\.#-]+\\.?)+(/[^\\s]*)?$') or system != 'url'" />
<source value="http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint" />
</constraint>
<constraint>
<key value="nppr-telecom-email-1" />
<severity value="warning" />
<human value="If telecom.system = #email, value should follow valid format Example: test@test.com" />
<expression value="value.matches('^[\\w.-]{1,64}@(?!.{254})[\\w.-]+\\.[A-Za-z]{2,4}$') or system != 'email'" />
<source value="http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint" />
</constraint>
</element>
<element id="ContactPoint.system">
<path value="ContactPoint.system" />
<min value="1" />
<mustSupport value="true" />
<binding>
<strength value="required" />
<valueSet value="http://hl7.org/fhir/ValueSet/contact-point-system" />
</binding>
</element>
<element id="ContactPoint.value">
<path value="ContactPoint.value" />
<min value="1" />
<mustSupport value="true" />
</element>
<element id="ContactPoint.use">
<path value="ContactPoint.use" />
<mustSupport value="true" />
</element>
<element id="ContactPoint.period">
<path value="ContactPoint.period" />
<min value="1" />
<mustSupport value="true" />
</element>
<element id="ContactPoint.period.start">
<path value="ContactPoint.period.start" />
<min value="1" />
<mustSupport value="true" />
</element>
<element id="ContactPoint.period.end">
<path value="ContactPoint.period.end" />
<mustSupport value="true" />
</element>
</differential>

</StructureDefinition>

{

"resourceType": "StructureDefinition",
"id": "NPPRContactPoint",
"url": "http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint",
"name": "NPPRContactPoint",
"status": "active",
"description": "Profile for expressing telecom details with valid value formats",
"fhirVersion": "5.0.0",
"kind": "complex-type",
"abstract": false,
"type": "ContactPoint",
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/ContactPoint",
"derivation": "constraint",
"differential": {
"element": [
{
"id": "ContactPoint",
"path": "ContactPoint",
"constraint": [
{
"key": "nppr-telecom-phone-1",
"severity": "warning",
"human": "If telecom.system = #phone, value should follow format +46123456789",
"expression": "value.matches('^\\\\+[1-9][0-9]+$') or system != 'phone'",
"source": "http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint"
},
{
"key": "nppr-telecom-url-1",
"severity": "warning",
"human": "If telecom.system = #url, value should follow valid format. Example: https://example.com",
"expression": "value.matches('(https?|ftp)://(-\\\\.)?([^\\\\s/?\\\\.#-]+\\\\.?)+(/[^\\\\s]*)?$') or system != 'url'",
"source": "http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint"
},
{
"key": "nppr-telecom-email-1",
"severity": "warning",
"human": "If telecom.system = #email, value should follow valid format Example: test@test.com",
"expression": "value.matches('^[\\\\w.-]{1,64}@(?!.{254})[\\\\w.-]+\\\\.[A-Za-z]{2,4}$') or system != 'email'",
"source": "http://electronichealth.se/fhir/NPPR/StructureDefinition/NPPRContactPoint"
}
]
},
{
"id": "ContactPoint.system",
"path": "ContactPoint.system",
"min": 1,
"mustSupport": true,
"binding": {
"strength": "required",
"valueSet": "http://hl7.org/fhir/ValueSet/contact-point-system"
}
},
{
"id": "ContactPoint.value",
"path": "ContactPoint.value",
"min": 1,
"mustSupport": true
},
{
"id": "ContactPoint.use",
"path": "ContactPoint.use",
"mustSupport": true
},
{
"id": "ContactPoint.period",
"path": "ContactPoint.period",
"min": 1,
"mustSupport": true
},
{
"id": "ContactPoint.period.start",
"path": "ContactPoint.period.start",
"min": 1,
"mustSupport": true
},
{
"id": "ContactPoint.period.end",
"path": "ContactPoint.period.end",
"mustSupport": true
}
]
}

}

Constraints

Path	Id	Grade	Details	Expression
ContactPoint	nppr-telecom-phone-1	warning	If telecom.system = #phone, value should follow format +46123456789	value.matches('^\\+[1-9][0-9]+$') or system != 'phone'
ContactPoint	nppr-telecom-url-1	warning	If telecom.system = #url, value should follow valid format. Example: https://example.com	value.matches('(https?\|ftp)://(-\\.)?([^\\s/?\\.#-]+\\.?)+(/[^\\s]*)?$') or system != 'url'
ContactPoint	nppr-telecom-email-1	warning	If telecom.system = #email, value should follow valid format Example: test@test.com	value.matches('^[\\w.-]{1,64}@(?!.{254})[\\w.-]+\\.[A-Za-z]{2,4}$') or system != 'email'

Terminology Bindings

Path	Strength	ValueSet
ContactPoint.system	required	http://hl7.org/fhir/ValueSet/contact-point-system

Examples

Patient with contact details

Person with link reference

Practitioner that has a prescriber code

Practitioner role that expires

RelatedPerson with structured address