Data Element
Tobacco/Nicotine Quit Date
Submitted By: Anita walden / HL7 Common Clinical Registry Framework project
Data Element Information
Data Element Description The date the individual when they stopped nicotine consumption/use.
Business rule: If quit date is within the last 30 days there should be a full date. If not, partial dates are accepted, or if null look for Quit Age
Use Case Description(s)
Use Case Description Currently, smoking status is collected in a variety of formats across healthcare settings, making it difficult to accurately aggregate information within and across health systems. The current USCDI broadly indicates smoking as a data element but organizations need specific minimum basic information concerning smoking that should be consistently collected. For primary patient care situations, clinicians are interested in a general understanding of nicotine and smoking use rather than trying to obtain exact information that may be difficult for patients to accurately report for a practical purpose. It is critical to collect reliable tobacco/nicotine use from patients in a manner that is easy for them to recall and provide. For example, patients often don’t remember historical dates, but generally, remember the age when they first started using tobacco/nicotine products.

Tobacco/Nicotine use information should be available across all EHRs in a standard format and made available to additional stakeholders such as registry stewards for quality reporting. Currently, tobacco/nicotine use is captured in various formats making it difficult to aggregate and understand use across patient care settings. Not only does this increase the cost of data collection and sharing with stakeholders, but mapping data can lead to data quality issues and data reduction.
Registries are one of the major stakeholders, routinely collecting tobacco/nicotine information from provider settings. Standardizing these data elements should reduce data exchange costs, resources, and improve quality data collection from patients and quality reporting. This information was collected as part of the HL7 CIC Common Clinical Registry Framework Initiative in partnership with Duke University and the Pew project.

Estimate the breadth of applicability of the use case(s) for this data element All of the US healthcare systems and national quality registries could use these data elements if they are made available in EHR systems.
Link to use case project page https://www.hl7.org/ and https://dcri.org/registry-data-standards/
Use Case Description Researchers may also use Tobacco/Nicotine Use directly from healthcare settings. If data was collected in a standard format for all US patients this would increase interoperability and create the ability to accurately compare data across various entities. They can use this information as cohort identification for patient populations adding additional questions for research protocols.
Estimate the breadth of applicability of the use case(s) for this data element It is difficult to measure the number of stakeholders across the pharmaceutical and clinical research community.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) There are SNOMED and LOINC Codes for most of the data elements but new codes will be requested for eCigarette use.
http://bioportal.bioontology.org/ontologies/SNOMEDCT/?p=classes&conceptid=http%3A%2F%2Fpurl.bioontology.org%2Fontology%2FSNOMEDCT%2F365980008
Additional Specifications HL7 CCRF DAM, HL7 FHIR have some of these data elements and we are hoping to expand those to the list we are proposing.
HL7 US Core is available through EHR systems. Not sure of the number of organizations that are using HL7 US Core
https://www.hl7.org/fhir/us/core/StructureDefinition-us-core-smokingstatus.html
Current Use Not currently captured or accessed with an organization
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) There should not be any limitations because SNOMED and LOINC will be used
Restrictions on Use (e.g. licensing, user fees) No Restrictions in the US
Privacy and Security Concerns No privacy concerns
Estimate of Overall Burden Updating the HL7 US CORE to include these data elements will lower the burden of Providers who have and will implement HL7 FHIR. The downstream users of the information should experience cost savings and see improvements in data quality if the information is collected in a standard format directly from the patient.
Other Implementation Challenges The biggest challenge is getting EHR vendors to agree to standardize their data collection systems to use the standard. Downstream users such as Registry stewards would have to change their systems and agree to accept the Tobacco/Nicotine data elements directly from the EHR without mapping to a proprietary codelist.

Comment

Submitted by Spruitt on

This field is for general…

This field is for general comments on this specific data element. To submit new USCDI data classes and/or data elements, please use the USCDI ONDEC system: https://healthit.gov/ONDEC

Submitted by CDC_DSMH_WG on

Unified Comment from CDC

CDC considers this element to be high priority and strongly recommends its inclusion in the USCDI V3.

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB