Stream: implementers
Topic: The IVD Industry Connectivity Consortium (IICC) and HL7
Lin Zhang (Aug 27 2017 at 04:33):
The IVD Industry Connectivity Consortium (IICC) is a global, nonprofit organization dedicated to creating and encouraging adoption of a unified connectivity standard to reduce the cost and variability of data exchange between IVD devices and healthcare informatics in clinical laboratories. This will improve healthcare efficiency and patient care.
IICC is collaborating with SDOs, including HL7, IHE and Regenstrief Institute. HL7 v2.x has been selected as a baseline standard for clinical laboratory connectivity.
How about FHIR?
IICC website:
http://ivdconnectivity.org/
Lin Zhang (Aug 27 2017 at 04:35):
LAW – Laboratory Analytical Workflow Profile – The LAW Profile defines the physical connection, message definitions (based on the HL7 Messaging Standard v2.5.1), and workflow definitions between instruments, middleware, and LIS systems in the laboratory. IICC collaborated with the IHE Pathology and Laboratory Medicine (PaLM) domain to develop the LAW Profile. LAW is currently being implemented by all major IVD companies.
For more information on LAW, see http://ivdconnectivity.org/law-profile/
Lin Zhang (Aug 27 2017 at 04:36):
IVD = In Vitro Diagnostics
Grahame Grieve (Aug 28 2017 at 11:47):
@Todd Cooper where does this fit into the picture?
Eric Haas (Aug 28 2017 at 15:44):
Orders and Observations is working on a project right now.... @Hans Buitendijk is working on this with the LIVD project will be reporting on it Q2 Thursday
Hans Buitendijk (Aug 31 2017 at 19:38):
There are at least three initiatives of interest here:
- HL7 V2 Lab Implementation Guides (eDOS, LOI, LRI) to enable exchange of orderable tests from Lab to ordering system (eDOS), placement of orders to a Lab (LOI), and results reporting from the Lab to ordering provider, Public Health, etc. (LRI). These are message based transactions and expected to still stay in the V2 space for some time to come. This effort is US focused. FHIR has opportunity as it augments with dynamic queries, or that the worfklow management required can substantially benefit from FHIR.
- IHE LAW, also V2 based, focuses on the device-LIS communication. This has an international focus. Surely if FHIR offers substantial improvements that justify replacement of something that works, there are opportunities.
- LIVD - IICC (in collaboration with FDA, ONC, NLM, HL7, CDC and I'm sure I missed somebody) established a set of requirements on how to communicate between device manufactures and Laboratories on suggested LOINC codes given the IVD test codes used by the devices. This can aid in easier mapping efforts to enable results reporting using the appropriate and consistent LOINC codes. Initially this is being express in straight JSON. HL7 has a project in progress to express these proposed mappings using FHIR and hopes to go to ballot on implementation guides/profiles in January. This has an international focus.
HL7 OO also did some initial work (see Eric Haas) to define FHIR profiles to represent LOI, LRI, eDOS, which helped us validate completeness/gaps in FHIR (at least is should be able to represent the data set already agreed to in the US).
Generally, FHIR resources necessary for enabling RESTful service based data access/exchange are in play, while profiles/implementation guides require a bit of work. In the US, the Argonaut/US-Core profiles/implementation guides have started to address that, but would not be able to support all the relevant Lab workflows currently supported by something HL7 based. Flipping perfectly functional, working V2 messages to FHIR based messages and services will require a good business case to make that worth everybody's effort. But augmenting these flows with FHIR based solutions and over time perhaps reaching a tipping point where we might as well move everything to FHIR is possible. So far it is still easier/faster to build on the V2 capabilities in place then it is to switch to FHIR for these workflows. "tomorrow" that answer may change, but the question is when would that make sense.
Lin Zhang (Sep 03 2017 at 17:27):
http://www.pchalliance.org/sites/pchalliance/files/Fundamentals_Data_Exchange_20170404.pdf
Lin Zhang (Sep 03 2017 at 17:30):
Last updated: Apr 12 2022 at 19:14 UTC
