LRI+Architecture+Overview

include component="page" wikiName="siframework" page="LRI Header" This is the wiki page to document the Lab Results Interface (LRI) Architecture for the Use Cases as defined by the S&I Framework Laboratory Results Use Case document. =LRI Pilot Architecture Overview= The objective of the LRI Pilot project is to enable the demonstration of the LRI User Story for electronic test results delivery using the S&I Framework Implementation Guide and Vocabulary. This architecture overview identifies the layers, components and interactions, and patterns using standards that are necessary to create a robust reference implementation that can be used by the community. The LRI Pilot will incorporate the LRI messaging requirements and vocabulary being defined by the IGs Analysis and CIM/Vocabulary Workgroups, and show that test result messages can be generated by senders and consumed by receivers as described in the LRI Abstract Model. To meet its objective, the LRI Pilot Demonstration will:
 * Electronically generate an HL7 test result message that:
 * Complies with the LRI Implementation Guide Analysis Workgroup Test Result Guide
 * Utilizes the vocabulary specified by the LRI CIM/Vocabulary Workgroup
 * Electronically consume the S&I Framework Test Result Message
 * Decompose the message into the atomic data elements.
 * **The RI focuses on tools for ensuring an LRI that meets the LRI S&I Initiative requirements** and is consistent with the LRI Initiative scope and charter. The RI can be used as is, or modified, by developers to create software modules that generate and consume LRI Test Result Messages.
 * **RI provides tools as aids, not as "standards."** RI tools do not supersede or replace balloted standards or implementation guides.

Out-of-Scope
The LRI Initiative acknowledges the variations in requirements for reporting across local, state, tribal, and territorial boundaries as well as voluntary versus mandatory requirements; however, the handling of these requirements is out of scope.
 * Transport, Security, Privacy, Addressing, Audit, and Patient Identification are out of scope for the LRI Pilot.** These are all essential components from an overall system perspective. However, this LRI initiative is about message structure and content, not about transport or other infrastructure. The RI will not produce code to transport, encrypt, or otherwise "secure" the payloads from a sender to a receiver. Other projects (Direct Project, Nationwide Health Information Network Exchange and CONNECT, etc.) have already produced open source reference implementations for transport, encryption, and other infrastructure. Some of the code from these other projects may be used in the LRI Pilot demonstrations for access control, audit log, authentication, integrity, encryption of data in rest and in transit. These projects have already been specified by ONC in its Final Rule for EHR Standards and Certification. Other ONC S&I Framework Initiatives, such as Provider Directory and Certificate Interoperability, will address gaps in standards and implementation guidance that have not been previously specified in regulations and/or standards.

Patient Consent
Organizations are assumed to have patient consent policies in place as appropriate and these existing mechanisms will be used by the senders and receivers before LRI information is exchanged between the senders and the receivers.

Guidance:
The following are key architecture drivers and principles that will guide the creation of a robust LRI Pilot Demonstration.
 * Focus on the minimal Data Elements required for LRI Initiative per the LRI Test Result Message Implementation Guide..
 * ‍‍‍‍‍‍‍‍The Clinical Information Model will be an isomorphic representation of input documents or messages.‍‍‍‍‍‍‍‍
 * Create domain specific services to generate and consume an LRI Test Result Message using the S&I LRI Implementation Guide as guidance. Clinical Information Model
 * ‍‍‍‍‍‍‍‍Ability to re-use Data Elements outside of the LRI Initiative‍‍‍‍‍‍‍‍
 * Use software patterns to provide modularity, extensibility and re-usability
 * Allow architecture to be implemented using multiple languages and platforms
 * The creation of an LRI Test result Message may require the use of multiple input documents and data sources, which through a chain of transformation produce the required message.
 * The Pilot Demonstration shall use a layered approach that follows standard enterprise architecture best practices and provides the following advantages:
 * Modular Software Design
 * Separation of concerns relating to data, applications and business logic.
 * Allows for extensibility and re-usability at each layer
 * Focuses on each data element and services for each data element that can be packaged with various service orchestrations.
 * Allows for designing computable models and plugging in different transformations, validations, discovery services in the future.
 * Supports encoding of individual and composite data elements using various encoding schemes.

LRI Pilot Architecture Components

 * LRI Use Case and Sequence Diagrams** – Pilot demonstration must implement the flow of events described in the LRI Use Case according to the User Story. The Pilot Architecture expands on the defined Sequence Diagram by showing bidirectional flow of messages (Lab Results Message and Acknowledgement response).
 * Policy and Service Identification** – Identifies policies and regulations applicable to each step of the flow of events described in the LRI Use Case and provides a conceptual service package diagram to inform the Pilot implementation.
 * Deployment Models** - Describe the various deployment scenarios and configuration of services required to implement a Pilot system.

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"