Submitted by nedragarrett_CDC on 2022-09-27
Submitted By: Sarah Gaunt / Lantana Consulting Group | |
---|---|
Data Element Information | |
Use Case Description(s) | |
Use Case Description | Electronic case reporting requires Patient identifier. |
Estimated number of stakeholders capturing, accessing using or exchanging | This data is exchanged as part of the extensive implementation of electronic case reporting in the US. Target is nationwide, currently 5400+ sites are reporting. There are between 56 and 2400 public health agencies using this data. Electronic case reporting is also cited in the Cares Act regulations. |
Link to use case project page | http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436; http://hl7.org/fhir/us/ecr/; |
Healthcare Aims |
|
Maturity of Use and Technical Specifications for Data Element | |
Applicable Standard(s) | FHIR US Core https://www.hl7.org/fhir/us/core/ |
Additional Specifications | https://www.hl7.org/fhir/us/core/ |
Current Use | Extensively used in production environments |
Supporting Artifacts |
This data is exchanged as part of the extensive implementation of electronic case reporting in the US. Target is nationwide, currently 5400+ sites are reporting. There are between 56 and 2400 public health agencies using this data. Electronic case reporting is also cited in the Cares Act regulations. http://hl7.org/fhir/us/ecr/; http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436 |
Number of organizations/individuals with which this data element has been electronically exchanged | 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 |
Electronic Case Reporting: Target is nationwide, currently 5400+ sites are reporting. There are between 56 and 2400 public health agencies using this data. |
Potential Challenges | |
Restrictions on Standardization (e.g. proprietary code) | None |
Restrictions on Use (e.g. licensing, user fees) | None |
Privacy and Security Concerns | No concerns over and above the typically privacy and security considerations associated with any health related data. |
Estimate of Overall Burden | This data element is straightforward in nature and should not present a large burden to implement provided the EHR system is capturing the data. |
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 2 - Used at scale in more than 2 different production environments |
Maturity - Current Exchange | Level 2 - Demonstrates exchange between 4 or more organizations with different EHR/HIT systems |
Breadth of Applicability - # Stakeholders Impacted | Level 2 - Used by a majority of patients, providers or events requiring its use |
Submitted by nedragarrett_CDC on 2022-09-29
CDC's comment on behalf of CSTE for USCDI v4
CSTE agrees with CDC's recommendation for this data element.