| Submitted By: Elizabeth Covington / University of Michigan | |
|---|---|
| Data Element Information | |
| Use Case Description(s) | |
| Use Case Description | The AAPM /ASTRO Operational Ontology for Radiation Oncology ( https://aapmbdsc.azurewebsites.net) identifies a prioritized set of data elements associated with radiation therapy, and these elements are specific to the radiation therapy prescription. The data elements of this class are generalizable across all disease sites e.g. prostate, breast, lung, gynecological, etc. High priority values are listed with this submission. |
| Estimated number of stakeholders capturing, accessing using or exchanging | All facilities that perform radiation therapy or facilities that provide care to patients that have received radiation therapy. |
| Healthcare Aims |
|
| Maturity of Use and Technical Specifications for Data Element | |
| Applicable Standard(s) | N/A |
| Additional Specifications | N/A |
| Current Use | Not currently captured or accessed with an organization |
| Number of organizations/individuals with which this data element has been electronically exchanged | 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 | These data elements are expected to reduce burden. Typically, radiation therapy prescription information is shared between facilities upon transfer of care. This data transfer is not standardized and can result in rework and multiple submission to ensure all relevant information is included. Including these standardized elements should improve and simplify data sharing. |
| ONC Evaluation Details Each submitted Data Element has been evaluated based on the following 4 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 |
|
|---|---|
| Maturity – Standards/Technical Specifications | Comment Level - May be represented by a vocabulary standard or an element of a published technical specification. |
| Maturity - Current Use | Comment Level - Used in limited test environments or pilots |
| Maturity - Current Exchange | Comment Level - Demonstrates limited exchange with external organizations, on same or different EHR/HIT systems |
| Breadth of Applicability - # Stakeholders Impacted | Comment Level - Used by few stakeholders, or for narrowly defined conditions or events |
Comment