Submitted by EmoryHealthcare on 2023-09-20
Laboratory Data Class - L2 Data Elements as of 9.20.2023
- Emory Healthcare submits its support for the inclusion of all Data Elements currently listed as Level 2 under the Laboratory data class in draft USCDI v5.
- Emory Healthcare performs both clinical pathology and anatomic pathology testing to support patient care. While the Laboratory data class, with the inclusion of the Level 2 data elements, includes the information necessary to paint a comprehensive picture of clinical pathology testing, Emory Healthcare recommends ONC work to provide clarity on the appropriate documentation of anatomic pathology reports or narratives within USCDI.
Submitted by Riki Merrick on 2023-09-20
APHL supports elevation of Level 2 data elements
APHL supports elevation of these data elements:
#1 Test Kit Unique Identifier (https://www.healthit.gov/isa/taxonomy/term/3731/level-2): it would be necessary for the EHR-s to support collection of this data element, when it is provided; if EHR-s cannot retain this data element then it will not be available to downstream systems for use in research or by public health for emergency preparedness.
#2 Laboratory Test/Panel Code (https://www.healthit.gov/isa/taxonomy/term/2431/level-2): It is helpful to understand the clinical context for the results and one way is to understand how they were ordered - also this is a CLIA required data element (§493.1291(c)(4)). LOINC should be used to represent the order code, when an appropriate code exists (for the lab workflow the local code is the important element, as that is the test that the authorized requesting provider is asking for) - it should be codes of type 1 (Laboratory), where the Order vs. Observation is 'Order only' or 'Both'.
#3 Accession number (https://www.healthit.gov/isa/taxonomy/term/3716/level-2): This data element is also a CLIA required element (§493.1276 (a)), and it is probably especially important to have it identified as such, since what the lab uses as its accession number varies by lab,so this identifier is used as the primary key to locate all data that belongs to this specimen. To support communication between provider (EHR-s, which is patient centric) and lab (LIS, which is specimen-centric) and between lab and public health agency (Sureveillance system that receives reports from both EHR-s and LIS) this identifier is very important. It must be stressed, that this identifier should be unique within the assigning authority and not reused over time (though that may still be a practice in some labs).
For these three elements reconciliation needs to happen, but it is unclear what the USCDI definition will be, since only the link to the submission currently defines the element:
Laboratory results: date and timestamps (https://www.healthit.gov/isa/taxonomy/term/2426/level-2): For laboratory the following date/timestamps should be considered:
#1 Specimen Collection Date/time = Clinically relevant time = observation date/time, a CLIA required element (42 CFR 493.1241 (c) (6)) - this date/timestamp provides the temporal context for the result in relation to the patient's disease phase for example and is also needed for trending of result over longer periods of time; This cannot be the same as procedure date, because in most cases the specimen collection is not separately tracked as a procedure, and even if it was it's not included in the data exchange with the lab (on the order or result), so it would need to be easily identifiable in the EHR-s as the specimen collection date/time.
#2 Results/Report/Update date/time, a CLIA required element (§493.1291(c)(3)) - which can be one of several date/times tracked in the LIS: the date/time the result is produced by the analyzer (this is more often referred to as the test date/time), the date/time the result is verified by the supervisor (for each individual result) - this would be metadata on the Tests (https://www.healthit.gov/isa/taxonomy/term/676/uscdi-v4) element, the date/time the report is released, which often includes more than one result, so it might be the meta data associated with the Laboratory Test Panel Code (https://www.healthit.gov/isa/taxonomy/term/2431/level-2) or the Accession Number (https://www.healthit.gov/isa/taxonomy/term/3716/level-2).
#3 specimen received date/time = the date/time the specimen was received by the lab and is available for scessioning and processing - while this is not a CLIA element, it is the FIRST date the lab actually has control over, so could be used as proxy for the specimen collection date, should that ever not be obtainable
Laboratory Test Performed Date (https://www.healthit.gov/isa/taxonomy/term/2436/level-2) - the definition on this element is ambivalent: "The clinically relevant date/time of the observation. In the case of observations taken directly from a subject, it is the actual date and time the observation was obtained. In the case of a specimen-associated study, this field shall represent the date and time the specimen was collected or obtained." - Since this element is called Laboratory Test only the second part of this sentence applies, which basically means it is the same element as Specimen collection date/time (https://www.healthit.gov/isa/taxonomy/term/3256/level-2)
See prior comment: https://www.healthit.gov/isa/comment/5236