1 / 6

Lab Results Interface Functional Requirements Guide

This document outlines functional requirements for lab results interfaces. It covers error handling, result progression, data updates, and linkage to EHR models. Key topics include eDOS, reporting, and regulatory items.

leighanna-gamble
Download Presentation

Lab Results Interface Functional Requirements Guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EHR-S Functional Requirements IG: Lab Results Interface 10/17/2014

  2. Timeline • Notice of Intent to Ballot (NIB) - 11/1/2014 • Is on HL7 OO WG agenda for next week (10/25) • Draft content due to editors - 11/15/2014, review on 11/17 • Final content due 12/7/2014 • Ballot open 12/12/2014 - 1/9/2015 • WGM 1/18/2015 – 1/23/2015

  3. Issues for LRI Guide • Error handling (note that LRI has ballot comments on this section) • what is a hard error with the expected behavior • what is a soft error with the expected behavior • Result progression • Preliminary, final, corrected, amended, appended, etc – translate to detailed behavior guidance • Reporting when one order code translates into N results • eDOS defines grouping function for ordering convenience of panels/profiles • Data updates besides results (patient, specimen) • Linkage to the EHR-s Functional Model verbs • Linkage between this document and the to be created Lab Functional Profile and the EHR-S Functional Model • Use case diagrams

  4. Issues for EHR-S FR, NOT LRI, but lab related • eDOS incorporation (initial load vs update vs overwrite) • LOI guide: • handling cancelation • diagnosis type • reflex testing with request for placer number • AOE vs ASC • not in current scope: • updating specimen information • order updates • Capturing comments (order, patient, result, specimen etc) • Regulatory items (CLIA, et al)

  5. LIS functionality parking lot document • Error handling • what is a hard error with the expected behavior • what is a soft error with the expected behavior • Result progression – preliminary, final, corrected, amended, appended, etc • reporting profiles • Data updates besides results (order, patient, specimen) • linkage to the EHR-s (LIS) Functional Model verbs • linkage between this document and the to be created Lab Functional Profile and the EHR-S Functional Model • use case diagrams • eDOS creation • handling cancelations • diagnosis type • reflex testing with request for placer number • AOE vs ASC • Capturing comments (order, patient, result, specimen etc)

  6. document sections – .. authors • Background • Relationship to EHR-S FM (conformance of derived FPs) • Relationship to EHR-S Lab FP • Project Scope – drafted and reviewed • Use Case Assumptions – drafted and reviewed • Results to ordering Provider – drafted and reviewed • Diagrams • User stories – drafted and reviewed • Requirements for Incorporate • Intro to spreadsheet and link to file • Issue detail section(s) • Error handling • Result progression

More Related