12/7/2015 8:40 am services ontology development an overview from hdtf december 2007 ken rubin eds...
TRANSCRIPT
04/21/23 11:55
Services Ontology DevelopmentAn Overview from HDTF
Services Ontology DevelopmentAn Overview from HDTF
December 2007December 2007
Ken RubinEDS
Co-Chair, OMG Healthcare Domain Task Force
Co-Chair, HL7 Services-oriented Architecture [email protected]
Ken RubinEDS
Co-Chair, OMG Healthcare Domain Task Force
Co-Chair, HL7 Services-oriented Architecture [email protected]
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 2
First, some general context…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
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 3
And a little more context…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
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 4
Overview of HSSP (HDTF + HL7) ActivitiesOverview 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
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 5
So, what is the need?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
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 6
Use CasesUse 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
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 7
Our Service Ontology solution must…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)
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 8
ReferencesReferences
• Healthcare Services Specification Project Wiki
• http://hssp.wikispaces.com
• HL7 Website:
• http://www.hl7.org
© 2006 HSSP Project, http://hssp.wikispaces.com
Reuse with attribution permitted Page 9
Thank you!Thank you!
Ken Rubin, EDS
+1 703 845 3277 desk
+1 301 335 0534 mobile