| Submitted By: Keith W. Boone
/ Audacious Inquiry
|
| Data Element Information |
| Use Case Description(s) |
| Use Case Description |
The provider telecom information can provide multiple methods to contact a provider (Direct address, phone number, FHIR endpoint, etc). Direct addresses or FHIR endpoints can be used to send notifications to the Patient's primary care or other (e.g., specialist) providers to meet CMS requirements for Notifications. |
| Estimate the breadth of applicability of the use case(s) for this data element
|
Many stakeholders already use Direct to capture this data, but do not communicate it to other stakeholders in messages they exchange with others. It is used to communicate, and required to enable communication under ONC 21st Century Cures regulations in 45 CFR 170.315(b)(1)(i) which references Direct and Direct Edge Protocols at 45 CFR 170.202(a)(2) and 202(d). Other telecom information is frequently used to contact providers by a number of individuals. |
| Healthcare Aims |
- Improving patient experience of care (quality and/or satisfaction)
- Improving the health of populations
- Improving provider experience of care
|
| Maturity of Use and Technical Specifications for Data Element |
| Applicable Standard(s) |
See standards and IGS selected in 45 CFR 170.202(a)(2) and 202(d)
https://www.law.cornell.edu/cfr/text/45/170.202
|
| Additional Specifications |
See standards and IGS selected in 45 CFR 170.202(a)(2) and 202(d), as well as https://www.hl7.org/fhir/practitioner-definitions.html#Practitioner.telecom
https://www.hl7.org/fhir/valueset-contact-point-system.html |
| Current Use |
This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders |
| Supporting Artifacts |
It is required for certification. See chart for 170.315(b)(1)(i) at the link below.
https://chpl.healthit.gov/#/charts
|
| Extent of exchange
|
5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders. |
| Supporting Artifacts |
This identifier (e-mail address) is available through numerous directories, including Direct Trust, SureScripts, and there is a place for it in the NPPES.
https://nppes.cms.hhs.gov/webhelp/nppeshelp/HEALTH%20INFORMATION%20EXCHANGE.html
|
| Potential Challenges |
| Restrictions on Standardization (e.g. proprietary code) |
None |
| Restrictions on Use (e.g. licensing, user fees) |
None |
| Privacy and Security Concerns |
The Direct Address is a communication address for a provider. It is publicly available information through NPPES. Other telecom information is generally also publicly available. |
| Estimate of Overall Burden |
Providers communicating with other agencies through HL7 V2 Messages (e.g., ADT), CCDA Documents, or FHIR APIs would need to add a few lines code to the components sending these to a) retrieve when known the providers Direct address (e.g., through a Provider Directory), and then add this information to the message or document communication. |
| Other Implementation Challenges |
The biggest challenge would be the fact that often the Provider Directory Lookup component is used in a separate part of the application, and may not be immediately accessible to the message creation component. |
on
Submitted by pwilson@ncpdp.org on
NCPDP Comment
Given the Code of Federal Regulations (CFR) is the official citation, NCPDP believes the link listed under the View Submission - Applicable Standards https://www.law.cornell.edu/cfr/text/45/170.202 should be updated to the direct CFR link https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-B/section-170.202.