Patient Demographics

The ability to capture, track, and monitor expiration date (hospital, home, LTC, other).
Cause of death can be optional

Submitted By: Jeff Lyall / Cigna
Data Element Information
Use Case Description(s)
Use Case Description	1. Systematic awareness and data life cycle completeness in regards to a Patient records and data maintainers (i.e. Providers and Health Plans) 2. Meaningful analytic driven guidance relating to disease tracking, patient longevity, and population trends. 3. Population studies – include or exclude members based on living status from study criteria will have more accurate outcomes and or interventions 4. Bereavement considerations impacting family members. Payers could reduce member notification to member and family or better service survivors on next steps 5. Health Plans can reduce fraud and abuse by monitoring claim activity for deceased membership.
Estimated number of stakeholders capturing, accessing using or exchanging	>1M+ : This would be used by multiple entities (plans , providers, health proxies) for the individuals and for population health uses.
Use Case Description	Date of death is required to be captured in inpatient certified EHR systems as part of ONC's 2015 Certification
Estimated number of stakeholders capturing, accessing using or exchanging	All inpatient EHRs are required to capture date of death in their certified EHRs.
Link to use case project page	https://www.healthit.gov/test-method/demographics
Healthcare Aims	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)	Follow the DOB format
Additional Specifications	HL7 USCore Implementation Guide v3.1.0 and v3.1.1 (Errata release) both allow for capturing deceased as either a Boolean (yes/no) or the date of death in the Patient profile. (Reference Link) However, neither version of the USCore Implementation Guide state the element as a Must Support or required. USCore would need to bring the Patient profile up-to-date if the proposed Date of Death element is approved for USCDI v2.
Current Use	In limited use in production environments
Number of organizations/individuals with which this data element has been electronically exchanged	N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code)	N/A
Restrictions on Use (e.g. licensing, user fees)	N/A
Privacy and Security Concerns	Same security measure apply to this data element.
Estimate of Overall Burden	EMR capture expiration dates