Healthcare Data Interpretation Facility HDIF Revised Submission

1
Healthcare Data Interpretation Facility (HDIF)
Revised Submission

• CogniTech Corporation
• Concept Five Technologies
• Hitachi
• Los Alamos National Laboratory (LANL)
• Theragraphics

2
Summary

• Submission Status
• Design Objectives
• Content of the Submission
• Issues
• Next Steps

3
Initial Submissions

• RFP Issued April, 1998
• Initial Submissions December, 1998
• Chiron Informatics
• CogniTech
• Concept Five / Hitachi
• LANL / Theragraphics
• Presented at January, 1999 OMG Meeting
• Decision to Merge Submissions

4
Progress on Merged Submission
5
Submitters Contact Information
6
How We Integrated Submissions

• CogniTech Initial Submission
• High Level Information Model
• Healthcare Specific Functionality and Scenarios
• Concept Five / Hitachi Initial Submission
• Low Level Services Model
• DataItems
• Metadata Model using XMI
• All Submitters
• Merged Submissions and Simplified Interfaces

7
Mandatory Requirements

• Multiple Forms of Intelligent Data Transforms
• Chaining
• Supplemental Information
• Introspection
• List of Relevant Healthcare Standards
• Support for Publicly Available Vocabularies
• COAS, LQS, and PIDS Alignment

8
Optional Requirements

• Data from Sources Not Compliant with COAS
• Non-clinical Data
• Support for Proprietary Vocabularies
• Confidence or Uncertainty Values for Outputs
• Object Wrapper to Pass Character Data

9
How the HDIF Addresses the Requirements
HDIFManager
Clinical Inputs, Engine Selection, Control
Parameters
HDIF Client
DSSEngineExecute
10
Changes Since Last Meeting

• Added significant detail to the description of
  HDIF DataItems
• Section 6.2 - UML Model now includes operations
  on classes
• IDL Guide has been added including detailed
  textual descriptions of operations, attributes
  and exceptions on all DataItem types
• Document Formatting

11
Content of the Submission

• DSSEngine (wraps processing)
• DataItems (wraps state)
• HDIFManager
• Design Patterns for Running Engines
• Supplemental Information
• Metadata

12
DSSEngine Interfaces
DSSEngineExecute
Factory
Conversion
Synchronous
Asynchronous
HDIF Compliant DSS Engine
DSS Engine
HDIFManager
13
DataItems
14
DSSEngine
15
DSSEngine Execute
16
Additional DSSEngine Interfaces
17
IO Set
18
DataItems
19
Details on DataItems

• Framework that supports range of commonly found
  data types
• Table, Name/Value, XML, simple MIME
• Extensible to domain
• COAS
• Heavily reuses existing OMG standards where
  standards support requirements
• Property Service
• Negotiation Facility (for XML/DOM)
• COAS
• Adds interfaces to support MIME and Tables
• Table types reuse many Property Service data
  types and follow similar approaches for accessing
  data

20
DataItem
21
PropSet
22
ConstrainedPropSet
23
MIME
24
AbstractTable
Note Exception definitions deleted
25
Table
26
ConstrainedTable
27
SequentialTable
28
Document
29
HCObservation
30
Supplemental Information andReferences
31
Supplemental Information Links
32
Role of HDIFManager

• Inherit from DSSEngine
• Manages Chaining
• Manager-specific Logging
• Locating Engines

33
Metadata

• UML Foundation
• XMI Representation
• OCL for Constraints
• Need to Validate
• Consistency with Ontologies
• Satisfaction of Constraints

34
Related Standards Efforts

• Healthcare
• OMG COAS, LQS, HRAC, PIDS
• HL7 Templates
• Outside Healthcare
• W3C Document Object Model (DOM) / OMG support of
  DOM
• OMG EAI SIG, Intelligent Agents RFI, Simulation
  SIG, Logging Facility

35
Issues

• Role of HDIFManager
• Ontology/XML Representation for Metadata, and
  tie-in to HL7
• Complete Alignment with RAD and OMG Logging
  Facility
• LQS tie-in
• Refine supplemental information and add
  operations
• Conformance Levels

36
Next Steps

• Vote for Extension of Final Submission Deadline
• Continue to Progress on Standard
• Complete UML Model, Generate IDL, Create RM-ODP
  Specification
• Form Evaluation Committee
• Submit Final Submission for March OMG Meeting