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
21 st Century : e-Knowledge Economy Human Capital Competitive Capability Co-opetition Skills Capacity Productivity & Efficiency Communities of Interest Community Trust Communities of Practice e-Ology e-Business e-Population Co-operating Registries Peer to Peer Repositories Service Architecture & Networking Infrastructure Standards for Business Process Workflow & Quality of Service Agreements Best Practice Collaboration Protocols & Policies Knowledge & IP Semantic Information Grids
e-Society : Knowledge Mediation & Interoperation e-Health e-Learning e-Research e-Government e-Community of Interest e-Community of Practice e-Business e-Science Knowledge Mediation & Interoperation
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 / PBM’s (pharmacy benefit management), and other Agencies to create service processes that support internationally agreed business process definitions, trust mechanisms and process control methods
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
Conceptual Layer : Community of Interest Semantics Business Usage Semantics Data Usage Semantics System Interoperability Service Quality Data Dictionary Info Engineering Model Object Oriented Model / Thesaurus DTD / XML Schema / Dublin Core RDFS / UML / Topic Map / UNSPSC OWL-S Ontology + Templates + SKOS + Archetypes
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
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 .
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
Registry D Registry E Registry B Registry A Registry C
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
ISO/TS 15000 OASIS ebXML Registry
One interface (HTTP, SwA, ebMS ) to classified knowledge content :
Web Services WSDL / WSRP
Business Process Requirements, Objects, Data
Domain specific Semantics and Relationships between Assets & Artifacts
SQL queries and APIs
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
ebXML Registry Information Model (RIM) - COI Classification RegistryObject ClassificationNode Classification RegistryPackage ExtrinsicObject Service Association RegistryEntry ClassificationScheme The structure of the classification scheme may be defined internal or external to the registry A Classification instance identifies a ClassificationScheme instance and taxonomy value defined within the classification scheme Classification trees constructed with ClassificationNodes are used to define the structure of Classification schemes or ontologies Person
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
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 .
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
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)
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 .
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.