1 / 19

HL7 SOA Interoperability Paradigm, Dynamic Model, and Conformance Patterns

HL7 SOA Interoperability Paradigm, Dynamic Model, and Conformance Patterns. January 2008 WGM, San Antonio, TX. John Koisch, Booz Allen Hamilton Alan Honey, Kaiser Permanente Charlie Mead, Booz Allen Hamilton. Contents. Introduction, Purpose and Vision Analysis Framework (RM-ODP)

terena
Download Presentation

HL7 SOA Interoperability Paradigm, Dynamic Model, and Conformance Patterns

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HL7 SOA Interoperability Paradigm, Dynamic Model, and Conformance Patterns January 2008 WGM, San Antonio, TX John Koisch, Booz Allen Hamilton Alan Honey, Kaiser Permanente Charlie Mead, Booz Allen Hamilton

  2. Contents • Introduction, Purpose and Vision • Analysis Framework (RM-ODP) • Methodology (SIP) • The Dynamic Model (CDL) • Worked Example • Conclusions and Next Steps

  3. Link • Based on Healthcare Interoperability: A Service-Based Paradigm, Conformance Model, and HL7 Dynamic Model • Link: http://hssp-implementation.wikispaces.com/SOAInteroperabilityParadigm

  4. Introduction and Purpose • This deck summarizes the current state of work being carried out by the SOA SIG on the “Service Interoperability Paradigm” • This arose from a Birds of a Feather discussion in Atlanta among members of MnM, InM, ITS and SOA • “The HDF should work towards a single framework for interoperability paradigms so that technical artifacts only need to be defined once and can migrate across the paradigms as appropriate” • “Define Once, Reuse Everywhere” • To Include the choice of Interoperability Paradigm in the HDF as a methodological step and as a set of pathways for development of standards and implementations • SOA Sig should define the Services Interoperability Paradigm • SOA Sig should define the Service Conformance Levels

  5. Vision: Services, Documents, Messages Orchestration, Choreography, and Interaction Patterns Services Contents: Domain & Document Models Trading Partner Agreements: Binding Services and Content Models Made by HL7, IHE, Realms, Projects Messaging: Binding the Services and Contents to a transportation Platform (HL7 Wrappers & ATS)

  6. RM-ODP Framework • Candidate Framework: Reference Model for Open Distributed Processing (RM – ODP, ISO/IEC IS 10746 | ITU-T X.900 ) • Two Components • Consists of Five non-hierarchical Viewpoints for specifying an Composite Architecture • Ontology • Facilitates the communication between and among viewpoints • Creates language for Conformance Testing

  7. Five RM-ODP non-hierarchical Viewpoints(each Viewpoint has multiple layers) Why? What? How? Where?

  8. The SOA IP Methodology

  9. Standardization and the HSSP Methodology

  10. Standardization and the Methodology (cont’d)

  11. Conformance

  12. The Dynamic Model • Package = Interoperability Contract Specification • Roles, Behaviors, Responsibilities, Participations • Channels, Information Types • Relationships, Behaviors • Choreographies, per se, are Computational constructs • Encapsulated Interactions, Exchanges • Logical Work Flows

  13. Choreographies • CDL rigorously expresses the concepts of the SOA Dynamic Model

  14. CDL Tooling

  15. The Service Specification Methodology and Framework (Detail)

  16. Sample (from SOA IP Draft) • MDA-based partial worked example from business analysis through technology specification • Business Process incorporating Encounter, Lab Order, Lab Result, and Notification • UML is used to capture analysis artifacts through all levels of specification • CDL is used to rigorously define behavioral semantics (and expresses the dynamic model)

  17. Conclusions Using CDL, we have defined the methodology for the Service Interoperability Paradigm. It is capable of fully expressing the requirements of the HL7 Dynamic Model within the SOA IP We have defined the expression of the conformance points and their content There are several outstanding follow-up items around tooling and maturing the CDL spec We believe that this Dynamic Model approach is directly applicable to other Interoperability Paradigms (Messaging and Documents)

  18. Recommendations and Next Steps • Resolve the outstanding issues with CDL (standard) • Resolve the outstanding issues with CDL tooling • SOA Sig finalization of SOA IP • Incorporate the SOA IP into the HDF • Contribute to the ARB’s 2008 goal of a robust Dynamic Model (across all three Interoperability Paradigms) harmonized with the Computational and Informational Viewpoint’s artifacts

  19. Questions? • Presentation available at: • http://hssp-implementation.wikispaces.com/SOAInteroperabilityParadigm

More Related