Product DSS SFM
Contents
- 1 Product Brief - Decision Support Service Functional Model (DSS SFM)
- 1.1 Product Name
- 1.2 Topics
- 1.3 Standard Category
- 1.4 Integration Paradigm
- 1.4.1 How does this relate to the OMG Technical Specification and to the Healthcare Services Specification Project?
- 1.4.2 How does this relate to the HL7 Services-Aware Enterprise Architecture Framework?
- 1.4.3 Don’t industry standard services (such as the Decision Support Service, Entity Identification Service) limit vendor competition?
- 1.5 Type
- 1.6 Releases
- 1.7 Summary
- 1.8 Description
- 1.9 Business Case (Intended Use, Customers)
- 1.10 Benefits
- 1.11 Implementations/ Case Studies (Actual Users)
- 1.12 Resources
Product Brief - Decision Support Service Functional Model (DSS SFM)
- back to Main_Page
- back to Product List
Product Name
Decision Support Service Functional Model (DSS SFM)
Topics
Standard Category
Application Functional Specifications - Services (SOA)
Integration Paradigm
Services
How does this relate to the OMG Technical Specification and to the Healthcare Services Specification Project?
For EIS, HL7 has partnered with OMG to produce technical specifications supporting Service Functional Models within OMG’s technology adoption process. To the healthcare industry, this provides value via OMG’s rigorous architectural approach, review process, and distributed systems expertise. For OMG, this relationship brings deep healthcare experience via HL7’s extensive international participation and vertical industry expertise. The Healthcare Services Specification Project (HSSP) is a moniker for the collaboration between groups collaborating on service standards, of which HL7 and OMG are participants.
How does this relate to the HL7 Services-Aware Enterprise Architecture Framework?
In 2008, HL7 embarked upon developing its Services-Aware Enterprise Architecture Framework (SAEAF). SAEAF will be aligning the broad range of HL7 specifications—including services, messages, and document standards—to a consistent approach across the whole of HL7’s offerings. SAEAF also specifies usage constraints for deployed HL7 standards. Several HSSP services predate SAEAF. Over time, we expect all HL7 Service Functional Models to come into alignment with SAEAF.
Don’t industry standard services (such as the Decision Support Service, Entity Identification Service) limit vendor competition?
Not necessarily. While industry standards specify how a consumer interacts with the service, these specifications have expressly left how these functions are supported out-of-scope. In other words, there is no predetermined knowledge modeling formalism, system design platform, or approach that is advocated in the standard. Vendors are able to compete based upon quality-of-service and the benefits of their specific implementation. Further, the specification includes mandatory and supplemental requirements (“nice-to-haves”), which can further stratify marketplace offerings.
Type
Releases
- DSTU: HL7 Version 3: Decision Support Service (DSS), Release 1. This DSTU has been extended an additional 24 months upon the approval of the TSC as indicated in TSC Tracker item #996. Ends April 2011
Summary
The Decision Support Service Functional Model (DSS 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 for evaluating patient data to reach patient-specific conclusions. A DSS, for example, can evaluate a patient’s health summary as encoded in a Continuity of Care Document (CCD) and provide structured recommendations regarding the patient’s health maintenance and chronic disease management needs. The DSS SFM is among the first healthcare standards targeted to support a service-oriented architecture (SOA), and is at the basis for an unprecedented collaboration with the Object Management Group (OMG), which has adopted a technical specification complementing this SFM.
Description
Business Case (Intended Use, Customers)
Why produce an industry standard Decision Support Service?
Quite simply, the Decision Support Service defines the collective set of behaviors that one would expect a clinical decision support engine to perform. This functionality is required of most healthcare organizations and allows for the data collected in electronic health records and other clinical information systems to provide enhanced value for patients, clinicians, healthcare providers, and payors. The challenge is that the lack of a standard makes the use of decision support services more costly and difficult. Without clearly defined expectations of how Decision Support Services should interface with health information systems, variants abound and interoperability suffers.
Benefits
Implementations/ Case Studies (Actual Users)
Resources
Work Groups
Education
- See more at http://www.hl7.org/implement/training.cfm
Certification Available
- none
