1. Laboratory Orders Interface Initiative
eDOS Workgroup Update
Laboratory Orders Interface Initiative
eDOS is the Test Compendium Framework for the electronic delivery of a lab’s Directory of Service (DOS)

2. Meeting Etiquette
Remember: If you are not speaking keep your phone on mute
Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call
This meeting, like all of our meetings, is being recorded
Another reason to keep your phone on mute when not speaking!
Feel free to use the “Chat” or “Q&A” feature for questions or comments
Please announce your name each time prior to making comments or suggestions during the Q&A portion of the meeting
From S&I Framework to Participants:
Hi everyone: remember to keep your phone on mute 
NOTE: This meeting may be recorded and, if recorded, will be posted on the eDOS wiki page after the meeting

3. Agenda Announcements eDOS Pilot Updates
eDOS Test Cases (if open questions)
eDOS IG Project Updates
Q&A

4. eDOS Summary – Background
eDOS: Provides an electronic interchange of a laboratory’s Directory of Services (DOS) in a structured format based on HL7’s master file update found in Chapter 8 of version 2.6. This implementation guide, initially developed by the members of the American Clinical Laboratory Association’s (ACLA) in conjunction with their Health Information Technology (HIT) Committee, is intended to provide all necessary information to help an Ordering Provider properly request laboratory tests consistent to aide patient diagnosis.
The eDOS work effort will:
Validate that the current Informative Implementation Guide meets the objective through a pilot of eDOS
Align the IG with the in-scope tests in the Lab Result Interface (LRI) IG
Incorporate pilot findings to update the Implementation Guide to develop a normative document to be balloted based on HL7’s ANSI process.
The Normative IG is intended to support the efforts of the Lab Order Interface (LOI) IG and the Lab Result Interface (LRI) IG by providing the services necessary to meet the needs of the users of those guides.

5. Background
eDOS, or the Laboratory Test Compendium Framework, provides an electronic interchange of a laboratory’s directory of services in a structured format based on HL7’s master file update.
An Implementation Guide was developed by the members of the American Clinical Laboratory Association (ACLA) in conjunction with their Health Information Technology (HIT) Committee to provide all necessary information to help an Ordering Provider properly request laboratory tests consistent to aide patient diagnosis.
The eDOS IG is available as an informative document from HL7
The LOI Tiger Team identified the importance of coordinating the LOI and eDOS efforts so that LOI can validate the eDOS IG as part of the LOI alignment activities
To ensure that the eDOS efforts don’t delay the LOI Initiative, the Tiger Team decided to spin off a separate eDOS Work Group to focus on eDOS 5

6. Background
The initial work group efforts outlined focus on kicking off pilots to validate the Implementation Guide with the goal of creating a normative document to be balloted based on HL7’s ANSI process
To ensure successful validation and pilots, a Use Case and Functional Requirements will be developed to validate existing industry requirements and the current informative IG
Real-world scenarios will help create specific pilot test conditions and metrics for use in Pilot validation of the IG
Clearly defined functional and data set requirements facilitate eDOS & LOI coordination and alignment
A well-articulated Use Case supports awareness of the clinical and implementer communities’ real-world needs 6

7. Pilot Updates Quest Diagnostics Initial Contact Kaiser Permanente
LabCorp
Bioreference Labs
Mayo
Request for Pilot Submitted
Genoptix
Kaiser Permanente
Initial Contact
ARUP
Contact Identified
eDOS – electronic directory of service

8. Test Cases
Questions?
Questions from Eric Haas

9. eDOS IG Project Update IG updates in progress:
Deleted HL7 content to synch with LOI/LRI style convention
Adding the following:
approved errata/change requests
data type section, synched with LOI and LRI
“pre-adopt” notes, e.g. V2.8 approved proposals, and select V2 data types (synch with LOI/LRI)

10. eDOS IG Project Update - Profiles
eDOS Profiles
eDOS_Common_Component
eDOS_GU_Component (Globally Unique)
eDOS_NG_Component (Non-Globally Unique)
LAB_XO_Component (Exclusions)
Acknowledgement Profiles
edos_Acknowledgement_Component
GU _Acknowledgement_Component (Globally Unique)  
NG_Acknowledgement_ Component (Non-Globally Unique)

11. eDOS IG Project Update – Appendix B - AOE
Submit common AOE examples by March 8
LOINC Code
LOINC Description
Suggested HL7 data type (for OBX “Answer”)
Usage note (if applicable)
Review consolidated submissions March 12
Open Peer Review March 12, comments by March 19
Resulting AOE example list included in eDOS HL7 Ballot

12. AOE Examples LOINC Code AOE Question Suggested HL7 Data
Type OBX Response
Usage Note
For whom did you work at your main job or business?
XON
Employer Name – Organization
What was the location of this company?
XAD
Employer Address
8665-2
Patient’s last menstrual period DT

13. Next Steps - Reminders
Sign up as a Committed Member for the Workgroup (link)
Review the Workgroup Charter Workgroup meeting (link)
Fill out the Pilot Spreadsheet
Pilot Spreadsheet being updated with information from the wiki form:

14. Q&A