Building Enterprise Portals for knowledgebased, integrated, patientcentered Healthcare systems in IR - PowerPoint PPT Presentation

1 / 24
About This Presentation
Title:

Building Enterprise Portals for knowledgebased, integrated, patientcentered Healthcare systems in IR

Description:

Improving health care services quality. Share and reuse Health information ... Mental health systems. Private lab systems. Private radiology systems. Pharmacy systems ... – PowerPoint PPT presentation

Number of Views:52
Avg rating:3.0/5.0
Slides: 25
Provided by: Bab51
Category:

less

Transcript and Presenter's Notes

Title: Building Enterprise Portals for knowledgebased, integrated, patientcentered Healthcare systems in IR


1
(No Transcript)
2
Building Enterprise Portals for knowledge-based,
integrated, patient-centered Healthcare systems
in IRAN
3
Purpose
  • Present a framework of processes and portal
    technology that enable Health information
    Management and sharing
  • Proven incorporates lessons learned from portal
    systems
  • Explains key design requirements, solution
    options, and Measures of Effectiveness

4
Agenda
5
Who We Are
  • TAKFAB is Health Information Authority of I.R.I
  • TAKFAB has central role in
  • Defining National health IT vision and strategies
  • Defining IT portfolios and aligning national IT
    projects
  • Health Enterprise architecture

6
ICT
To Be
As Is
7
Processes Evolution
TAKFAB
Healthcare Systems Environment
Standards
Source FEA
8
Availability
Accessibility
Affordability
Effective Coverage
Acceptability
High Quality
9
vision
10
A Change in Approach
Hospital
Primary Care
Social Resources
Primary Care
11
Four Main Parts of Health care systems
12
e- Health
??Care
13
Expectations Needs
  • Improving health care services quality
  • Share and reuse Health information
  • Reduce information overload
  • Minimize operation and maintenance costs
  • Streamline business processes
  • Enterprise system interoperability
  • More effective and faster Health care services

14
Expectations Fall into Several Process Areas
Patient Support Services
Revenue Cycle Denials
Patient Care Services
?Care Coordination
Clinical Resource Utilization
15
Pharmacy/ Medication Safety
Physician Clinical Practice
Clinical Decision Support
Data Warehouse
Severity Adjustment
Report Writer
Physician Order Entry
Result Review
Order Sets
Medication Order entry
Out patient Prescription
eMar
Rules and Alert
Comparative Data Base Access
Outcomes Measurement
Resource Utilization
Provider Documentation
Task lists/ Workflow Tools
Pathways
Protocols
Formulary Management
Cost Management
Dosing Management
Provider Profiling
Credentialing
Patient Location/ Patient Lists
Ambulatory Practice Management
Rounding Tools
Patient History Problem lists
Bar Coding
Drug Interactions
Access to Drug Data Bases
Enterprise patient Access
Core Information Management Components
Admission/ Registration
Enterprise Scheduling
Eligibility Verification
User Interface/Portal
Departmental/ Support Services
Request for Authorization
Consumer Portal
Technical Dental Management
Data Aggregation and Reporting Tools
Clinical Data Repository
Research Repository
EMPI
Common Medical Vocabularies
Lab
Cardilogy
Radiology
Clinical Documentation
Decision Support Repository
Order Entry
Rules Engine
Standard CDM Master File
Pathology
Surgery
Emergency Department
I Q Vital Signs
Patient Assessment
Flow Sheets
Security Tools
Blood Bank
Integration Tools
Other Departmental Systems
Medical Imaging
Response Time
PDA Support
Task List
Kardex
Care Plans
Transition Planning
Non-MD Orders
Interfaces To Monitors
Health information Management
Care management
Clinical Specialty Documentation
Patient Education
Non-MD Evidence Based Documentation
Authorization
Initial Concurrent Review
Discharge Planning
Clinical Dental Management
Chart Management
Transcription Dictation
Coding Support
Supply Chain
Work Lists
Payer Communication Notes
Document Imaging
Workflow Tools
Electronic Signature
Pathways
Support for LOG
Patient Supply Charges
Tracking Reconciliation
Support For Product Standards
Release of Information
Abstracting
MRN Management And Merge
Social Services Supports
Post Acute Placement
Alerts
Disease Management
Inventory Management
Interface To ERP Systems
16
The Path to SUCCESS
Formal Standardization
RFPs, Reference Implementations
Learning Technology Vendors, Academic
Institutions, Governmental Org
Consortia, Research Projects
17
Team-Based Approach
Shared Objectives
Shared Responsibilities
User Groups
Shared Risk
18
Vision Integrated Takfab Concept
Train like we Develop Develop like we Train
Hospital systems
Community systems
Mental health systems
Private lab systems
Private radiology systems
Authorization Service
Authentication Service
Provider Service
Audit Service
Facility/ Location Service
Client Service
Consent Service
Org. Service
Clinical Event Service
Pharmacy systems
Secure network infrastructure
19
Authentication Service
EMPI/ Client Service
Provider Registry
Audit Service
Consent Service
Clinical Event Service
20
Building a Portal
21
The Information Environment
Content (local and remote)
Currently.
End-user needs to join services together manually
- as well as learning multiple user interfaces
Source University of BATH , www.ukoln.ac.uk
22
The Information Environment
The vision.
End-user is automatically presented with
relevant resources through relevant channels
Source University of BATH , www.ukoln.ac.uk
23
Thank you for your attention
24
Definition of a Portal Ours
  • Network accessible web-based IT systems that
  • provide a single point of access to multiple
  • systems and information resources.
  • Combine targeted links with dynamic and
  • personalized information analysis and retrieval.
  • Commonly include functions for posting news,
  • calendars, personnel directories, storing
  • documents, accessing other systems,
  • collaboration, and full-text search.
  • Differ from websites by their level of dynamic
  • information aggregation and presentation, and
  • integration to other web-enabled systems.

25
Semantic Web
  • The vision of the Semantic Web aims at creating a
    Web where information can be understood by
    machines as well as humans
  • The Semantic Web requires the emergence of a
    general purpose representation and markup
    language to convey information about machine
    accessible semantic
  • Taxonomies can be expressed as abbreviated
    Ontologies for the Semantic Web

26
Thank You For Attention
Write a Comment
User Comments (0)
About PowerShow.com