Data Element
Provider Reported Toxicity Value
Description

For each Cancer Patient - Provider Reported Toxicity record the Toxicity Value corresponding to the Toxicity Measure specified indicates the severity of the toxicity using the standardized table. specifies what value is measured. For example if CTCAE v5.0 (https://ctep.cancer.gov/protocoldevelopment/electronic_applications/doc…) the values in the standardized set are 0,1,2,3,4,5

The AAPM Operational Ontology for Radiation Oncology ( https://aapmbdsc.azurewebsites.net) identified this as a high priority element supporting patient care, outcomes research and public policy
Submitted By: Charles Mayo / University of Michigan
Data Element Information
Use Case Description(s)
Use Case Description Toxicity assessed by a care provider. In radiation oncology a primary objective in treatments is balancing radiation dose to target volumes (probability of cure) against radiation damage to near by healthy tissues (probability of toxicity. Longitudinal measures of toxicity using standardized scales (e.g. CTCAE v5.0 https://ctep.cancer.gov/protocoldevelopment/electronic_applications/docs/CTCAE_v5_Quick_Reference_8.5x11.pdf) are recorded as part of routine care and followup to document what was achieved vs what was intended.
Estimate the breadth of applicability of the use case(s) for this data element All
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) Common Terminology Criteria for Adverse Events
https://ctep.cancer.gov/protocoldevelopment/electronic_applications/docs/CTCAE_v5_Quick_Reference_8.5x11.pdf
Additional Specifications https://ctep.cancer.gov/protocoldevelopment/electronic_applications/docs/CTCAE_v5_Quick_Reference_8.5x11.pdf
Current Use Extensively used in production environments
Supporting Artifacts Standard element in EPIC flow sheets
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns None
Estimate of Overall Burden Minimal. It is routinely captured in EHR's such as EPIC and ARIA
Other Implementation Challenges None
ONC Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
Evaluation Comment Represents a subset of the more generally applicable Problems or Encounter Diagnosis data elements, thus a narrower breadth of applicability

Comment

Log in or register to post comments