The metadata, or extra information about data, regarding who created the data and when it was created.

Data Element
Author Credential(s)
Description

Author Credential(s), in context of action taken and/or in context of USCDI dataset or data element authorship. Should allow credentials such as MD, DO, RN, DDS, PharmD...

Provenance set includes the who, what, when, where and why as metadata for USCDI data classes and data elements. Author Credential(s) are part of “who”.

Author Credential(s) must be associated with each USCDI dataset or data element that has a unique provenance set. Occurs when data is originated (captured, collected or sourced), updated, verified, attested, transformed.

Note that Author Credential(s) are intrinsic to what the source EHR/HIT system already knows, thus it does not require extra data collection (burden) by the clinician or other end user.
Submitted By: Gary Dickinson / EHR Standards Consulting
Data Element Information
Rationale for Separate Consideration Author Credential(s) are crucial to identify/ensure qualification and authority for actions taken and/or authorship of specific data classes or data elements. It offers essential assurance for transparency, accountability, trust, traceability and data in
Use Case Description(s)
Use Case Description All use cases (including health data/record exchange) where essential assurance of transparency, accountability, trust, traceability and data integrity is required.
Estimate the breadth of applicability of the use case(s) for this data element Any/all stakeholders for any/all use cases.
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • 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) N/A
Additional Specifications N/A
Current Use Extensively used in production environments
Supporting Artifacts FHIR Core Release 4.0.1 – Record Lifecycle Event Implementation Guide
ISO 21089:2018 – Trusted End-to-End Information Flows
ISO/HL7 10781 – Electronic Health Record System Functional Model, Release 2.1

http://hl7.org/fhir/ehrsrle/ehrsrle.html
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns None. In fact enables health data/record audit events and audit logs (audit trails).
• Who did what when where and why (actions taken)
• Who documented what when where and why (health record entries)
Estimate of Overall Burden As stated previously, most all of the submitted Provenance elements are intrinsic to what the source EHR/HIT system already knows, thus will not require extra data collection (burden) by the clinician or other end user.
Other Implementation Challenges The usual resistance from certain stakeholders – those who believe Provenance is unnecessary – after all, who would believe that transparency, accountability, assurance, traceability and data integrity are essential/integral to trusted health data/record management and use?
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 0 - Data element is not represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 0 - Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
Criterion #3
Maturity - Current Exchange		 Level 0 - Data element is electronically exchanged in limited environments, such as connectathons or pilots.
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.

Comment

Submitted by gldickinson on

Missing Part of the Description

Note that the first sentence of the Author Credential description is missing.  It should read:  

Author Credential(s), in context of action taken and/or in context of USCDI dataset or data element authorship.  Should allow credentials such as MD, DO, RN, DDS, PharmD...

Log in or register to post comments