Healthcare Services Specification Project   The Business Case for Healthcare SOA Standards HL7 Service-Oriented Architectu...
Acknowledgements <ul><li>Contributions to this content have come from: </li></ul><ul><ul><li>Health Level Seven (HL7) http...
What is the Healthcare Service Specification Project?   <ul><li>A joint standards development activity occurring in multip...
HSSP is part of the bigger health IT landscape…
SOA and Enterprise Architecture in HL7 <ul><li>HL7 has started developing the Services-Aware Enterprise Architecture Frame...
HSSP Asset Inventory page  Asset Purpose Functional Spec-DSTU Technical Spec Functional Spec-Norm Implementation  Availabi...
What type of products do you produce?  <ul><li>SOA Functional Standards [Service Functional Models] </li></ul><ul><ul><li>...
“ Practical Guide for SOA in Healthcare”  <ul><li>Targeted to help those interested in SOA  to do SOA </li></ul><ul><li>Is...
2009 Events  (planned, major milestones) Dec:  OMG Long Beach (Dec 7-11) Issue PASS Audit RFP (OMG) Issue HSD RFP (OMG) Ju...
Core Project Principles <ul><li>Leverage each community to its strength </li></ul><ul><li>Organizations jointly participat...
The HSSP Process OMG HL7 HL7 DSTU Service Functional Model OMG RFP Technical Specification ANSI Standard
Understanding HSSP Artifacts, Roles, Attributes SFM Owned / Produced by HL7 Community RFP Submission Implementation Define...
How are HSSP services expressed?  Semantic Space/ Universe Formalism   (Structure) Semantic Signifiers (profile-relevant  ...
Why “services”?* <ul><li>A common practice in healthcare, just not yet in healthcare IT </li></ul><ul><li>Many key product...
Context of HSSP Specifications
Interoperability Realized page  Documents Messages Services Context Constraints Requirements Model Enterprise Information ...
SOA  ≠  Web Services Yes No Is an industry standard? Yes Yes Is an enabler for business and IT transformation? No Yes Affe...
The Benefits of HSSP Standards…  <ul><li>Define industry standard behaviors for healthcare-oriented service functions </li...
Where would these specifications be used <ul><li>Inter-Enterprise (such as NHIN, RHIOs, HIE’s)  </li></ul><ul><ul><li>By f...
The Value of HSSP … Lower cost = wider deployment = higher quality service Participation by provider and payer community i...
How is this project “different”?  <ul><li>Active participation from three continents and 15+ organizations </li></ul><ul><...
Why should I participate in HSSP?  <ul><li>This effort is focused on and driven by business-need </li></ul><ul><ul><li>It ...
Why participate in standards at all?  <ul><li>This is happening, with or without you.   We’d rather it be with you…  </li>...
How do I Participate? <ul><li>Participation is open to everyone.  You don’t need to be a member (though we encourage you t...
Who should I involve? <ul><li>Involve the staff that can best address your business needs: </li></ul><ul><ul><li>You will ...
References <ul><li>All HSSP artifacts and work in process are open.  Visit us at:  </li></ul><ul><ul><ul><li>http:// hssp....
<ul><li>Supplemental Slides:  HSSP Stakeholder Benefits and Impacts </li></ul>
What Participants are Saying…  <ul><li>“ Kaiser Permanente I.T. is currently transitioning to an SOA-based approach to bus...
For Product Consumers and Users… The Impacts and Rationale of HSSP Specifications Lower cost = wider deployment = higher q...
Product Vendor … The Impacts and Rationale of HSSP Specifications You can shape the standard to be supportive of your prod...
Regulatory/Policy/Legislative … The Impacts and Rationale of HSSP Specifications HSSP is using HL7 semantics, OMG processe...
Research … The Impacts and Rationale of HSSP Specifications Composable nature of services promotes construction Enables co...
Implementer/Integrator … The Impacts and Rationale of HSSP Specifications Using services speeds project design phases and ...
SDOs … The Impacts and Rationale of HSSP Specifications Practical, market-focus and iterative timeline promotes participat...
Upcoming SlideShare
Loading in …5
×

2009_4_HSSP_Public_Slide_Deck_Version_2.1.ppt

406 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
406
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • HL7 supports the requirements modeling and through a ballot process, issues a Draft Standard for Trial Use. OMG supports open standards, and supports a technically rigorous process to issue RFPs and vote on submissions. The final draft of the HL7 DSTU, which is influenced by the RFP Responders, can go on to become an American National Standards Institute (ANSI) standard
  • HL7 supports the requirements modeling and through a ballot process, issues a Draft Standard for Trial Use. OMG supports open standards, and supports a technically rigorous process to issue RFPs and vote on submissions. The final draft of the HL7 DSTU, which is influenced by the RFP Responders, can go on to become an American National Standards Institute (ANSI) standard
  • The pyramid demonstrates several interacting components that influence interoperability. The color-temperature scale on the right shows that the “peak” of the pyramid represents highest interoperability, with minimal interoperability at the base. The left side of the pyramid shows factors influencing “information” and its ability to carry meaning across systems and organizations. The right side addresses the mechanism of interaction. Note that neither side of the pyramid alone produces interoperability. Though we can improve the mechanisms of interoperability to “state of the art” technology using standards-based middleware and mechanisms such as dynamic discovery, interoperability cannot be achieved unless the corresponding information has semantic meaning. Interoperability is achieved as one scales the pyramid, improving the semantic integrity and understanding of the knowledge, as well as improving the access mechanisms by which that knowledge can be attained. At the peak (but not actually part of the pyramid) is the software application itself. These applications, built upon many or all of the components depicted below it, provide the integrating mechanism by which the component technologies and knowledge come together to provide business value .
  • PM Tool has free form text field to track project resources, such as implementers, etc.
  • 2009_4_HSSP_Public_Slide_Deck_Version_2.1.ppt

    1. 1. Healthcare Services Specification Project The Business Case for Healthcare SOA Standards HL7 Service-Oriented Architecture SIG OMG Healthcare Domain Task Force Open Health Tools April 2009
    2. 2. Acknowledgements <ul><li>Contributions to this content have come from: </li></ul><ul><ul><li>Health Level Seven (HL7) http://www.hl7.org </li></ul></ul><ul><ul><li>Object Management Group (OMG) http://www.omg.org </li></ul></ul><ul><li>With additional contributions from: </li></ul><ul><ul><li>Integrating the Healthcare Enterprise (IHE) http://www.ihe.net </li></ul></ul><ul><ul><li>Open Health Tools http://www.openhealthtools.org </li></ul></ul>
    3. 3. What is the Healthcare Service Specification Project? <ul><li>A joint standards development activity occurring in multiple organizations, including Health Level 7 (HL7), the Object Management Group (OMG), IHE, Open Health Tools, and others </li></ul><ul><li>An effort to create common “service interface specifications” tractable within Health IT </li></ul><ul><li>Its objectives are: </li></ul><ul><ul><li>To create useful, usable healthcare standards that address business functions, semantics and technologies </li></ul></ul><ul><ul><li>To complement existing work and leverage existing standards </li></ul></ul><ul><ul><li>To focus on practical needs and not perfection </li></ul></ul><ul><ul><li>To capitalize on industry talent through open community participation </li></ul></ul>page Policy Business Drivers Information Models Service Funct. Model RFP Profiles Technical Specifications Implementations Requirements Government, Professional Societies,… Healthcare Organizations HL7, openEHR, CEN, … HL7 Domain Committees, CEN, Standards Bodies (SDOs) OMG Healthcare Domain Task Force IHE, SDOs, Healthcare Orgs IHE OMG, RFP Submitters Interop Testing Vendors, OHT, Healthcare Orgs HSSP Approach
    4. 4. HSSP is part of the bigger health IT landscape…
    5. 5. SOA and Enterprise Architecture in HL7 <ul><li>HL7 has started developing the Services-Aware Enterprise Architecture Framework (SAEAF), and which embraces services, messages and documents </li></ul><ul><li>Includes SOA-based behavioral framework and conformance framework for HL7 standards (including HL7 v2 and v3 messages, CDA documents and services) </li></ul><ul><li>Utilizes SOA and Model-Driven Architecture principles for explicit expression of policy, governance and traceability </li></ul><ul><li>Service standards rely on SOA WG and HSSP work </li></ul><ul><li>Framework development in progress, will influence future development of standards within HL7 </li></ul>
    6. 6. HSSP Asset Inventory page Asset Purpose Functional Spec-DSTU Technical Spec Functional Spec-Norm Implementation Availability Entity Identification Service ( EIS ) To manage identities and identifying traits (e.g., MPI) Complete Complete In Ballot Commercially Available Retrieve Locate Update Service ( RLUS ) To manage location and retrieval of healthcare content Complete Complete Expected 9/2009 Commercially Available Decision Support Service ( DSS ) To analyze patient data and assess against knowledge rules. Complete Expected 9/09 Expected 5/2010 In development Common Terminology Service ( CTS II ) Defines behavior for managing/maintaining terminologies Expected 5/2009 TBD - - [Healthcare] Audit Service ( PASS Audit ) Security-oriented service to manage audit record Expected 9/2009 TBD - - Human Svcs Directory ( HSD ) To find providers & services in allocated areas, e.g., referrals. Expected 9/2009 TBD - - Practical Guide for SOA in Healthcare Informative reference on how to approach SOA N/A N/A N/A N/A
    7. 7. What type of products do you produce? <ul><li>SOA Functional Standards [Service Functional Models] </li></ul><ul><ul><li>Define the scope, purpose, and information content of industry standard healthcare services </li></ul></ul><ul><li>Technical Specifications for balloted Functional Standards </li></ul><ul><ul><li>Bind functional specifications into specific technologies, transport protocols; technical conformance criteria </li></ul></ul><ul><li>Implementation Guidance & White Papers </li></ul><ul><ul><li>Non-normative guidance to help consumers apply and use HSSP specifications within their organizations. Not standards. </li></ul></ul>
    8. 8. “ Practical Guide for SOA in Healthcare” <ul><li>Targeted to help those interested in SOA to do SOA </li></ul><ul><li>Is one approach for SOA-enabling healthcare organizations </li></ul><ul><li>Brings together practical experience with recommended best-practices </li></ul><ul><li>Is not (nor is it intended to be) an industry standard </li></ul><ul><li>Is not (nor is it intended to be) officially sanctioned by HL7 </li></ul><ul><li>Alignment with the HL7 SAEAF is underway </li></ul><ul><li>Available at http://hssp.wikispaces.com/PracticalGuide </li></ul>
    9. 9. 2009 Events (planned, major milestones) Dec: OMG Long Beach (Dec 7-11) Issue PASS Audit RFP (OMG) Issue HSD RFP (OMG) Jun : SOA in Healthcare Workshop (Chicago) OMG San Jose (Costa Rica) DSS RFP Initial Submission (OMG) Nov: May : HL7 Kyoto EIS SFM Normative Ballot (HL7) CTS2 SFM Ballot (HL7) Oct: Apr: Sep: OMG San Antonio (Sep 14-18) HL7 Atlanta (Sep 20-25) PASS Audit Ballot (HL7) Issue CTS II RFP (OMG) Develop HSD SFM RFP (OMG) Revised Practical Guide (HSSP) Mar: OMG Washington EIS Tech. Spec. Adopted (OMG) RLUS Tech. Spec. Adopted (OMG) Aug: Feb : Jul: Jan : SFM Ballots (CRFQ, Security) HL7 Orlando
    10. 10. Core Project Principles <ul><li>Leverage each community to its strength </li></ul><ul><li>Organizations jointly participate in all activities </li></ul><ul><li>Work products will be “owned” by only one organization but used collaboratively </li></ul><ul><li>“Operate as one project” as a principle </li></ul><ul><li>Actively seek vendor participation </li></ul><ul><li>Recognize that participation is an investment </li></ul>
    11. 11. The HSSP Process OMG HL7 HL7 DSTU Service Functional Model OMG RFP Technical Specification ANSI Standard
    12. 12. Understanding HSSP Artifacts, Roles, Attributes SFM Owned / Produced by HL7 Community RFP Submission Implementation Defines what a service does but not how Independent of technical platform Audience is tech leads, EAs, tech spec developers Produced / owned by OMG community Translates SFM into technical requirements ID’s supported technical platforms Audience is community with implementation interest Produced by OMG Member “Submitters” Defines the service’s technical spec Defines interfaces, platform bindings, and conformance profiles Audience is project team architect, lead developers, etc. Owned by organizations and vendors Builds the service that lives behind the interface Complies with a “conformance profile” Audience are consumers of the system or service
    13. 13. How are HSSP services expressed? Semantic Space/ Universe Formalism (Structure) Semantic Signifiers (profile-relevant semantic structures) Usage Context (interoperability paradigm) Functional Subset List (enumerate Supported Functions) Version Submitter Name Metadata Metadata Conformance Profile Semantic Profile Functional Profile Metadata
    14. 14. Why “services”?* <ul><li>A common practice in healthcare, just not yet in healthcare IT </li></ul><ul><li>Many key products use them but do not expose interfaces </li></ul><ul><li>Ensures functional consistency across applications </li></ul><ul><li>Accepted industry best practice </li></ul><ul><li>Furthers authoritative sources of data </li></ul><ul><li>Minimizes duplication across applications, provides reuse </li></ul><ul><li>Messages can be either payloads in or infrastructure beneath services </li></ul><ul><li>Service-oriented architecture provides the framework for automation of common services </li></ul>*slide adapted from a Veterans Health Administration Presentation, used with permission
    15. 15. Context of HSSP Specifications
    16. 16. Interoperability Realized page Documents Messages Services Context Constraints Requirements Model Enterprise Information Computational Engineering
    17. 17. SOA ≠ Web Services Yes No Is an industry standard? Yes Yes Is an enabler for business and IT transformation? No Yes Affects workflow and business processes? No Yes Primary ownership is business-line owned? Yes No Is a technology platform? Yes No Is a transport protocol? Web Services SOA
    18. 18. The Benefits of HSSP Standards… <ul><li>Define industry standard behaviors for healthcare-oriented service functions </li></ul><ul><li>Eliminate “different flavors” of web services from occurring in different organizations </li></ul><ul><li>Rapid-pace stds development: ~18-24 months </li></ul><ul><li>Methodology embracing cross-group standards development </li></ul>
    19. 19. Where would these specifications be used <ul><li>Inter-Enterprise (such as NHIN, RHIOs, HIE’s) </li></ul><ul><ul><li>By functionally specifying behavior, roles between applications and products are clarified, and the technologies supporting them can be profiled and sharpened </li></ul></ul><ul><li>Intra-Enterprise </li></ul><ul><ul><li>Standardization on functionality allows for better integration of off-the-shelf and custom development environments, and promotes more of a “plug and play” environment </li></ul></ul><ul><li>Intra-Product </li></ul><ul><ul><li>Facilitates vendors ability to integrate third-party value-add components and speed design phase with higher confidence </li></ul></ul><ul><li>Custom-Implementation </li></ul><ul><ul><li>Affords organizations wishing to custom-develop the opportunity to later integrate off-the-shelf </li></ul></ul>
    20. 20. The Value of HSSP … Lower cost = wider deployment = higher quality service Participation by provider and payer community is direct expression of business need Requirements definition – influence vendors in a direct way Availability of an industry-accepted component interface eases product development burden Time to market Unity in purpose and consistency in interface eases integration burden Facilitates integration Consumer demand will create increased marketplace competition Increased buyer/product offerings Using compliant products means side-by-side interoperation of multiple product offerings Multiple vendor product use/ interoperability Standard interfaces means that conformant components are substitutable Consistency at the interface level assures asset protection Specifications will support multiple topologies and technologies Promotes deployment ease and flexibility Rationale Value
    21. 21. How is this project “different”? <ul><li>Active participation from three continents and 15+ organizations </li></ul><ul><li>Significant cross-cutting community involvement </li></ul><ul><ul><li>Providers & Payers (Blue Cross/Blue Shield, DoD Military Health System, Duke University, Kaiser-Permanente, Mayo Clinic, Veterans Health Administration) </li></ul></ul><ul><ul><li>Vendors, Integrators, Value-added Providers (Booz-Allen Hamilton, CSW Group, EDS, IBM, Initiate Systems, Intel, Northrop-Grumman, Ocean Informatics, Software Partners, 88Solutions) </li></ul></ul><ul><ul><li>Governments (Canada Health Infoway, DoD Military Health System (MHS), National Cancer Institute, NeHTA (Australia), SerAPI (Finland), Veterans Health Administration, Victoria Health (Australia)) </li></ul></ul><ul><li>Managing differences between SDOs in terms of membership, intellectual property, and cost models </li></ul>
    22. 22. Why should I participate in HSSP? <ul><li>This effort is focused on and driven by business-need </li></ul><ul><ul><li>It is not an “academic exercise” striving for perfection </li></ul></ul><ul><ul><li>Standards must be used to be useful </li></ul></ul><ul><ul><li>Focused on the practical and achievable </li></ul></ul><ul><ul><li>Short timelines </li></ul></ul><ul><ul><li>Based upon business value and ROI </li></ul></ul><ul><li>Leveraging talent from multiple communities </li></ul><ul><li>Being run like a “project” and not a committee </li></ul><ul><li>We recognize that participation is an investment and not an expense </li></ul>
    23. 23. Why participate in standards at all? <ul><li>This is happening, with or without you. We’d rather it be with you… </li></ul><ul><li>Unparalleled Networking. Standards work provides access to the industry’s best and brightest </li></ul><ul><li>Benefit from “lessons learned” from others. Someone else may have already solved your biggest problem. </li></ul><ul><li>Industry Leadership. Standards work provides a platform for you to establish market presence. </li></ul><ul><li>Risk avoidance. Increasingly, standards compliance is mandatory. Make them work for you and not against you. </li></ul>
    24. 24. How do I Participate? <ul><li>Participation is open to everyone. You don’t need to be a member (though we encourage you to do so) </li></ul><ul><li>Join appropriate standards organizations </li></ul><ul><ul><li>HL7 for functional work </li></ul></ul><ul><ul><li>OMG for technical specification work </li></ul></ul><ul><li>Allocate resources to actively engage in the project </li></ul><ul><ul><li>Engage existing, knowledgeable resources in the areas they are working already. </li></ul></ul><ul><ul><li>Subgroups form based on industry need and priority </li></ul></ul><ul><ul><li>Teleconferences are weekly; meetings approximately bimonthly </li></ul></ul>
    25. 25. Who should I involve? <ul><li>Involve the staff that can best address your business needs: </li></ul><ul><ul><li>You will get out what you put in. Senior staff will drive more value and ROI to you than a junior associate. </li></ul></ul><ul><ul><li>Organizations that commit resources garner more influence and more mindshare </li></ul></ul><ul><ul><li>Your business interests are being represented by your attendees </li></ul></ul>
    26. 26. References <ul><li>All HSSP artifacts and work in process are open. Visit us at: </li></ul><ul><ul><ul><li>http:// hssp.healthinterop.org </li></ul></ul></ul>
    27. 27. <ul><li>Supplemental Slides: HSSP Stakeholder Benefits and Impacts </li></ul>
    28. 28. What Participants are Saying… <ul><li>“ Kaiser Permanente I.T. is currently transitioning to an SOA-based approach to business and systems integration. Availability of industry standard services will bring many benefits towards this goal in terms of speed of implementation, flexibility and reduced cost. I am very pleased that both HL7 and OMG are committed to this timely effort.”, Alan Honey, Enterprise Architect (Principal), Kaiser-Permanente </li></ul><ul><li>“ The creation of a health Informatics infrastructure based upon a service-based architecture grounded in comparable data has the potential to improve healthcare delivery and greatly enhance patient safety.”, Peter L. Elkin, MD, FACP, Professor of Medicine, Mayo Clinic College of Medicine </li></ul><ul><li>“ The Eclipse Foundation is pleased to support an open source project dedicated to building frameworks, components, and exemplary tools to make it easy and cost-effective to build and deploy healthcare software solutions. This Eclipse Open Healthcare Framework project will leverage the Eclipse Platform developed by IBM, Intel, Wind River, Actuate, Borland, BEA, Computer Associates and others.” Mike Milinkovich, Executive Director, Eclipse Foundation </li></ul><ul><li>“ The time is now and the place is here in this joint OMG/HL7 project. Never before has the industry been closer to cogent, clear healthcare IT data model and service standards that can provide true interoperability in a short timeframe, with open-source implementations making availability abundant.”, Richard Mark Soley, Ph.D., Chairman and CEO, OMG </li></ul>
    29. 29. For Product Consumers and Users… The Impacts and Rationale of HSSP Specifications Lower cost = wider deployment = higher quality service Participation by provider and payer community is direct expression of business need Requirements definition – influence vendors in a direct way Availability of an industry-accepted component interface eases product development burden Time to market Unity in purpose and consistency in interface eases integration burden Facilitates integration Consumer demand will create increased marketplace competition Increased buyer/product offerings Using compliant products means side-by-side interoperation of multiple product offerings Multiple vendor product use/ interoperability Standard interfaces means that conformant components are substitutable Consistency at the interface level assures asset protection Specifications will support multiple topologies Promotes deployment ease and flexibility Rationale Impacts
    30. 30. Product Vendor … The Impacts and Rationale of HSSP Specifications You can shape the standard to be supportive of your product architecture Participation provides the ability to influence the standard Ability to reuse design ideas, incorporate off-the-shelf components into value-add offerings <ul><li>Reduced time and cost to market </li></ul><ul><li>Use of 3 rd party components </li></ul><ul><li>Simplify / reuse of design </li></ul>Consumers view conformance as a confidence metric Conformance adds legitimacy to product offering Standardization of interfaces eases cost-of-entry to markets Market opportunity – ability to grow business / “Grow the pie” Rationale Impacts
    31. 31. Regulatory/Policy/Legislative … The Impacts and Rationale of HSSP Specifications HSSP is using HL7 semantics, OMG processes, IHE testing, and established technology protocols Solution that complements existing standards HSSP integrates function/ behavior, data, and protocol promoting an integrated solution set <ul><li>Offering an easy/easier solution that is complete and actionable / ease the path to adoption: </li></ul><ul><ul><li>How do we “Pick the winning horse”? </li></ul></ul><ul><ul><li>“ Opportunity cost” of using the wrong standard has big implications </li></ul></ul>Concurrent support of multiple technologies allows for technology evolution Allows for technology change within the regulation Inclusion of rigorous conformance assertions benefits compliance and verification <ul><li>Establishing objective assessment criteria: </li></ul><ul><ul><li>Measurement criteria for regulatory compliance </li></ul></ul>Rationale Impacts
    32. 32. Research … The Impacts and Rationale of HSSP Specifications Composable nature of services promotes construction Enables construction of higher-order service stacks with less investment Standard interfaces accommodate dynamic and emerging strategies and tools Facilitates responsiveness to bio-surveillance requirements Enlarges cell and sample sizes based on interoperability Leveraged use of identity service enables de-identification Enabler for collaborative studies, e.g. de-identification, retrieval, etc. Strong emphasis on semantically rigorous data and query/retrieval Promotes accessibility to “raw” information Rationale Impacts
    33. 33. Implementer/Integrator … The Impacts and Rationale of HSSP Specifications Using services speeds project design phases and promotes reuse Improved ability to deliver and support interfaces that have been implemented Allows staff and solutions to build upon the use of the standard and not technologies Creates a value offering opportunity based on the ability to deliver using these service standards By training staff in the standard, skills are portable across tools Risk mitigation (skill portability/ training advantage, vendor independence, substitutability) Use of standard in off-the-shelf tools facilitates their use Reduced integration time and cost resulting from the use of standard tooling Rationale Impacts
    34. 34. SDOs … The Impacts and Rationale of HSSP Specifications Practical, market-focus and iterative timeline promotes participation and results More members/involvement = more revenue & better specs Integration of function, data, and technology promotes leveraged reuse Promotes harmonization, cooperation, cohesion among standards communities Shortens time required to develop specifications and encourages collaboration Market-focused standards based on commercial implementations Emphasis on practicality Useable standards Rationale Impacts

    ×