Ontology Pragmatics : BCM

1
Ontology Pragmatics BCM e-Business Registry
Repository

• E-Knowledge Economy
• Knowledge Interoperation Mediation
• BCM Business Centric Guidelines
• Semantic Federation
• Co-operating Registry Repository
• Communities of Interest Affinity Domain
• Semantic Content Management
• Controlled Vocabularies
• Choice Points Contextual Validation

Deep Dive
2
Carl Mattocks _at_ CHECKMi.com

• Co-Chair (ISO/TS 15000) ebXMLRegistry Semantic
  Content SC
• Co-Chair Business Centric Methodology TC
• CEO CHECKMi
• Multiple Agent Training Engine (MATE) binding
  1000 databases
• Knowledge Compendium (.Net open source code)
• Crosswalk UDDI / ebXML Registry / IMS Repository
• Multiple Taxonomies, Z39.50 SRW Gateway, XACML

3
21st Century e-Knowledge Economy
Human Capital
Competitive Capability
Knowledge IP
Co-opetition
Skills Capacity
Productivity Efficiency
Communities of Interest
Community Trust
Communities of Practice
Standards for Business Process Workflow Quality
of Service Agreements
Best Practice Collaboration Protocols Policies
Service Architecture Networking Infrastructure
Co-operating Registries
Peer to Peer Repositories
Semantic Information Grids
e-Ology e-Business
e-Population
4
e-Society Knowledge Mediation Interoperation
e-Community of Practice
e-Research
e-Science
Knowledge Mediation Interoperation
e-Learning
e-Government
e-Health
e-Business
e-Community of Interest
5
Knowledge Mediation Goals Re-Use, Re-Usable,
Re-Useful

• Support Communities of Practice Communities of
  Interest
• Locally, regionally, nationally, internationally
• Use Natural Knowledge models suitable for wide
  audience not just IT support specialists e.g. the
  Patient
• Ability to mitigate business vocabularies and
  multi-lingual challenges
• Automate sharing Semantically rich MetaData e.g.
  e-Health
• provide discovery, understanding, and exchange of
  Electronic Health Record (EHR) information
• Enable Providers, Pharmacy, Health Plans / PBMs
  (pharmacy benefit management), and other Agencies
  to create service processes that support
  internationally agreed business process
  definitions, trust mechanisms and process control
  methods

6
Business Centric Methodology COI Interoperation

• Enables precise communication between business
  users and technical experts enterprise
  applications and their respective business
  partner systems
• Involves a layered approach for strategically
  managing Service Oriented Architecture artifacts
  and constraints while achieving semantic
  interoperability

7
Conceptual Layer Community of Interest Semantics
Business Usage Semantics
System Interoperability
OWL-S Ontology Templates SKOS Archetypes
RDFS / UML / Topic Map / UNSPSC
DTD / XML Schema / Dublin Core
Object Oriented Model / Thesaurus
Info Engineering Model
Data Dictionary
Data Usage Semantics
Service Quality
8
BCM Conceptual Layer COI Semantic Federation

• Role - Semantically connect Facts and Facets
• Provide trace-ability from business vision to
  system implementation
• Ensure alignment of business concepts with
  automated procedures
• Facilitate faster information utilization between
  business parties
• Enable accurate information discovery and
  synchronization
• Integrate information by interest, perspective or
  requirement
• Resource - COP knowledge organization systems
• SKOS Core http//www.w3.org/2004/02/skos/core/
• Classification constraint schemes for artifacts
  e.g. e-Health archetypes

9
COI Knowledge Registry Repository Needs

• A Federated Knowledge Registry not only acts as
  an interface to a Repository of stored content,
  it formalises how information is to be registered
  and shared beyond a single enterprise or agency.
• Specifically, a Federated Registry Repository
  capability is required when there is a need for
  managing and accessing metadata across physical
  boundaries in a secure manner. Those physical
  boundaries might be the result of
  community-of-interest, line of business, system,
  department, or enterprise separation.
• Irrespective of the boundary type, a Federated
  Registry Repository must enable users to
  seamlessly access, share and perform analysis on
  information, including
• Maps of information dependencies across workflow
• evidence of quality, statements of provenance and
  assurance
• policies supporting security and privacy
  requirements e.g. HIPAA.

10
COI Registry Repository Federated Content

• Mappings for the critical path of information
  flowing across a business value chain e.g.
  ordering payment of e-Prescription
• Quality indicators such as statements of
  information integrity, authentication and
  certification e.g. electronic signature used for
  e-prescribing
• e-Business Components (e.g. XSDs, Elements,
  Templates) and Universal Semantics Management

11
COI Component Management Knowledge

• Interacting entities need re-usable data (items)
  with known semantics
• These items are required as (XML) Schema
  components
• The Schema (document) and the Components must be
  shared within and often outside the organization
• Components may use external components such as
  code lists
• Domain Components must be managed cooperatively
• Core components must be common
• Data definition arbitration agreements are
  essential
• Data types must be standardized

12
ISO/TS 15000 OASIS ebXML Registry

• One interface (HTTP, SwA, ebMS) to classified
  knowledge content
• Electronic Forms
• Web Services WSDL / WSRP
• Collaboration Agreements
• Business Process Requirements, Objects, Data
• Domain specific Semantics and Relationships
  between Assets Artifacts
• SQL queries and APIs

13
e-Business Knowledge XML Registry Version 3

• Registration and classification of any type of
  artifact
• Namespaces defined for certain types of content
• Messages defined as XML Schemas
• Taxonomy hosting, browsing and validation
• Links to external content
• Built-in security (SAML)
• Event notification, Event-archiving (audit trail)
• Life cycle management of objects
• Federation for inter-registry relocation,
  replication, references
• metadata is stored in one registry a registry
  may cooperate with multiple federations for the
  purpose of federated queries

14
ebXML Registry Information Model (RIM) - COI
Classification
Classification trees constructed with
ClassificationNodes are used to define the
structure of Classification schemes or ontologies
RegistryObject
ClassificationNode
Classification
Association
RegistryEntry
A Classification instance identifies a
ClassificationScheme instance and taxonomy value
defined within the classification scheme
RegistryPackage
ExtrinsicObject
Service
ClassificationScheme
The structure of the classification scheme may be
defined internal or external to the registry
Person
15
NIST HL7 e-COI Registry of DMIMs, RMIMs, HMDs,
and MessageTypes

• HL7-specific classification schemes, especially
  the code hierarchies for the structural
  attributes in the RIM.
• RMIM static models from technical domains,
  including finance, Patient Administration,
  Scheduling, Laboratory Orders, Research Trials,
  Pharmacy, Medical Records, Common Message Types,
  Message Control, Master File, and Clinical
  Documents
• RMIM static models from the CMETs domain, each
  with a an association to the DMIM it is derived
  from (using external identifiers to the HL7
  identification schemes) with external links to
  diagrams and descriptions, and a number of
  classifications by specific codes that are fixed
  by constraints on the RMIM.
• RMIMs leads to one or more derived HMDs and
  MessageTypes.
• Each registered artifact has ExternalLinks to its
  base UML diagrams, long html descriptions, and
  other visual display aids for presentation of
  base classes, attributes, relationships, and
  constraints.
• OWL-related template artifacts submitted by HL7
  participants active in the Templates technical
  committee

16
IHE Integration XDS Affinity Domain Sharing

• The XDS Cross Enterprise Clinical Documents
  Sharing profile defines the (document) Registry
  as an actor that maintains metadata about each
  registered document in a document entry
  enforces policies at the time of document
  registration
• An XDS Document is a composition of clinical
  information that contains observations and
  services for the purpose of exchange with the
  following characteristics Persistence,
  Stewardship, Potential for Authentication, and
  Wholeness (characteristics that are well defined
  in the HL7 CDA)
• An XDS Folder provides a collaborative mechanism
  for several XDS Document Sources to group XDS
  Documents for a variety of reasons. XDS Documents
  may be placed into an existing Folder at any
  time, as long as they relate to the same patient.
• A Document Source may only contribute documents
  with Document Codes and Health Facility Codes
  that draw from a Vocabulary Value Set that is
  approved by the Affinity Domain.

17
XDS does not focus on Ontology .. however

• BCM COI XDS Affinity Domain defined by formal
  or informal organizational structures
• Clinical information exchange exploits Controlled
  Vocabularies
• Ontological Layers
• Upper level ontology is focused on the
  non-volatile language and principles of a domain
• Lower ontology is focused on the knowledge
  specific to particular community of practice (as
  formulated by the recognized experts)

18
Ontology other Semantic Content Considerations
.. artifacts that help agents communicate,
coordinate, collaborate

• XML provides syntax for structured documents, but
  imposes no semantic constraints on the meaning of
  these documents.
• XML Schema is a language for restricting the
  structure of XML documents and also extends XML
  with datatypes.
• RDF is a data model for resources and relations
  between them.
• RDF Schema is a vocabulary for describing
  properties and classes of RDF resources, with a
  semantics for generalization-hierarchies of such
  properties and classes.
• OWL adds more vocabulary for describing
  properties and classes e.g. relations between
  classes, cardinality, equality.
• SKOS-Core is an RDF OWL schema for
  representing controlled vocabularies and other
  types of Simple Knowledge Organization Systems .

19
COI CHI (Consolidated Health Informatics)
portfolio of Clinical Vocabularies

• National Council on Prescription Drug Programs
  (NCDCP) standards for ordering drugs from retail
  pharmacies.
• The Institute of Electrical and Electronics
  Engineers 1073 (IEEE1073) series of standards
  that allow for health care providers to plug
  medical devices into information and computer
  systems
• Digital Imaging Communications in Medicine
  (DICOM) standards that enable images and
  associated diagnostic information to be retrieved
  and transferred from various manufacturers'
  devices
• Laboratory Logical Observation Identifier name
  Codes (LOINC) to standardize the electronic
  exchange of clinical laboratory results.

20
BCM Choice Points Ontological Templates
Archetypes

• Template Archetype Choice Points significantly
  aids to comprehensibility, alignment, while
  promoting tracing and accountability when
• archetype is a computable expression of a domain
  level (clinical) concept in the form of
  structured constraint statements, based on some
  reference model (RMIM)
• archetypes are aligned with Affinity Domain
  concepts
• archetypes all have the same formalism i.e. may
  be part of a COP ontology but belong to only one
  or other ontological level
• template is used to narrow the choices of
  archetypes for local or specific purposes (DMIM).
  
• archetype defines constraints on reference model
  instances which express valid structure (i.e.
  composition, cardinality).
• archetype defines constraints on instances of a
  reference model which express valid types and
  values.

21
Challenge of Ontology Annotated e-Health Services

• e-Health service information can be managed by
  two different e-Health service entities using
  different message structures.
• ARTEMIS project providing a standard way of
  accessing the data by registering storing
• ontologies based on existing healthcare
  standards,
• the semantic mapping between these ontologies,
• invoke each others web services by semantic
  mediation.
• Discovery of Services stored in a Registry need
  semantic service registry query mechanisms that
  leverage previous research linking OWL to the
  Registry Information Model

22
Linking OWL to ebXMLRegistry Objects
23
With thankful links to

• Members of ebXMLRegistry Semantic Content SC
• http//www.oasis-open.org/committees/sc_home.php?w
  g_abbrevregrep-semantic
• Members of Business Centric Methodology TC
• http//www.oasis-open.org/committees/download.php/
  5931/BCM20Executive20Brochure.pdf
• Contact CarlMattocks_at_CHECKMi.com