Generated Narrative: StructureDefinition pca-practitioner-personal-contact-details Name Flags Card. Type Description & Constraints ContactPoint 0..* ContactPoint Details of a Technology mediated contact point (phone, email, etc.) #xD; system S 1..1 code phone | email Binding: PCA Restricted Contact Point System (required) #xD; value S 1..1 string The actual contact point details #xD; use S 1..1 code home Fixed Value: home #xD; Documentation for this format
This Contact Point data type profile enables sharing personal contact information (i.e. personal telephone and email address) of a practitioner, with their business partners, so that they can be contacted using those channels where appropriate.
Copyright © 2024 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.
Details of a Technology mediated contact point (phone, email, etc.)
Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
A system is required if a value is provided.
not(exists(f:value)) or exists(f:system)
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Telecommunications form for contact point - what communications system is required to make use of the contact.
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.
Need to support legacy numbers that are not in a tightly controlled format.
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.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one
Specify preferred order of use (1 = highest)
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.
Time period when the contact point was/is in use