Integration of Information for Manufacturing and Compliance

1
Integration of Information for Manufacturing and
Compliance

• Jack W Smith, MD PhD
• Dean School of Health Information Sciences
• UTHSC-H

2
Conceptualize at Three Levels

• Informatics Information and Knowledge
• Computer Science Computation
• (representation of knowledge and information 8
  vs. 100)
• Information Technology Hardware/Software
  Communication Infrastructure

3
What Are We Integrating?

• Product Lifecycle Management (PLM)
• Enterprise Resource Planning (ERP)
• Supply Chain Management (SCM)
• Organizational Productivity, Portals and
  Collaboration
• Data and Information Management
  www-306.ibm.com/software/solutions/SMB/L/indust
  ry_overview.html

4
Why Are We Integrating Enhances Critical
Competencies

• Integrated communication and collaboration
• Customer service
• Accurate estimating and quoting
• Flexible production planning
• Efficient project managementwww.microsoft.com/Bu
  sinessSolutions/industry/

5
Industry Specific Pharmaceuticals and
Biotechnology

• Accelerate and Optimize the Discovery Pipeline
• Improve Operational Efficiencies and Outcomes in
  Clinical Trial Management
• Reduce Risk Through Process Validation and
  Compliance
• Increase Marketing, Sales, and Service
  Effectivenesshttp//www.oracle.com/industries/li
  fe_sciences/pharm.html3

6
Fundamental Problems and Common Approaches

• Cut across application areas
• There is overlap
• Analogical problem-solving is fundamental to
  making progress
• Information overload
• Data management
• Visualization
• Decision support
• Distance as a barrier
• Social, organizational, economic issues
• Evaluation

7
Industry-Wide IT Failure

• Rates shown are average of 13,522 projects
  across industry
• The risk of failure is even greater for larger
  projects

Source CHAOS Report. The Standish Group, 2004
From Keith Butler at Boeing
8
Integration is NOT an IT project

• More than 50 HIT projects fail
• Most of these failures are NOT due to flawed
  technology
• But due to the lack of systematic considerations
  of non-technology issues
• usability
• workflow
• organizational change
• error
• process reengineering

9
Usability What?

• Usability refers to how usable a product is for a
  human user in terms of
• ease of use
• ease of learning
• subjective satisfaction
• flexibility
• customizability
• user error Dr. Jiajie Zhang http//www.shis.uth.
  tmc.edu/

10
Vocabularies and Standards

• Naming concepts and relating them to each other
• Standards agreed-upon conventions
• Allow communication
• Ex Start numbering with 0 vs. 1Dr. Todd
  Johnsonhttp//www.shis.uth.tmc.edu/

11
Standard for SCM Rosetta Net

• Universal standards for the global supply chain
• Open, non-profit consortium of industry leaders
• User driven standards development process
• Increases efficiency of collaborative commerce
  for organizations of any size
• Implement and certify adoption of these standards
• Users specify best practices that allow users to
  maximize standards utilitywww.rosettanet.org