| Submitted By: Dave Shekhar | |
|---|---|
| Data Element Information | |
| Use Case Description(s) | |
| Use Case Description | This data element is of extreme interest to Next of Kin/Related Parties and of high value to Care Team (needed for revised Care Plan) and would immensely help with timely and seamless Transition and Coordination of Care between different settings and care givers. |
| Estimated number of stakeholders capturing, accessing using or exchanging | 8+. Multiple stakeholders, including PCP, Care Manager, Inpatient facilities, LTC facility, SNF, Labs, Radiology centers, ED. |
| Supporting Attachments |
Terminal Illness Status.txt |
| Healthcare Aims |
|
| Maturity of Use and Technical Specifications for Data Element | |
| Applicable Standard(s) | Terminal illness (Code 300936002) SNOMED code. https://www.hipaaspace.com/medical_billing/coding/snomed/300936002 https://www.findacode.com/snomed/162607003--terminal-illness-early-stage.html https://build.fhir.org/ig/cqframework/opioid-cds-r4/ValueSet-limited-life-expectancy-conditions.html https://www.hipaaspace.com/medical_billing/coding/snomed/300936002 |
| Additional Specifications | CDC Opioid Prescribing Support Implementation Guide |
| Current Use | In limited use in production environments |
| Supporting Artifacts |
CDC : Opioid Prescribing Support Implementation Guide https://build.fhir.org/ig/cqframework/opioid-cds-r4/ValueSet-limited-life-expectancy-conditions.html https://build.fhir.org/ig/cqframework/opioid-cds-r4/index.html |
| Number of organizations/individuals with which this data element has been electronically exchanged | 2-3 |
| Supporting Artifacts |
Please note: Not aware of exact number of Prod environments for CDC Opioid Prescribing Support Implementation Guide https://build.fhir.org/ig/cqframework/opioid-cds-r4/ValueSet-limited-life-expectancy-conditions.html |
| Potential Challenges | |
| Restrictions on Standardization (e.g. proprietary code) | No restrictions. Part of SNOMED-CT. |
| Restrictions on Use (e.g. licensing, user fees) | License required to use SNOMED-CT codes which is already procured by NLM. |
| Privacy and Security Concerns | No concerns. This data element should be encouraged to be exchanged. |
| Estimate of Overall Burden | Minimal as other initiates like Cures Act, FHIR R4 mandates, CMS-9115 etc already faciliates lot of ground and foundation work. |
| Other Implementation Challenges | No challenge to implementation. Aligns with PI and other ONC and CMS mandates. |
| 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 | Level 1/2 - Must be represented by a vocabulary standard or an element of a published technical specification |
| Maturity - Current Use | Level 1 - Used in limited production environments, 1 or 2 different systems |
| Maturity - Current Exchange | Level 1 - Demonstrates exchange between 2 or 3 organizations with different EHR/HIT systems |
| Breadth of Applicability - # Stakeholders Impacted | Level 1 - Used by many, but not most, patients, providers or events requiring its use |
| Evaluation Comment | This data element is evaluated at Level 1 given its somewhat limited extent of use and exchange, as well as it's limited use in primarily in end of life care. Of note, this data element could be included in other existing data elements such as Functional Status or Problems. |
Comment