Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.

Data Element
Individual Administering Vital Signs
Description

Identify the role of the individual taking the vital signs, differentiating between inputs that are from a care team member, patient or family/caregiver, as separate from an automated device or home monitoring system.
Submitted By: Tayler Williams / American Medical Informatics Association (AMIA)
Data Element Information
Use Case Description(s)
Use Case Description ONC should consider adding elements to identify the role of the individual taking the vital signs, differentiating between inputs that might be from a care team member, or patient or family/caregiver, as separate from an automated device or home monitoring system. By adding Individual Administering Vital Signs data element, would keep data quality paramount when following an individual's journey of care.
Estimate the breadth of applicability of the use case(s) for this data element This use case would apply to all health organizations administering vital signs, and potentially the patient themselves and caregivers. Also, this would apply to automated devices (e.g. wearables tracking heart rate, at home blood pressure monitors) tracking vital signs.
ONC Priority
  • Address public health interoperability needs of reporting, investigation, and emergency response
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) For care team members: Examples include but are not limited to National Provider Identifier (NPI) and National Council of State Boards of Nursing Identifier (NCSBN ID).

For FDA approved devices: FDA Unique Device Identification (UDI) System
Additional Specifications N/A
Current Use (Level 2) Captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) There could be restrictions on the standardization of this data element and class with potential use of proprietary code used by an EHR.
Restrictions on Use (e.g. licensing, user fees) There could be restrictions on the use of this data element and class with potential user fees and associated costs for reporting the use of medical devices.
Privacy and Security Concerns Medical data used by an individual and health care organization contains sensitive information and should be held to a standard of privacy for health care and only securely transferred.
Estimate of Overall Burden There could be a burden of time for health systems that do not currently capture the individual or device that administers vital signs of the patient. The EHR systems could be burdened in developing software to allow the ability to capture this information.
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 This data element represents a specialized use or subset of the data elements that make up the Care Team Member(s) data class in USCDI v4.

Comment

Log in or register to post comments