1 / 19

SOA Sig Progress Report

EHR TC, September 2007. SOA Sig Progress Report. John Koisch OCTL Consulting SOA Sig Co-Chair. Outline. Progress Report on the SOA Sig HL7 and the SOA Sig – Strategic Issues Ongoing Efforts at EHR FM / SOA Sig alignment Examples: Web Services vs Services vs SOA

willem
Download Presentation

SOA Sig Progress Report

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. EHR TC, September 2007 SOA Sig Progress Report John Koisch OCTL Consulting SOA Sig Co-Chair

  2. Outline • Progress Report on the SOA Sig • HL7 and the SOA Sig – Strategic Issues • Ongoing Efforts at EHR FM / SOA Sig alignment • Examples: • Web Services vs Services vs SOA • An informal SOA Architecture • Retrieve, Locate, and Update Specification as an example

  3. The HSSP The Healthcare Services Specification Project (HSSP) is a joint venture between Health Level 7 (HL7) and The Object Management Group (OMG). HSSP relies on HL7’s domain expertise and world-class information models to provide Functional classifications, requirement, and focuses OMG brings the technology industry to the table by issuing a Request for Proposal (RFP). Companies create the Technical Specification HSSP is young – it has been around for 18 months or so, and is growing

  4. The HSSP Process HL7 HL7 SOA SIG Service Functional Model OMG HL7 DSTU OMG HDTF OMG RFP ANSI Standard RFP Responders Technical Specification

  5. Current Specifications

  6. HSSP Timeline

  7. And what is HSSP working on next? • Reference Architecture • Taxonomies, Business Rules, Choreographies • Profile Methodologies • Template Registry • Service Meta-model • SOA 4 HL7 • Evangelizing SOA within the Healthcare community • Service Specifications

  8. HL7 and the SOA Sig SOA Sig occupies an interesting place in HL7: • Focused on Methodology • HL7 Dynamic Model analysis, Interoperability Paradigms • Focused on Implementation Guides • Focused on re-using high-quality domain content in real world systems • Templates SIG • Strong ties to outside organizations • The HSSP process and products have been endorsed by The Eclipse Project We have found that SOA is not just a technological shift or a strategic initiative, but really a paradigm shift

  9. Paradigm Shifting In a word, SOA is trying to take HL7 into a different paradigm than messaging • Different governance models • Different Design and Implementation Patterns • Different provisioning patterns

  10. Aligning with the EHR FM • We feel that there are strong opportunities to tie EHR implementation to the SOA process, architecture, and products • In every SFM, there is a place to talk about aligning the SFM content / intent with the EHR FM • We have struggled because of the paradigm differences • We would welcome more opportunity to align

  11. Aligning with the EHR FM, ii

  12. HL7 EHR System Functional Model (EHR-S)(> 230 System Functions in 4 level categorization(see attached spreadsheet for full enumeration) Business Choreography Choreography Business Entity (Information) Service Types Business System Functions Infrastructure Entity (Information) Infrastructure Infrastructure Infrastructure Business Choreography NOTE: “Other” Category - The EHR-S model does NOT include Electronic Resource Planning (ERP) / Logistics and Financial components, which are needed for completeness of a military EHR.

  13. Web Services v Services v SOA

  14. A common conception of Healthcare SOA PACS radiology PACS cardiology Lab. Pharmacy Order entry MPI Billing • This is a decent view of business communications • This is good context • This is a nice org chart This is bad SOA From http://hssp-infrastructure.wikispaces.com/space/showimage/CORBAmed_2000_05_01_ROADMAP_2_0.doc

  15. Management Management Towards a Better SOA Order Management Service Party Management Facility Order Entry Service Clinical Image Access Service Resource Access Control Service Clinical Observation Access Service Health Information Locator Healthcare Relationship Service Terminology Query Service Person Identification Service Person Demographic Service Architect’s View for Clinical Systems Development From http://hssp-infrastructure.wikispaces.com/space/showimage/CORBAmed_2000_05_01_ROADMAP_2_0.doc

  16. RLUS Specification • The gauntlet (Use Cases): • We want functional consistency across service deployments with the ability to bind to different Information constructs • Example 1: What if you want to create a service that provides vital signs given a patient id? • Example 2: What if you want to bind the consumer to a single static model that may encompass many other static models? • The CCD (CCR for CDA) has a template for conformance that references 18 models • What if you wanted to create an MPL from n sources that were each modeled differently?

  17. RLUS • An RLUS instance contains: • A Functional Profile – An Instance’s Supported Operations • A Semantic Profile – the composition of semantic signifiers • Is guaranteed to self-describe through well-known interfaces

  18. Sample RLUS Dependencies

  19. Questions … ? jkoisch@octlconsulting.com http://healthinterop.org

More Related