Others titles
- FHIR Contact Point Datatype
- Electronic Health Records Exchange Through FHIR
Keywords
- FHIR
- HL7
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
Contact Point
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.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
Description
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
About this Dataset
Data Info
Date Created | 2018-09-20 |
---|---|
Last Modified | 2023-03-26 |
Version | 5.0.0 |
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 |
Data Fields
Name | Description | Type | Constraints |
---|---|---|---|
Concept_Name | Name of the concept in the FHIR structure. | string | required : 1 |
Computer_Ready_Name | A 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. | string | required : 1 |
Type | The type the structure describes. | string | - |
Dollar_Ref | The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced. | string | - |
Description | A free text natural language description of the structure and its use. | string | - |
Items | The 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 | - |
Enum | The 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 | - |
Data Preview
Concept Name | Computer Ready Name | Type | Dollar Ref | Description | Items | Enum |
ContactPoint | id | #/definitions/string | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |||
ContactPoint | extension | array | 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 | |||
ContactPoint | system | Telecommunications form for contact point - what communications system is required to make use of the contact. | ||||
ContactPoint | _system | #/definitions/Element | Extensions for system | |||
ContactPoint | value | #/definitions/string | The actual contact point details | |||
ContactPoint | _value | #/definitions/Element | Extensions for value | |||
ContactPoint | use | Identifies the purpose for the contact point. | ||||
ContactPoint | _use | #/definitions/Element | Extensions for use | |||
ContactPoint | rank | #/definitions/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 | _rank | #/definitions/Element | Extensions for rank |