| Submitted By: Sanjeev Tandon on behalf of CDC / CDC | |
|---|---|
| Data Element Information | |
| Rationale for Separate Consideration | This may seem to be represented by the “Procedures” element. The specimen collection method differs from a procedure as it is not considered a procedure in the clinical workflow. |
| Use Case Description(s) | |
| Use Case Description | Specimen collection method is created at the provider side when a specimen is collected for laboratory testing. It may be captured in some EHRs during test order creation. It is exchanged with the laboratory as part of the order message. A proper test interpretation cannot be given for some test types without knowing the specimen collection method. Laboratories are required to receive this for certain tests as per CLIA requirement §493.1291(c)(5). |
| Estimate the breadth of applicability of the use case(s) for this data element | This use case applies to some types of testing that would impact all the laboratory professionals conducting and interpreting applicable laboratory tests. It impacts patient care and providers using those test interpretations to make decisions. These providers include all the doctors, nurses, and other medical professionals who order laboratory tests. |
| ONC Priority |
|
| Maturity of Use and Technical Specifications for Data Element | |
| Applicable Standard(s) | SNOMED CT® https://browser.ihtsdotools.org/?perspective=full&conceptId1=17636008&edition=MAIN/2023-09-01&release=&languages=en |
| Additional Specifications | This data element RE in LOI, LRI, ELR and FHIR R5. LOI - http://www.hl7.org/implement/standards/product_brief.cfm?product_id=152 LRI - http://www.hl7.org/implement/standards/product_brief.cfm?product_id=279 FHIR R5 - https://hl7.org/fhir/specimen-definitions.html#Specimen.collection.method |
| Current Use | (Level 2) Captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer |
| Extent of exchange | (Level 2) Between more than two production EHRs or other HIT modules using available interoperability standards |
| Potential Challenges | |
| Restrictions on Standardization (e.g. proprietary code) | None |
| Restrictions on Use (e.g. licensing, user fees) | None |
| Privacy and Security Concerns | None |
| Estimate of Overall Burden | This element is generated at the bedside and captured/ should be captured by the EHR. There are no calculations applicable. It should be communicated with the lab test order and will be used by the laboratory professional running and interpreting the test. Attempts to collect it do not impact the clinical workflow. |
| Other Implementation Challenges | A development burden is expected. |
Analysis of clinical specimens to obtain information about the health of a patient.
Data Element |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Specimen Collection Method
Description
This is the collection method of the specimen sent for laboratory testing. |
||||||||||||
|
||||||||||||
Comment