| Literature DB >> 20805960 |
Neil R Kudler1, Liron Pantanowitz.
Abstract
BACKGROUND: Laboratory data account for the bulk of data stored in any given electronic medical record (EMR). To best serve the user, electronic laboratory data needs to be flexible and customizable. Our aim was to determine the various ways in which laboratory data get utilized by clinicians in our health system's EMR.Entities:
Keywords: Decision support; EMR; flowsheet; health maintenance tool; information system; laboratory
Year: 2010 PMID: 20805960 PMCID: PMC2929542 DOI: 10.4103/2153-3539.63824
Source DB: PubMed Journal: J Pathol Inform
Summary or laboratory data utilization in our EM
| Cerner Millennium tool | Availability of the tool | Utilization by clinicians | Positive features | Negative features |
|---|---|---|---|---|
| Flowsheets | All enterprise settings | All | Lab data can be viewed in multiple formats | Difficult to identify an ideal default setting to present data |
| Data can be easily sorted | Lengthy time to view large amounts of data | |||
| Data can be viewed during the time period set by the user | Need to scroll up and across screens to view large data sets | |||
| Graphs can be easily created for trending | Results can be missed | |||
| Customization of specialty flowsheets | Result details within small boxes may be hidden or truncated | |||
| Data can be printed directly from the EMR with reference ranges | Additional right-click required for some information (e.g. comments) | |||
| Flagging results is restricted to the use of symbols (e.g. H, L, ↓, ↑) and/or colors | ||||
| Second tier “discoverable” data may not get printed from the EMR | ||||
| Unable to import/store outside lab data within flowsheets | ||||
| Personal Inbox/EMR messaging | All enterprise settings | All | Secure communication between users | Limited adoption by users |
| Delivery of all results (lab, radiology, and ancillary) | Occasional difficulty identifying the correct provider to notify | |||
| Results are sent to the ordering provider | Results can be sent to the wrong clinician | |||
| Creation of reminders and messages to oneself or other users | Poorly formatted inbox can cause results to be lost or not seen | |||
| Forward capabilities of documents for review or co-signature | Irrelevant messages create noise | |||
| Ability to generate electronic consult requests | Messages require frequent review and can accumulate | |||
| High priority setting available | Limited user interface | |||
| Return receipt tools available | Result refusal process is suboptimal | |||
| Easy access to patient charts from inbox | Potential medicolegal liability for unread messages | |||
| Decision support tools | All enterprise settings | All | Identify drug–drug interactions | Workflow interruption |
| Identify any drug–condition interactions | May not be relevant in all situations | |||
| Therapeutic drug monitoring | Requires custom builds | |||
| Identify drug allergy prior to use | Manual management | |||
| “Alert fatigue” | ||||
| No distinction between true allergy, intolerance, side effect, etc. | ||||
| Health maintenance tool | Mainly ambulatory environment, but available across the enterprise | Primarily PCPs and their staff | Monitor preventive and condition-specific measures | Requires custom builds |
| Interface to use lab results possible | Lab values are not included or accessible | |||
| Direct data feed to registries for quality reporting and care management | Practice guidelines need to be kept updated | |||
| Requires users to interact with the tool | ||||
| Clinical notes/letters | All enterprise settings | All | Letter writing can be done in tandem with results review | Reference ranges are not available in documents and letters |
| Documents can include lab data as needed | Risk of adding incomplete or inaccurate lab data to reports | |||
| Templates facilitate incorporating lab data | Technically possible for a nonpathologist to modify reports by adding an addendum | |||
| Text explanations for patients about specific tests can be included |
PCP: Primary care provider.
Figure 1Screenshot showing portion of an HIV flowsheet in the EMR with laboratory data in a table format
Figure 2Screenshot of a user's EMR inbox messages showing an automated e-alert informing them that a potassium result was modified from 11 to 3.5 mmol/L
Figure 3Screenshot of the EMR Health Maintenance view populated with pending expectations for the user to act on
Figure 4Example of an EMR-generated letter by a physician to his/her patient including laboratory results and interpretation comments for the patient