03-23-05
                                                         April 2008



Interoperability, Information Fidelity, an...
What is Interoperability?


        Quiz time. Are you interoperable…

                 – … if you and your business partn...
What is information fidelity?


            Quiz time. Do you have rich, robust information if….


                       ...
The beauty of standards…


                                                             Messaging Standards
              ...
SOA ≠ Web Services



                                                                         SOA                    Web ...
Our Challenge…




                 “How do you know that the [web-]
               services you’re building are not just ...
Addressing the Two Dimensions of Interoperability


                                                                Ideal ...
Designing for                                                                                                             ...
What is the Healthcare Services Specification Project ?

                 • Standards specifically to support healthcare S...
What does this have to do with SOA?



              • Provides authoritative “sources of truth” within an
               ...
Why hold a conference on SOA and Health Quality?



              • To break the “log-jam” between IT companies, healthcar...
Our risk…




                    “It is cheaper and easier than ever to create
                     badly designed applic...
Thank you!




                                                                                Ken Rubin
                 ...
Upcoming SlideShare
Loading in …5
×

Interoperability, Information Fidelity, and the ...

329 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
329
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Interoperability, Information Fidelity, and the ...

  1. 1. 03-23-05 April 2008 Interoperability, Information Fidelity, and the Need for SOA Healthcare Standards Ken Rubin (ken.rubin@eds.com) Chief Healthcare Architect, EDS Federal Health Portfolio Chair, OMG Healthcare Domain Task Force page 1
  2. 2. What is Interoperability? Quiz time. Are you interoperable… – … if you and your business partners speak different languages – … if gender = “01” means “male” in your business and “female” for your business partner? – …if information sharing is primarily by fax or e-mail? – … if electronic data is exchanged via DVD-ROM? – …if you use XML? – …if you use Web Services? SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 2
  3. 3. What is information fidelity? Quiz time. Do you have rich, robust information if…. – … the definition of “episode” differs within your organization? – … your IT systems require users to capture coded data? – … you lack processes to validate accuracy of data entry? – … you allow localized extensions to your common data set? – … business rules are inconsistently enforced depending upon the applications being used – … two systems within your organization have the same data content (but that content differs)? SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 3
  4. 4. The beauty of standards… Messaging Standards • HL7 Terminology Standards • X.12 “Functional” Standards; • NCPDP Structured Doc Standards • ASTM Services Standards • OMG Standards Profiling • DICOM • IHTSDO/SNOMED • ICD • LOINC • IHE • CEN TC 251 • ISO TC 215 SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 4
  5. 5. SOA ≠ Web Services SOA Web Services Is a technology platform? No Yes Is a transport protocol? No Yes Primary ownership is business-line owned? Yes No Affects workflow and business processes? Yes No Is an enabler for business / IT transformation? Yes Yes Is an industry standard? No Yes SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 5
  6. 6. Our Challenge… “How do you know that the [web-] services you’re building are not just the next generation of stovepipes?” Janet Martino, LTC, USAF (Retired), to a panel of Healthcare IT Leaders SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 6
  7. 7. Addressing the Two Dimensions of Interoperability Ideal Target • Behaviorally, there are a SNOMED-CT lot of solutions Semantics • Need to marry Semantic Interoperability with Behavior • The touchstone business OWL-S case is the notion of ISO-11179 automated discovery, Web Services composition, and delivery UDDI v3 Java RMI CORBA Behavioral SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 7
  8. 8. Designing for High Interoperability Ability to Interoperate Low SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 8
  9. 9. What is the Healthcare Services Specification Project ? • Standards specifically to support healthcare SOA • Establish industry-accepted “SOA Service” definitions, functions, behavior, (functional and technical specs) • Joint effort involving HL7, OMG, Open Health Tools (OHT), and IHE HL7 Domain OMG Committees HSSP’s Objectives: Methodology (SSF), • To create useful, usable healthcare standards that address functions, DSTU Feedback, Consultative support RFP OpenEHR Requirements semantics and technologies Technical CEN SFMs, Specifications, Methodology, Info Models, RFP process HL7/SOA Harmonization Requirements, SOA Interop Specs • To complement existing work and Service Profiles leverage existing standards Info Models, Service Profiles Semantic Profiles SOA Interoperability Specifications Open Source • To focus on practical needs and National HSSP not perfection Ref Implementations, Tools Programs (e.g. OHT ONC, NEHTA) Policy Technical Specifications • To capitalize on industry talent Integration Profiles, Conformance Testing, Interoperability Validation through open community Use Cases, Candidate Standards SOA Interoperability Specifications , participation Use Cases, Use Profiles Requirements HITSP IHE SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 9
  10. 10. What does this have to do with SOA? • Provides authoritative “sources of truth” within an organization • Well defined, cohesive functions that are reused promotes consistency (e.g. shared business rules) • Authoritative sources minimize unplanned redundancy and promote information quality • Healthcare-specific SOA services may also define information constructs (e.g., consistent semantics) • SOA allows for precise, rigorous expression of function (e.g., behavior) and access to those functions by others • Promote interoperability by defining interfaces that focus on function and not on technology, and supporting standards • Improve fidelity through use of formally expressed information constructs built on coded data and ontology SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 10
  11. 11. Why hold a conference on SOA and Health Quality? • To break the “log-jam” between IT companies, healthcare software vendors, and healthcare organizations • Health care as a domain sector is different. That said, not everything is different. We can learn from others. • Without considering quality impact, this would be “just any other” SOA conference • Eliminate the perception that nobody in health care is doing anything using SOA • To get beyond the hype. While not a “silver bullet” it provides some real benefits to the health industry MOST IMPORTANTLY, this event will allow us to share experiences, network with colleagues, and learn the tricks and traps that our peers have encountered. SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 11
  12. 12. Our risk… “It is cheaper and easier than ever to create badly designed applications and spaghetti integration.” Alan Honey, Enterprise Architect, Kaiser-Permanente SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 12
  13. 13. Thank you! Ken Rubin Chair, OMG Healthcare Domain Task Force Healthcare Architect Kenneth_S_Rubin@omg.org ken.rubin@eds.com SOA, Healthcare, and Reference Architectures April 2008 © 2008, All Rights Reserved, Reuse with Attribution Permitted page 13

×