Version 1.2 12-15-2007
Enablement through SOMA: Moving from Strategy to Implementation
Building a Statewide Emergency Services Information Exchange Network
Donald George, CEO PRISM Communication Systems, Inc.
National Emergency Management Summit: March 5, 2007
Version 1.2 22-15-2007
Why does Emergency Response need transformation?
Disasters
Emergency Response Challenges Today
-Fragmented infrastructure-Insufficient planning-Insufficient policy-Fragmented operational linkages
Version 1.2 32-15-2007
Emergency Response Challenges Today
Why does Emergency Response need transformation?
Diseases
-Fragmented infrastructure-Insufficient planning-Insufficient policy-Fragmented operational linkages
Version 1.2 42-15-2007
Why does Emergency Response need transformation?
Terrorism
Emergency Response Challenges Today
-Fragmented infrastructure-Insufficient planning-Insufficient policy-Fragmented operational linkages
Version 1.2 52-15-2007
• How can our healthcare system respond most effectively to a major health emergency that could overwhelm the system’s routine capacity and resources?
Emergency Response Challenges Today
Version 1.2 62-15-2007
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
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
• Integrated communication
• Decision support• Alerting systems• Surveillance• Countermeasures• Geospatial
services
Business Needs
How do we transform Emergency Response?
Version 1.2 72-15-2007
• Build an Integrated Health and Emergency Services Framework
• Transform the public health business model across multiple functional health and emergency systems
Connect the Information Systems
The business needs will be met by using the Service Oriented Modeling and Architecture (SOMA) to:
How do we transform Emergency Response?
Version 1.2 82-15-2007
Service-oriented Modeling and Architecture (SOMA)
CBM
Top-down: business-driven Process, event and
variation analysis
Bottom-up:Leverage Legacy thru
understanding and transformation
Business Services linkedTo Business Goals
Model driven developm
ent is key.
Specify IT Components, their services and flow
Legacy
Business Vision
Map components & Services to best technology,
Service-oriented Architecture
1
2
3 4 5
SOMA combines Business Vision with Modern and
Legacy assetsto achieve an enterprise
services architecture.
How do we transform Emergency Response?
Version 1.2 92-15-2007
Connect the Information Systems Integrated Business ServicesReusable, integrated services
Emergency Operations Center
Dispatch
Public Health
Federal Agency
First Responders
Process integrationProcess integration
How do we transform Emergency Response?
Version 1.2 102-15-2007
Connect the Information Systems Integrated Health FrameworkIntro to Health and Emergency Standards
SOA
HL7IEEE
NCPDPDICOM
ANSI ASC X12N
HL7ICD-9-CM
CPT-4SNOMED CT
LOINCNDC
DSM IV
CAPEDXLNIMSStandardized collaboration
processes help bring about interoperability.
How do we transform Emergency Response?
Version 1.2 112-15-2007
Public Health and PHIN Alignment
Public HealthLabs
Hospitals/HealthPlans
AmbulatoryCare
VaccinationCenters
CDC/Other Agencies
PharmaceuticalStockpile
AlertMessaging
Systems
HL7 V3Data model
HL7 CDA_RXData model
Public Health Information NetworkPublic Health Information Network
Preparedness & Emergency ResponsePreparedness & Emergency Response
• Standards-based communications
• Open Architecture
• Web services enabled
EmergencyManagement
Fire, RescueEMS Transportation
LawEnforcement
911
Federal,State, Local,Tribal Govt.
NGOsIndustry Utilities
Schools,Education
Public HealthDirectory
EPAD
Version 1.2 122-15-2007
Connect the Information Systems Integrated Health FrameworkIntro 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.
How do we transform Emergency Response?
Version 1.2 132-15-2007
Service Requirements
Service Design Service
Build
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 Oriented AnalysisHow do you understand the business as services?How do you enable business agility?
Service Oriented DesignWhat is the precise behavior of services?How do you ensure scalability, reliability, etc?How do you enable technical agility?
Service Oriented ProvisioningHow do you determine which Services to use?How do you choose Service Providers?
Service Oriented ProgrammingHow do you reduce effort to code Web Services?
Service Development
Intro to Service Oriented Architecture Modeling
How do we transform Emergency Response?
Version 1.2 142-15-2007
Atomic Service Composite Service Registry
Servicesatomic and composite
Operational Systems
Service Components
Consumers
Business ProcessComposition; choreography; business state machines
Service ProviderService C
onsumer
Integration (Enterprise Service Bus)
QoS Layer (Security, M
anagement &
Monitoring Infrastructure Services)
Data A
rchitecture (meta-data) &
Business Intelligence
Governance
First Responders
Health Workers
PackagedApplication
CustomApplication
OOApplication
Integrated Services ArchitectureSOMA Processes
How do we transform Emergency Response?
Version 1.2 152-15-2007
Roadmaps Enable Alignment
Version 1.2 162-15-2007
Connect the Information Systems Integrated Health FrameworkCase Study: Public Health Information Network
Ancillary Data& Services
Registries Data& Services
EHR Data& Services
DataWarehouse
OutbreakManagement
PHSReporting
SharedHealth Record
DrugInformation
DiagnosticImaging Laboratory Health
Information
POINT OF SERVICE
Hospital, LTC,CCC, EPR
PhysicianOffice EMR
BusinessRules
EHRIndex
MessageStructures
NormalizationRules
Security MgmtData Privacy Data Configuration
Physician/Provider
Physician/Provider
Lab System(LIS)
Lab Clinician
EMS Systems
Radiologist
PharmacySystem
Pharmacist
Public HealthServices
Public Health Provider
Longitudinal Record Services
HIAL Communication Bus
Common Services
ClientRegistry
ProviderRegistry
LocationRegistry
TerminologyRegistry
Get Client IDResolution
List Laboratory Orders Get Laboratory Result
List LaboratoryResults
Get Prescription
List Medications
Stream DI Image
List DI Results Get DI ReportGet OutbreakCase Data
List CD ReportEvents
Get ProviderInformation
List ServiceDelivery
Locations
List EncounterEvents
Get EncounterSummary
Get ClinicalDashboard
Get ClientDemographic
Health Services
How do we transform Emergency Response?
Version 1.2 172-15-2007
Major Components of PHIN
OIDManager<<subsystem>>
(from Common)
PatientDemographics<<subsystem>>
(from Common)
PatientEncounter<<subsystem>>
(from Countermeasure & Response) CaseReporting<<subsystem>>
(from Early Event Detection)
Jurisdiction<<subsystem>>
(from Early Event Detection)
Reporter<<subsystem>>
(from Early Event Detection)
EventIdentification<<subsystem>>
(from Early Event Detection)
EventSpreadDetermination<<subsystem>>
(from Early Event Detection)
SampleTracking<<subsystem>>
(from Connecting Laboratory Systems)
SpecimenTesting<<subsystem>>
(from Connecting Laboratory Systems)
ChainOfCustody<<subsystem>>
(from Connecting Laboratory Systems)
Accession
(from ChainOfC...)
Custody
(from SampleTracking)
CaseInvestigation<<subsystem>>
(from Outbreak Management)
ReporterDemographics
(from Reporter)
Survey
(from CaseInvestigation)
FollowUp<<subsystem>>
(from Common)
HealthEvent<<subsystem>>
(from Outbreak Management)
ExposureSource
(from HealthEvent)
TravelHistory
(from HealthEvent)
DirectAlert<<subsystem>>
(from Messaging)
AcknowledgeReceipt
(from DirectAlert)
CascadeAlert<<subsystem>>
(from Messaging)
Directory<<subsystem>>
(from Partner Communication)
Location
(from SampleTracking)
Tracking Details
(from SampleTracking)
Specimen
(from SpecimenTesting)
SpecimenCollection
(from CaseInvestigation)
InventoryManagement<<subsystem>>
(from Logistics)
TransportationManagement<<subsystem>>
(from Logistics)
GeoSpatial<<subsystem>>
(from Common)
area
(from GeoSpatial)
CascadeAlert
(from CascadeAlert)
PODManagement<<subsystem>>
(from Countermeasure & Response) SNSActivation<<subsystem>>
(from Countermeasure & Response)
Transfe Asset
(from InventoryManagement)
ReceiveAsset
(from InventoryManagement)
DeactivateAsset
(from InventoryManagement)
CounterMeasure<<subsystem>>
(from Countermeasure & Response)
CampaignManagement<<subsystem>>
(from Countermeasure & Response)
Patient_VitalStatistics
(from PatientDemographics)
HL7NCRNNotification
(from CaseReporting)
Consent
(from PatientEncounter)
Triage
(from PatientEncounter)
TrackAsset
(from InventoryManagement)
ProjectedSpread
(from EventSpreadDetermination)
SendAlert
(from DirectAlert)
FindHealthEvent(from EventIdentification)
FIPSJurisdiction
(from Jurisdiction)
PopulationGroup
(from CampaignManagement)
Apportionment
(from CampaignManagement)
Command & Control(from Strategic National Stockpile)
OrderAsset
(from InventoryManagement)
SNS Request
(from SNSActivation)
CampaignHistory
(from CampaignManagement)
CampaignManagement
(from CampaignManagement)
OrganizationUnit
(from CommandControl)
UnifiedCommand
(from CommandControl)
Notification
(from PODManagement)
Communication
(from CommandControl)
Strategic National Stockpile
(from External Systems)
VAERS
(from External Systems)
State C&C
(from External Systems)
LIMS
(from External Systems)
HIS (Hospital Information System)
(from External Systems)
RODS
(from External Systems)
EARS
(from External Systems)
Bio-Watch
(from External Systems)
National Broker
(from External Systems)
ProjectedSpread
(from EventSpreadDetermination)
ManageOID
(from OIDManager)
Subject
(from SpecimenTesting)
AdverseEvent
(from FollowUp)
FollowupManager
(from FollowUp)
Patient_ClinicalHistory
(from PatientDemographics) Patient_ID
(from PatientDemograph...
ManageOID
(from OIDManager)
Patient_Address
(from PatientDemographics)
HL7OutbreakNotification
(from CaseReporting)
CaseHistory
(from CaseInvestigation)
HealthEventManager
(from HealthEvent)
CaseIdentifier
(from CaseInvestigation)
Diagnosis
(from CaseInvestigation)
Patient
(from PatientEncounter)
ManageOID
(from OIDManager)
PODManagement
(from PODManagement)
Isolate
(from CounterMeasure)
Quarantine
(from CounterMeasure)
ResponseMonitoring
(from CounterMeasure)
Dispense
(from PatientEncounter)
Treatment
(from CounterMeasure)
Countermeasure
(from PatientEncounter)
SendAlert
(from DirectAlert)
location
(from GeoSpatial)
ManageOID
(from OIDManager)
EntityExposure
(from HealthEvent)
Address
(from Directory)
Resource
(from TransportationManagement)
Route
(from TransportationManagement)
Replenishment
(from TransportationManagement)
IssueAsset
(from InventoryManagement)
Transport Resource Managment
(from TransportationManagement)
Dispatch
(from TransportationManagement)
EnterpriseMessaging<<subsystem>>
(from Common)
subject id
WarehouseManagement<<subsystem>>
(from Logistics)
Early detection, alerting, and counter measures
Version 1.2 182-15-2007
Move from Strategy to Implementation PHIN and Emergency Services Model
Building an Emergency Services Information Exchange Network
USER
BUSINESS
Resource Virtualization Services
Utility Business Services
Business FunctionServices
Business Process Choreography Services
Common Services
User AccessServices
Service Level Automation and Orchestration Services
User Interaction Services
InformationManagement
Services
Component BusinessServices
Enterprise Service Bus
Choreography
Personalization
Reporting
Custom Applications
Packaged Applications
Adaptation
Business Rules
Interaction Acquired ServicesCollaboration
PresentationConnectivity
Information Access
Information Integration
Analytics
Metadata
… … … …… …
Business Connections
Mediation, Messaging, EventsBusiness
Performance Management
BusinessService
BusinessService
BusinessService
BusinessService
BillingRatingMetering Services Peering Settlement
Application Services
Infrastructure Services
Availability Services
Security Services
Workload Services
Configuration Services
Problem Management
Data Placement
Server Storage Resource MappingNetwork Information …
…
…
USER
BUSINESS
Resource Virtualization Services
Utility Business Services
Business FunctionServices
Business Process Choreography Services
Common Services
User AccessServices
Service Level Automation and Orchestration Services
User Interaction Services
InformationManagement
Services
Component BusinessServices
Enterprise Service Bus
Choreography
Personalization
Reporting
Custom Applications
Packaged Applications
Adaptation
Business Rules
Interaction Acquired ServicesCollaboration
PresentationConnectivity
Information Access
Information Integration
Analytics
Metadata
… … … …… …
Business Connections
Mediation, Messaging, EventsBusiness
Performance Management
BusinessService
BusinessService
BusinessService
BusinessService
BillingRatingMetering Services Peering Settlement
Application Services
Infrastructure Services
Availability Services
Security Services
Workload Services
Configuration Services
Problem Management
Data Placement
Server Storage Resource MappingNetwork Information …
…
…
Start with a “hot” component area –product identificationDefine a model (e.g. with WBI Modeler) of the component to be transformed
Identify and design the required supporting infrastructure
Understand the underlying applications infrastructure and how it needs to change
How do we transform Emergency Response?
Version 1.2 192-15-2007
Technology
Policy/PlanningProcedureAdministration
Services
Resources
Mission
Mod
e of
Del
iver
ySu
ppor
t Fun
ctio
nsR
esou
rce
Mgt
.
Supporting Applications
-Director, Deputy, CFO-Grants Development Division-Legal Services and Policy Division-Governmental Relations Division-PH Districts-Advisory Boards & Councils
Core: e-mail, network availability, IT maintenance, enterprise architecture & strategy
OIT will develop/align Service Reference Model (SRM),Data Reference Model (DRM), and
Technical Reference Model (TRM) for each line of business
Health CareServices
Consumer Health& Safety
ImmunizationManagement
IllnessPrevention
-Physicians’ Alert-Women, Infant,
Children services
-Web based interface toallow entry of environmentaldata (Environmental Health)
Georgia ImmunizationRegistry (GRITS)
Government Line of Business to Citizens (G2C): Health
PH Monitoring
Vital Records, VitalEvents, NSTS
-WIC Branch-Family Health Br.
-Bioterrorism/Emergency Rsp.
-Environmental Health andInjury Prevention Branch
-Prevention ServicesBranch
-Laboratory Br.-Epidemiology Br.-V. Records Br.
Family Health Br.
-Prevention ServicesBranch
-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.
Completing the Framework: Public Health Sample
Analysis Phase: Sample Result
Version 1.2 202-15-2007
Functional ArchitectureTier 3
Existing Systems
Tier 2
Service Control Functions Resource FunctionsPresentation Functions Persistence & Connectivity
Web / Gateways Server
Portal Server
Integration Server
Application Server
Directory Server
UDDI
RDBMS
GIS Server
Vocabulary Server
HTTP
SOAP
SMTP
V .XM
L
Web Services
SOAP
RM
I
Business Rules
IIOP
MQ
System Monitor
Choreography
Transformation
State Persistence
Message Service
Connection Management
Clinical Systems
Analysis & Visualization
Case Management System
Adaptor ToolKit
PHIN Portal Application
Custom Adaptors
Search
Transaction ManagerApplication Mgt
SSO
Multi-device
Multi-device
IVR
Fax
CICS
UNIX
Windows
IMS
DBMS
External Services
HTT
PSO
AP
Manage OIDLab Result
Track Sample
Lab Order
CAP Alert Patient
EncounterDiagnosis Complaint
Pharmacy Order
Adverse Event
Specimen
CMR Referral
CMR Follow Up
Investigation NEDSS
LOINC
SNOMED
Enterprise Application ServerSupply Chain Management
Service Utilities
Enterprise Resource PlanningBusiness Intelligence
Enterprise Asset ManagementDemand Planning
Exposure Treatment Reporter Info
GEO Mapping
Org OutbreakNotification
Substance Admin
Notifiable Condition
ValidateVocabulary
HL7
HL7 v2.xHL7 v3.0HL7 CDAPHINMS
NCPDPX12 NOtherCAP 1.0
Internal ServicesGHIN XML HL
7
WEB EOC
SAS
Incident Command System
Outbreak Management System
Countermeasure Response Environmental
Health Information System
App
licat
ion
Infra
stru
ctur
e
Tier 1
Devices
GIS
Version 1.2 212-15-2007
Wireless/Internet
VPN Network Intranet
Intranet/Internet
Multi Partner Complex:Bioterrorism Preparedness Supported by Appropriate Public Health Infrastructure
WirelessSecureGateway
VoiceGateway
EnterpriseServiceBus
LawEnforcement
Hospitals
EMSOffices
PublicHealthLabs
Fire/Rescue
SNS
Virtual Private
Network
FEMA
CDC
HomelandSecurity
PublicHealthOffices
IncidentManagement
CommandControlSystem
ENOC
PublicHealthOffices
Wireless/Radio
Network
MMRS
EMA
IMMUNIZATIONText-VoiceGateway
NEDSS
GIS
VITALRECORDS
Alert Communication
System
Authent.ReverseProxy
VAN
Governor
Firewall
SecureConnection
AuthenticationServices
EnterpriseDirectory
Version 1.2 222-15-2007
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
Version 1.2 232-15-2007
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
Version 1.2 242-15-2007
More Information
http://www.prismsolution.com
Donald GeorgeChief Executive Officer
PRISM Communications System, Inc.1701 Barrett Parkway - Marietta, Georgia 30061
Version 1.2 252-15-2007
Enablement through SOMA: Moving from Strategy to Implementation
Building a Statewide Emergency Services Information Exchange Network
Donald George, CEO PRISM Communications Systems, Inc.
National Emergency Management Summit: March 5, 2007