Services Oriented Architecture
Below is a list of the current products this work group is stewarding.
If you are looking for a specific product, you may wish to visit the Master grid of all standards to see the full list of HL7 products.
Name | Description | Type |
---|---|---|
HL7 Cross Paradigm Specification: Health Services Reference Architecture (HL7-HSRA), Edition 1 | The Health Services Reference Architecture (HSRA) aims to support the design of medium/large scale eHealth architectures based on HL7 services and standards. The HSRA supports the architectural design process at the enterprise level with a map of bu... |
STU |
HL7 FHIR® Implementation Guide: FHIR for FAIR, Release 1 | The FHIR for FAIR Implementation Guide provides guidance on how the HL7 FHIR standard can be used for supporting the implementation and the assessment of the FAIR principles for health data.
See the specification at http:w... |
STU |
HL7 Health Services Platform (HSP) Marketplace, Release 1 | This is a vendor-agnostic Health Services Platform (HSP) Marketplace specification for publication, curation, discovery, and distribution of interoperable service implementations. This specification is completely agnostic to programming language/frameworks, database, and I/O techno... |
Informative |
HL7 Health Services Platform (HSP) Marketplace, Release 2 | The Marketplace API specification serves as a building block for orchestrating the exchange of such services and executable knowledge. Products deployed in an enterprise architecture are constituent building blocks in a larger information technology (IT) ecosystem. The deploy... |
STU |
HL7 Implementation Guide: Decision Support Service, Release 1 | A Decision Support Service takes in patient data as the input and provides back patient-specific assessments and recommendations. A Decision Support Service (DSS) facilitates the implementation of clinical decision support capabilities in a scalable manner... |
DSTU |
HL7 Implementation Guide: Immunization; Cross-Paradigm Interoperability Implementations, Release 1 | This implementation guide will explore the Service-Aware Interoperability Framework (SAIF) methodology to show how various HL7, IHE and OMG immunization-related artifacts can be deployed to satisfy immunization interoperability use cases. The project will provide feedback to the MnM SAIF Implem... |
Informative |
HL7 Model-based Transformation Service, Release 1 | This Standard provides a platform independent Service Functional Model (SFM) specification for an HL7 model-based bi-directional transformation service with exemplary mappings illustrating typical usage. The scope is limited to exchange of data between a source... |
STU |
HL7 Services Functional Model: Consent Management Service, Release 1 | This Service Functional Model API defines Services and API(s) for Consent Management. Consent Management is commonly addressed in regulation in participating jurisdictions. It is informed by the results of the Consent Management reference implementation occurr... |
STU |
HL7 Version 3 Methodology: Service Oriented Architecture; Service Definition, Release 1 | This document describes a methodology for defining services within the healthcare domain, in particular, for areas covered by Health Level Seven (HL7) domain content; an effort known as Service Oriented Architecture for Health Level Seven (SOA4HL7). It is accompanied by a set of delive... |
Informative |
HL7 Version 3 Specification: Ordering Service Interface – Release 1 | The Ordering Service is intended to complement existing SOA services and the SAIF Behavioral Framework (BF) for HL7. It will provide a Service Functional Model (SFM) for ordering pharmacy, laboratory, radiology, consult and nutritional services individually or part of an order ... |
DSTU, Informative |
HL7 Version 3 Standard: Common Terminology Services (CTS), Release 1 | The HL7 International Common Terminology Services (HL7 CTS) defines an Application Programming Interface (API) that can be used by HL7 Version 3 software when accessing terminological content. It is intended to specify only the unique services needed in the HL7 implem... |
Normative |
HL7 Version 3 Standard: Common Terminology Services (CTS), Release 2 | The goal of CTS2 is to provide a standardized interface for the use and management of terminologies. CTS2 provides a modular, common, and universally deployable set of behaviors which can be used to manage sets of terminologies deployed in a service environment. CTS2 s... |
Normative |
HL7 Version 3 Standard: Event Publish & Subscribe Service Interface, Release 1 – US Realm |
The Event Publish and Subscribe Service complements existing HL7 SOA services by providing a Service Functional Model (SFM) for services, components and systems to subscribe to clinical events of interest and receive notice when new data is available.
... |
DSTU, Normative |
HL7 Version 3 Standard: Healthcare, Community Services and Provider Directory (HCSPD SFM) | The Healthcare, Community Services and Provider Directory specifies core functionality of a Services and Provider Directory that not only supports semantic interoperability, but also valuable business initiatives such as Wait List Management. This HL7 SFM specifies a means to conduc... |
Normative |
HL7 Version 3 Standard: Identification Service (IS), Release 1 | The Identification Service (IS) also known as the Identification and Cross-Reference Service (IXS) Service Functional Model define the functional requirements which provides a set of capabilities to manage and retrieve identifying information for various kinds of entities (people, organi... |
Normative |
HL7 Version 3 Standard: Privacy, Access and Security Services (PASS); Access Control, Release 1 | The purpose of this document is to describe the conceptual-level viewpoints associated with the business requirements that relate to the content, structure, and functional behavior of information important to the Access Control area of the Privacy, Access, and Security domains within... |
Normative |
HL7 Version 3 Standard: Retrieve, Locate, and Update Service (RLUS) Release 1 | The Retrieve, Locate, and Update Service (RLUS) Service Functional Model specify the appropriate capabilities that must be realized by a service interface to locate, retrieve, and update resources (e.g. documents, messages) among and within healthcare organizations. ... |
Normative |
HL7 Version 3 Standard: Unified Communication Service Interface, Release 1 – US Realm | The Unified Communication Service complements existing SOA services by providing a Service Functional Model (SFM) for delivering alerts, recommendations, and other notifications using a variety of transport mechanisms including email, SMS, VOIP or other communication channels. The se... |
DSTU, Normative |