editing disabled

Retrieval, Location and Update Service (RLUS) Specification Profile


The Retrieve, Locate, Update Service Functional Model (RLUS SFM) is a functional standard defining the capabilities, responsibilities, inputs, outputs, and expected behavior of a system component capable of querying information and returning data and metadata between systems. RLUS can be used for managing a multitude of information content via a standard access mechanism, promoting consistency within a heterogeneous environment.

The Retrieve, Locate, and Update Service (RLUS) Service Functional Model specification provides a set of capabilities through which information systems can access and manage information resources. RLUS realizes, at its core, a basic set of CRUD capabilities plus location for health information resources management and, simply, standardizes the way in which the resources are exposed and consumed independently from the nature of the resources. In effect, RLUS provides an access layer for interacting with a system containing the data of interest, providing a standardized way of location, retrieval, and of update of that content.

RLUS is a coarse-grained SOA service specification, meaning that it contains relatively "few" operations that can be broadly applied to a wide variety of functional domains. The RLUS Standard is actually a collection of several supporting standards, each of which have been adopted separately but which are held together via a common construct. The specifications falling under the RLUS umbrella, as well as their intended use, appears in the table that follows.

The RLUS standards

The RLUS Standards, as a part of HSSP (Healtcare Service Specification Project), currently consists of:
Intended Use
RLUS Normative Edition v1.0 [HL7]
Enterprise Architects
Defines the scope, high-level functionality, and requirements governing supporting technical specifications.
Serves as a Functional Requirements Document. It is not a technical specification (see below)
RLUS Technical Specification [OMG]
Interop Architect
Defines, at a technical level, the precise API interface specifications for SOAP realizations of RLUS.
Serves as a technical specification document to define RLUS implementation compliance in SOAP.
RLUS HData RESTful Transport Specification
Interop Archtiect
Defines, at a technical level, the precise API interface specification for REST realizations of RLUS.
Serves as a technical specification document to define RLUS implementation compliance in REST.

RLUS Derivative Work

As RLUS by design is a broad, generic service interface, the original concept was to create domain-specific service profiles of RLUS intended to specify how RLUS would be applied to specific functional domains or use-cases. These service profiles indicate search criteria, expected results, and in some cases restrict the allowable set of method/procedure calls available within the overall RLUS specification, en route to a more tightly specified applicability into a problem domain.

Where a profile exists for your domain of interest, it will provide a more effective path to "turnkey" interoperability than would the generic RLUS specification itself. It is envisioned that the portfolio of service profiles for RLUS will continue to grow, and consumers with interest in developing a custom profile are encouraged to contact the HSSP Leadership and indicate your interests.

The collection of RLUS-relevant work can be found in our Knowledge Management system at our RLUS Resource Hub.

RLUS Presentations and Implementation Guidance

HSSP Artifact Type
(Service Functional Model)
HL7 - Retrieve Locate and Update Service (RLUS) SFM
Balloted version (passed)
Final reconciliation underway
(Service Technical Model)
OMG - Retrieve, Locate, and Update (RLUS) Service
Version 1.0.1
(Service Technical Model)
OMG - RLUS HData RESTful Transport (HDATA)
Version 1.0
Beta 1

This wiki contains details relating to the next step in HL7 process: the Normative Ballot effort for the HL7 SFM standard.

RLUS Working Draft


Document (post ballot)
  • File Not Found
    File Not Found
  • File Not Found
    File Not Found

RLUS Capabilities