This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Product RLUS SFM

From HL7Wiki
Revision as of 19:58, 17 July 2009 by Llaakso (talk | contribs) (New page: ==Product Brief - Retrieve, Locate, Update Service Functional Model (RLUS SFM) == :back to Main_Page :back to Product List ===Product Name=== Retrieve, Locate, Update...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Product Brief - Retrieve, Locate, Update Service Functional Model (RLUS SFM)

back to Main_Page
back to Product List

Product Name

Retrieve, Locate, Update Service Functional Model (RLUS SFM)

Topics

Standard Category

Application Functional Specifications - Services (SOA)

Integration Paradigm

Services

Type

Releases

Summary

The Retrieve, Locate, Update Service Functional Model (RLUS SFM) Draft Standard for Trial Use (DSTU) is a draft functional standard defining the functions, responsibilities, inputs, outputs, and expected behavior of a system component capable of querying information and returning data and metadata between systems. Although fairly abstract in nature, RLUS is actually very simple to understand—it provides a generic query and retrieval mechanism that can be used for a multitude of information content via a standard access mechanism, promoting consistency within a heterogeneous environment.

Description

For example, an organization may have a benefits/ enrollment system, an Electronic Health Record System, and a Personal Health Record System all within the organization. Intregrating information from among these systems can be complex. RLUS could be used to further this integration by building an RLUS-compatable interface into each of the above systems, and making a distributed RLUS call to retrieve pertinent information for a specific patient. The RLUS specification standardizes how disparate information types are managed and aggregated into a single result. Further, since RLUS provides a mechanism for new, richly structured information content to be supported, integration based upon RLUS allows for new systems to come online and integrate into the organization’s infrastructure. RLUS specifies a collection of behaviors needed to manage this inquiry, query, and retrieveal of content. The “location” function allows for the return of candidate information, indicating the availability of matching records without actually returning their instances (for example, does the system have any positive zzzz lab results for patient X). Other interface behaviors specify how the targeted information can be retrieved or updated. The RLUS SFM is among the first healthcare standards targeted to support a service-oriented architecture (SOA), and is at the basis for an unprecendented collaboration with the Object Management Group (OMG), whom has adopted a technical specification complementing this SFM.

Business Case (Intended Use, Customers)

Benefits

What is the benefit to using RLUS?

Integration of new software packages in a heterogeneous environment creates an exponential integration problem. Each new system-to-system interface creates tremendous integration burden in terms of creating messages, mapping data fields, and potentially transforming data for use. Interface engines have a role to play here, but do not directly support complex queries among participating systems. RLUS allows for these complexities to reside within the systems that hold the data, shielding requestors from unnecessary detail. RLUS simplifies the ask-answer pattern, providing both rigor and clarity while supporting rigorous information content.

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Education

Certification Available
  • none

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development