12/7/2015 8:40 AM Services Ontology Development An Overview from HDTF December 2007 Ken Rubin EDS Co-Chair, OMG Healthcare Domain Task Force Co-Chair, HL7 Services-oriented Architecture SIG Ken Rubin EDS Co-Chair, OMG Healthcare Domain Task Force Co-Chair, HL7 Services-oriented Architecture SIG
Page 2 © 2006 HSSP Project, Reuse with attribution permitted First, some general context… Healthcare DTF is being re-invigorated HDTF has a critical-path dependency on Health Level Seven, a predominant healthcare SDO The selection, scope, and functionality of HDTF work is being done in HL7 Technical specification and MDA is being done in OMG
Page 3 © 2006 HSSP Project, Reuse with attribution permitted And a little more context… The project has a subgroup responsible for “infrastructure”: –Metaspecification –Inter-service relationship –“Architecture” We have discovered a number of foundational needs recurring across the specifications we are working –Dynamic discovery –Operational/Maintenance functions –Non-vertical domain semantics
Page 4 © 2006 HSSP Project, Reuse with attribution permitted Overview of HSSP (HDTF + HL7) Activities Reference Architecture Taxonomies, Business Rules, Choreographies Profile Methodologies Template Registry Service Meta-model Evangelizing SOA within the Healthcare community Further Service Specifications
Page 5 © 2006 HSSP Project, Reuse with attribution permitted So, what is the need? HDTF has identified a need to be able to self- describe, register, navigate, and discover services and service capabilities In the four specifications we are working, the demand for this capability has been recurring Nothing about this need is healthcare-specific We have not been able to discover an ontology that meets our needs
Page 6 © 2006 HSSP Project, Reuse with attribution permitted Use Cases Finding the right instance of specialized “ordering” services within a large enterprise (where each has tailored business rules specific to the subspeciality.) Finding those services across a region containing diagnostic imaging capabilities Locating the appropriate decision support service based upon a specific need or clinical condition
Page 7 © 2006 HSSP Project, Reuse with attribution permitted Our Service Ontology solution must… …be able to describe the nature of the service behavior (function) …support classification of information viewpoint in the description / service ontology …support stratification and inter-service relationships …be formal and rigorous, allowing registration, navigation, and query based on functional capability …provide mechanisms for vertical-domain or locality extension(s) where appropriate …be freely usable (e.g., no IP encumbrances)
Page 8 © 2006 HSSP Project, Reuse with attribution permitted References Healthcare Services Specification Project Wiki HL7 Website:
Page 9 © 2006 HSSP Project, Reuse with attribution permitted Thank you! Ken Rubin, EDS desk mobile