Transcript Services

National Emergency Management Summit: March 5, 2007
Building a Statewide Emergency Services
Information Exchange Network
Enablement through SOMA: Moving from Strategy to
Implementation
Donald George, CEO
2-15-2007
PRISM Communication Systems, Inc.
Version 1.2
1
Emergency Response Challenges Today
Why does Emergency Response need transformation?
-Fragmented infrastructure
-Insufficient planning
-Insufficient policy
-Fragmented operational linkages
Disasters
2-15-2007
Version 1.2
2
Emergency Response Challenges Today
Why does Emergency Response need transformation?
-Fragmented infrastructure
-Insufficient planning
-Insufficient policy
-Fragmented operational linkages
Diseases
2-15-2007
Version 1.2
3
Emergency Response Challenges Today
Why does Emergency Response need transformation?
-Fragmented infrastructure
-Insufficient planning
-Insufficient policy
-Fragmented operational linkages
Terrorism
2-15-2007
Version 1.2
4
Emergency Response Challenges Today
• How can our
healthcare system
respond most
effectively to a major
health emergency
that could overwhelm
the system’s routine
capacity and
resources?
2-15-2007
Version 1.2
5
How do we transform Emergency Response?
Why does Emergency Response need transformation?
Emergency Preparedness:
California's Administration of Federal Grants
for Homeland Security and Bioterrorism
Preparedness Is Hampered by Inefficiencies
and Ambiguity
California State Auditor/Bureau of State Audits
September 2006
2-15-2007
Version 1.2
Business Needs
• Integrated
communication
• Decision support
• Alerting systems
• Surveillance
• Countermeasures
• Geospatial
services
6
How do we transform Emergency Response?
Connect the Information Systems
The business needs will be met by using the Service Oriented
Modeling and Architecture (SOMA) to:
• Build an Integrated Health and Emergency
Services Framework
• Transform the public health business model
across multiple functional health and emergency
systems
2-15-2007
Version 1.2
7
How do we transform Emergency Response?
Service-oriented Modeling and Architecture (SOMA)
CBM
3
Top-down: business-driven
Process, event and
variation analysis
4
SOMA combines Business
Vision with Modern and
Legacy assets
to achieve an enterprise
services architecture.
5
Business Services linked Specify IT Components,
Map components &
their services and flow Services to best technology,
To Business Goals
2
Service-oriented Architecture
Model driven development is key.
1
Business Vision
Bottom-up:
Leverage Legacy thru
understanding and transformation
Legacy
2-15-2007
Version 1.2
8
How do we transform Emergency Response?
Connect the Information Systems
Integrated Business Services
Reusable, integrated services
Process integration
Emergency Operations Center
Dispatch
Public Health
First Responders
Federal Agency
2-15-2007
Version 1.2
9
How do we transform Emergency Response?
Integrated Health Framework
Connect the Information Systems
Intro to Health and Emergency Standards
HL7
IEEE
NCPDP
DICOM
ANSI ASC X12N
Standardized collaboration
processes help bring about
interoperability.
2-15-2007
SOA
HL7
ICD-9-CM
CPT-4
SNOMED CT
LOINC
NDC
DSM IV
CAP
EDXL
NIMS
Version 1.2
10
Public Health and PHIN Alignment
Public Health
Directory
HL7 V3
Data model
Public Health
Labs
Hospitals/Health
Plans
Ambulatory
Care
Vaccination
Centers
HL7 CDA_RX
Data model
CDC/
Other Agencies
Pharmaceutical
Stockpile
Alert
Messaging
Systems
• Standards-based
communications
Public Health Information Network
• Open
Architecture
Preparedness & Emergency Response
• Web services
enabled
Emergency
Management
2-15-2007
Fire, Rescue
EMS
Transportation
Law
Enforcement
911
EPAD
Version 1.2
Federal,
State, Local,
Tribal Govt.
NGOs
Industry
Utilities
Schools,
Education
11
How do we transform Emergency Response?
Integrated Health Framework
Connect the Information Systems
Intro to Service Oriented Architecture Modeling
• Business Decomposition
• Identification of Services
and Classification
• Subsystem Analysis
and Interface
• Software Service
Realization
Service-architecture modeling is a method for developing software components
as services using a service-oriented analysis and design process for modeling,
analyzing, designing, and producing an SOA alignment with the business
analysis. It allows development of an integrated business service model.
2-15-2007
Version 1.2
12
How do we transform Emergency Response?
Intro to Service Oriented Architecture Modeling
Service Oriented Analysis
How do you understand the business as
services?
How do you enable business agility?
Service
Design
Service
Requirements
Service Oriented Design
What is the precise behavior of services?
How do you ensure scalability, reliability, etc?
How do you enable technical agility?
The best practices of
service orientation
which is the process
and practices that
guide the delivery of a
SOA is in the early
stages of adoption for
many organizations
Service
Build
Service
Development
Service Oriented Provisioning
How do you determine which Services to
use?
How do you choose Service Providers?
Service Oriented Programming
How do you reduce effort to code Web
Services?
2-15-2007
Version 1.2
13
How do we transform Emergency Response?
SOMA Processes
Integrated Services Architecture
Services
atomic and composite
Service Provider
Service Components
Operational Systems
Atomic Service
2-15-2007
Packaged
Application
Custom
Application
OO
Application
Composite Service
Version 1.2
Governance
Composition; choreography;
business state machines
Data Architecture (meta-data) &
Business Intelligence
Business Process
QoS Layer (Security, Management &
Monitoring Infrastructure Services)
Health
Workers
Integration (Enterprise Service Bus)
Service Consumer
First
Responders
Consumers
Registry
14
Roadmaps Enable Alignment
2-15-2007
Version 1.2
15
How do we transform Emergency Response?
Integrated Health Framework
Connect the Information Systems
Case Study: Public Health
Information
Network
Health
Services
Ancillary Data
& Services
Registries Data
& Services
Client
Get Client ID
Registry
Resolution
Get Outbreak
Case PHS
Data
Outbreak
Management
List CD Report
Shared Events
Health Record
Reporting
Provider
Registry
Location
Registry
EHR Data
& Services
List Laboratory
Results
List Encounter
Events
Get Provider
Information
Business
Rules
EHR
Index
Terminology
List Service
Registry Delivery
List DI Results
Diagnostic
Imaging
Drug
Information
Message
Structures
Laboratory
Get DI Report
Health
Information
Stream DI Image
Normalization
Rules
List Laboratory
Orders Record Services
Longitudinal
Get Laboratory Result
List Medications
Locations
Get Encounter
Summary
HIAL
Data
Warehouse
Get Clinical
Dashboard
Security Mgmt
Data
Get Client
Demographic
Common Services
Privacy Data
Configuration
Get Prescription
Communication Bus
Public Health
Services
POINT OF SERVICE
2-15-2007
Public Health
Provider
Pharmacy
System
Pharmacist
EMS
Systems
Lab System
(LIS)
Radiologist
Lab Clinician
Version 1.2
Hospital, LTC,
CCC, EPR
Physician/
Provider
Physician
Office
EMR
Physician/
Provider
16
Major Components of PHIN
Early detection, alerting, and counter measures
Command & Control
State C&C
(from Strategic National Stockpile)
Strategic National Stockpile
(from External Systems)
(from External Systems)
UnifiedCommand
(from CommandControl)
Communication
<<subsystem>>
(from CommandControl)
OrganizationUnit
PODManagement
(from CommandControl)
<<subsystem>>
(from Countermeasure & Response)
<<subsystem>>
SNSActivation
CampaignManagement
SendAlert
(from Countermeasure & Response)
(from DirectAlert)
(from Countermeasure & Response)
Notification
CampaignManagement
PODManagement
(from CampaignManagement)
(from PODManagement)
SNS Request
ProjectedSpread
(from SNSActivation)
(from EventSpreadDetermination)
(from PODManagement)
<<subsystem>>
WarehouseManagement
CampaignHistory
(from Logistics)
Apportionment
(from CampaignManagement)
PopulationGroup
<<subsystem>>
(from CampaignManagement)
(from CampaignManagement)
PatientEncounter
<<subsystem>>
(from Countermeasure & Response)
CaseReporting
ManageOID
(from Early Event Detection)
National Broker
(from OIDManager)
(from External Systems)
Dispense
Countermeasure
HIS (Hospital Information System)
HL7OutbreakNotification
(from PatientEncounter)
(from PatientEncounter)
(from External Systems)
<<subsystem>>
(from CaseReporting)
<<subsystem>>
Consent
Triage
(from Outbreak Management)
Patient
HL7NCRNNotification
(from PatientEncounter)
(from CaseReporting)
(from Logistics)
HealthEvent
OrderAsset
(from Outbreak Management)
(from InventoryManagement)
Diagnosis
CaseIdentifier
HealthEventManager
(from CaseInvestigation)
(from CaseInvestigation)
(from HealthEvent)
(from PatientEncounter)
InventoryManagement
<<subsystem>>
CaseInvestigation
(from PatientEncounter)
TravelHistory
DeactivateAsset
(from HealthEvent)
(from InventoryManagement)
ReceiveAsset
(from InventoryManagement)
TrackAsset
<<subsystem>>
<<subsystem>>
CounterMeasure
(from InventoryManagement)
FollowUp
CaseHistory
(from Common)
(from CaseInvestigation)
(from Countermeasure & Response)
Survey
SpecimenCollection
EntityExposure
ExposureSource
(from HealthEvent)
(from HealthEvent)
(from CaseInvestigation)
Isolate
Treatment
(from CounterMeasure)
(from CounterMeasure)
VAERS
<<subsystem>>
(from FollowUp)
IssueAsset
(from InventoryManagement)
(from CaseInvestigation)
FollowupManager
Transfe Asset
AdverseEvent
(from InventoryManagement)
<<subsystem>>
(from FollowUp)
(from External Systems)
Directory
PatientDemographics
(from Partner Communication)
(from Common)
Quarantine
(from CounterMeasure)
ResponseMonitoring
Patient_VitalStatistics
(from CounterMeasure)
(from PatientDemographics)
<<subsystem>>
TransportationManagement
Patient_Address
ManageOID
(from PatientDemographics)
(from OIDManager)
<<subsystem>>
ManageOID
Address
(from OIDManager)
(from Directory)
(from Logistics)
SpecimenTesting
<<subsystem>>
subject id
(from Connecting Laboratory Systems)
Resource
EventSpreadDetermination
Patient_ClinicalHistory
(from Early Event Detection)
(from PatientDemographics)
(from PatientDemograph...
EARS
Dispatch
(from TransportationManagement)
Patient_ID
Subject
Specimen
(from SpecimenTesting)
(from SpecimenTesting)
ProjectedSpread
(from EventSpreadDetermination)
Route
Transport Resource Managment
(from TransportationManagement)
(from TransportationManagement)
(from External Systems)
<<subsystem>>
<<subsystem>>
OIDManager
<<subsystem>>
(from Common)
SampleTracking
DirectAlert
(from Messaging)
(from Connecting Laboratory Systems)
<<subsystem>>
Jurisdiction
<<subsystem>>
(from Early Event Detection)
EventIdentification
(from Early Event Detection)
ManageOID
<<subsystem>>
(from OIDManager)
Custody
Tracking Details
(from SampleTracking)
LIMS
FIPSJurisdiction
(from External Systems)
FindHealthEvent
(from Jurisdiction)
Location
AcknowledgeReceipt
SendAlert
GeoSpatial
(from DirectAlert)
(from DirectAlert)
(from Common)
(from SampleTracking)
(from SampleTracking)
(from EventIdentification)
<<subsystem>>
<<subsystem>>
Reporter
<<subsystem>>
(from Early Event Detection)
EnterpriseMessaging
ChainOfCustody
<<subsystem>>
(from Connecting Laboratory Systems)
CascadeAlert
(from Common)
Bio-Watch
RODS
(from External Systems)
(from External Systems)
location
area
(from GeoSpatial)
(from GeoSpatial)
(from Messaging)
Accession
ReporterDemographics
2-15-2007
Replenishment
(from TransportationManagement)
(from TransportationManagement)
CascadeAlert
(from ChainOfCustody)
...)
(from Reporter)
(from CascadeAlert)
Version 1.2
17
How do we transform Emergency Response?
Move from Strategy to Implementation
PHIN and Emergency Services Model
Building an Emergency Services Information Exchange Network
Application Services
U
S
E
R
Component
Business
Services
User Access
Services
Business
Service
Adaptation
User Interaction
Services
Business
Process Choreo
graphy Services
Common
Services
Business
Function
Services
Information
Management
Services
Reporting
Information
Integration
Information
Access
Interaction
Collaboration
Choreography
Packaged
Applications
Acquired Services
Connectivity
Presentation
Business Rules
Custom
Applications
Personalization
Analytics
Business
Service
…
…
…
…
…
Metadata
…
Mediation, Messaging, Events
 Start with a “hot” component area –
product identification
 Define a model (e.g. with WBI
Modeler) of the component to be
transformed
 Understand the underlying
applications infrastructure and how
it needs to change
B
U
S
I
N
E
S
S
Business
Performance
Management
Enterprise Service Bus
Business Connections
Business
Service
Metering
Services
Utility Business Services
Rating
Billing
Peering
Settlement
…
Service Level Automation and Orchestration Services
Problem
Management
Security
Services
Server
Storage
Business
Service
Workload
Services
Configuration
Services
Availability
Services
Data
Placement
…
Resource Virtualization Services
Network
Resource Mapping
Information
…
Infrastructure Services
 Identify and design the required
supporting infrastructure
2-15-2007
Version 1.2
18
Completing the Framework: Public Health Sample
Resource Mgt.
Support Functions
Mode of Delivery
Analysis Phase: Sample Result
Government Line of Business to Citizens (G2C): Health
Services
Supporting
Applications
Health Care
Services
-Physicians’ Alert
-Women, Infant,
Children services
Consumer Health
& Safety
-Web based interface to
allow entry of environmental
data (Environmental Health)
Immunization
Management
PH
Monitoring
Georgia Immunization
Registry (GRITS)
Vital Records, Vital
Events, NSTS
Illness
Prevention
OIT will develop/align Service Reference Model (SRM),
Data Reference Model (DRM), and
Technical Reference Model (TRM) for each line of business
Technology
Core: e-mail, network availability, IT maintenance, enterprise architecture & strategy
Resources
Policy/Planning
Procedure
Administration
Mission
-WIC Branch
-Family Health Br.
-Bioterrorism/
Emergency Rsp.
-Environmental Health and
Injury Prevention Branch
-Director, Deputy, CFO
-Grants Development Division
-Legal Services and Policy Division
-Governmental Relations Division
-PH Districts
-Advisory Boards & Councils
-Prevention Services
Branch
-Laboratory Br.
-Epidemiology Br.
-V. Records Br.
Family Health Br.
-Prevention Services
Branch
-Chronic Disease Prv.
& Health Promotin. Br.
-State Pharmacy
-Office of Nursing
-Office of Health Information & Policy
-IT Liaison
The Division of Public Health (DPH) is responsible for disease control and prevention, the reduction
of avoidable injury-related deaths and disabilities, and the promotion of healthy lifestyles.
2-15-2007
Version 1.2
19
Functional Architecture
Tier 2
Lab
Order
Pharmacy
Order
RMI
SOAP
GEO Mapping SNOMED
NEDSS
HL7
IIOP
MQ
SMTP
Clinical
Systems
Manage OID LOINC
Validate
Vocabulary
Reporter
Info
Adverse Substance CMR
Event
Admin
Referral
V.XML
NCPDP
X12 N
Other
CAP1.0
Existing Systems
Patient Diagnosis Investigation Complaint
Encounter
Exposure Treatment
Countermeasure
Response
HL7 v2.x
HL7 v3.0
HL7 CDA
PHINMS
Resource Functions
HTTP
External Services
Web Services
Track
Lab
Sample Result
CAP
Alert
Application
Persistence & Connectivity
HL7
WEB EOC
Service Control Functions
SOAP
Presentation Functions
HTTP
Devices
Tier 3
SOAP
Tier 1
Internal Services
Environmental
Health Information
System
GHIN XML
CMR
Follow Up
Outbreak Management System
Org
Notifiable
Condition
Case Management
System
Specimen Outbreak
Notification
GIS
Incident Command System
Web / Gateways
Server
Integration Server
Choreography
Multi-device
Transformation
Infrastructure
IVR
Multi-device
Message Service
Directory Server
Connection
Management
UDDI
Adaptor ToolKit
RDBMS
Custom Adaptors
Fax
CICS
UNIX
GIS Server
Vocabulary Server
Windows
IMS
DBMS
Portal Server
State Persistence
Application Server
Transaction
Manager
Application Mgt
Search
System Monitor
Business Rules
SAS
Analysis &
Visualization
PHIN Portal
Application
SSO
Enterprise Application Server
Enterprise Resource Planning
Business Intelligence
Demand Planning
Enterprise Asset Management
2-15-2007
Version 1.2
Supply Chain
Management
Service
Utilities
20
Homeland
Security
Governor
Wireless/
Radio
Network
EMA
Virtual
Private
Networ
k
ENOC
Authent.
Reverse
Proxy
Incident
Command
Alert
Management Control
Communication
System
System
FEMA
Law
Enforcement
MMRS
Hospitals
Secure
Connection
Wireless/
Internet
VPN
Network
VAN
Firewall
Wireless
Secure
Gateway
Enterprise
Service
Bus
Intrane
t
Public
Health
Labs
Authentication
Services
VITAL
RECORDS
NEDSS
Intrane
t/
Interne
t
Fire/
Rescue
SNS
CDC
Enterprise
Directory
Public
Health
Offices
GIS
Public
Health
Offices
Voice
Gateway
EMS
Offices
Text-Voice
Gateway
IMMUNIZATION
Multi Partner Complex:
Bioterrorism Preparedness Supported by Appropriate Public
Health Infrastructure
2-15-2007
Version 1.2
21
Benefits of Integrated Services
• Integrated services improve emergency
response and reduces costs
• Provides an integrated view across the
continuum of responses
• Creates an integrated process framework
that connects health and emergency
services to improve operational response
efficiency
• Builds common, reusable services
2-15-2007
Version 1.2
22
Summary
• Without an Enterprise Services Vision and
Roadmap for emergency response, today’s
response services will remain siloed
• An Enterprise Services Vision and Roadmap is
essential to move toward an SOA enabled
emergency preparedness
• Make SOA real by tackling cross-enterprise
processes
• Service oriented modeling is essential to
effective architecture design
2-15-2007
Version 1.2
23
More Information
http://www.prismsolution.com
Donald George
Chief Executive Officer
PRISM Communications System, Inc.
1701 Barrett Parkway - Marietta, Georgia 30061
[email protected]
2-15-2007
Version 1.2
24
National Emergency Management Summit: March 5, 2007
Building a Statewide Emergency Services
Information Exchange Network
Enablement through SOMA: Moving from Strategy to
Implementation
Donald George, CEO
2-15-2007
PRISM Communications Systems, Inc.
Version 1.2
25