Laboratory Results Interface (LRI)Functional Requirements Implementation Guide

Diagrams Showing Store & Display Option Pairs11/2/14Draft 2

Example Receive / Store / Display CombinationsReceive Store Display

ABC ABC ABC

ABC ABC abc

ABC

S-EXStore the exact data received

U-EXDisplay the exact

data received/stored

S-EXStore the exact data received

U-TRDisplay equivalent of the exact data

stored

S = Store U = Use for Display

S-EQ*Store equivalent of the

exact data received

U-EQDisplay the stored

equivalent of the exact data that was received

*S-EQ replaced OO-S-EQ

Store Option assigned to

each data element is the

minimum requirement

abc abc

Should the system be able

to persist this displayed

version in an audit trail?

ABC abca-b-c

OR

From Craig: “U-EQ should allow for an equivalent display relevant to the stored data. For example, we use equivalent a lot for date/time values, the message may say 20141031, we may store an equivalent of 56443 (number of days from a system specific “start date”) and we display 10/31/2014”

Example Receive / Store / Display CombinationsReceive Store Display

ABC ABC

ABC abc

S-EX-TRStore the exact data

received; may also store equivalent as well

U-EXDisplay the exact

data received/stored

U-TRDisplay equivalent of the exact data

stored

S = Store U = Use for Display

Store Option assigned to

each data element is the

minimum requirement

ABC

abc also allowed

S-EX-TRStore the exact data

received; may also store equivalent as well ABC

abc also allowed

Should the system be able

to persist this displayed

version in an audit trail if

“abc” was not stored?

If “abc” not stored, then translation of “ABC” to “abc”

(equivalent data) would need to occur here

Example Receive / Store / Display CombinationsReceive Store Display

ABC

S = Store U = Use for Display

S-TR-DStore equivalent of the exact data received;

exact data rcvd cannot be recreated

U-EQDisplay the equivalent of the exact data that was

received and stored

Store Option assigned to

each data element is the

minimum requirement

abc abc

ABC

S-TR-RStore equivalent of the exact data received;

exact data rcvd can be recreated

U-EQDisplay the equivalent of the exact data that was

received and stored

abc abc

ABC

S-TR-RStore equivalent of the exact data received;

exact data rcvd can be recreated abc ABCU-EX

Display the exact data received/stored

U-EXDisplay the exact

data received/storedNot Supported

ABC abca-b-c

ABC abca-b-c

OR

Example Receive / Store / Display CombinationsReceive Store Display

S = Store U = Use for Display

ABC ABC

S-EX-A**Store via association (pointer) the exact

data received

**S-EX-A replaced OO-S-ME & OO-S-MI

Table/File (EHR Internal or External)

ABCPointer

U-REFDisplay referenced data using pointer

Store Option assigned to

each data element is the

minimum requirement

ABC ABC

S-RCProcess, & Re-create

the exact data received if needed

EHR Data Model

ABCPointer

U-REFDisplay referenced data using pointer

S-MA Make Available

EHR

Message

John Cohen

John Cohen Ordering Provider

Processed…& discarded

The implementation SHALL make the data element available for use to accomplish the stated tasks defined by the use case (e.g., incorporation of laboratory results). There is no requirement to store the element.

LName Type Code LName Type Code

Example Receive / Store / Display CombinationsReceive Store Display

ABC ABCS-EX

Store the exact data received

U-NRDisplay of the data is

not recommended

S = Store U = Use for Display *S-EQ replaced OO-S-EQ

Store Option assigned to

each data element is the

minimum requirement

S-EQ*Store equivalent of the

exact data received

ABC abc

S-TR-DStore equivalent of the exact data received;

exact data rcvd cannot be recreated

ABC abc

S-TR-RStore equivalent of the exact data received; exact data rcvd can

be recreated

ABC abc

S-EX-TRStore the exact data

received; may also store equivalent as well

ABC ABCmaybe abc also N

ot R

ecom

men

ded

ABC a-b-cOR

Example Receive / Store / Display Combinations

Store Display

ABCor

a-b-cor

abc or

no data (display is not recommended)

S = Store

From Craig: “I still think the display should be relative to what is in the database, not what was in the message.”

S-EXStore the exact data received

S-EQStore equivalent of the

exact data received

S-TR-DStore equivalent of the exact data received;

exact data rcvd cannot be recreated

S-TR-RStore equivalent of the exact data received;

exact data rcvd can be recreated

S-EX-TRStore the exact data

received; may also store equivalent as well

S-EX-AStore via association (pointer) the exact

data received

S-RCProcess, & Re-create

the exact data received if needed

Each Vendor decides how the received data is represented (stored) in the patient record in their EHR-S database.

Each Vendor displays whatever version of the received data is represented (stored) in the patient record in their EHR-S database.

Receive

ABC

Example Receive / Store / Display Combinations

Receive Store Display

ABCUnspecified in

Functional Requirements

ABC

ABC abc

U-EXDisplay the exact

data received

U-TR or U-EQDisplay equivalent of the exact data

received

U = Use for Display

Should the system be able

to persist this displayed

version in an audit trail?

From Craig: “Otherwise, I think we just need a single requirement which relates the message content to the display, and allow each vendor to determine how they want to store the data.”

“I don’t think a display audit trail is practical”

Unspecified in Functional

RequirementsHow is conformant

“incorporation” of the lab results data to be determined for

certification testing? Only a subset of these data that are

received in the HL7 message are required to be displayed to pass

certification testing.

Display Option assigned to

each data element is the

minimum requirement;

EHR is always permitted to

display the exact data

received in the message.