Get documents about "PowerPoint Presentation - IDI - NTNU
Document Sample
Health Informatics, NTNU, October 13 2005
HealthCare and Architecture:
a model-based approach
Ståle Walderhaug
SINTEF ICT
stale.walderhaug@sintef.no
Telecom and Informatics
1
Health Informatics, NTNU, October 13 2005
MAFIIA
Model-based Architecture description
Framework for Information Integration
Abstraction
Telecom and Informatics
2
Health Informatics, NTNU, October 13 2005
MAFIIA Overview
Handbook of generic Handbooks with Architectural
architectural domain specific description of
description additions to concrete
framework framework applications
MAFIIA/H
Healthcare Healthcare
specialisation App <…>
MAFIIA Handbook architecture
Refined Used to
Generic part in MAFIIA/D create
Defence Defence
specialisation App <…>
IIS specialisation
architecture
…
MAFIIA/<.>
<Domain> <Domain>
specialisation App <…>
architecture
Telecom and Informatics
3
Health Informatics, NTNU, October 13 2005
MAFIIA Background
Partly
MACCIS
Guide reused in
Part A
MAFIAA
Handbook
MACCIS Additional Generic part
Specification minor input
Part B
IEEE 1471 Terminology MAFIAA
used in Handbook
IIS specialisation
IIS
Literature Background
for creating
Telecom and Informatics
4
Health Informatics, NTNU, October 13 2005
MAFIIA
System
assets....
Concerns
System assets
Dictionary
Patterns
Standards
Reference architecture
Viewpoints
Process
Concerns....
Telecom and Informatics
5
Health Informatics, NTNU, October 13 2005
S ystem
Has an
Architecture
Has
Role S takeholder
* *
1..* Is important to
Described by
1
Has Reference Architecture
* Is based on
1..*
Concern Architectural Description (AD)
Identifies
1 Selected formalism
Organised by
1..* Selects
*
Conforms to
Viewpoint View
Modelling Language
1
Participates in
MAFIIA 1..*
Expressed using
Consists of
Concepts Model
Participates in Participates in
1 1
(based on Consists of
*
*
Consists of
Textual Description Diagram
IEEE 1471)
Telecom and Informatics
6
Health Informatics, NTNU, October 13 2005
Stakeholder
An individual, team, or organization (or classes thereof) with
interests in, or concerns relative to, a system. (MAFIIA)
A stakeholder was originally a person who holds money or other property while its
owner is being determined. The situation often arises when two persons bet on the
outcome of a future event and have a third person act as the stakeholder, holding
the money (or "stake[s]") they have both wagered (or "staked") until the event
occurs. Courts sometimes act as stakeholders, holding property while litigation
between the possible owners resolves the issue of which one is entitled to the
property, and trustees often act as stakeholders, holding property until beneficiaries
come of age, for example. An "escrow agent" is one kind of trustee who is a
stakeholder, usually in a situation where part of the purchase price of property is
being held until some condition is satisfied. It is a very old concept in the law.
(WIKIPEDIA)
In the last decades of the 20th century, the word "stakeholder" has evolved to
mean a person or organisation that has a legitimate interest in a project or entity. In
discussing the decision-making process for institutions -- including large business
corporations, government agencies and non-profit organizations -- the concept has
been broadened to include everyone with an interest (or "stake") in what the entity
does. (WIKIPEDIA)
Telecom and Informatics
7
Health Informatics, NTNU, October 13 2005
Task No. 1
a) For a Health Information System (HIS) to be used by
doctors inside a hospital, who/what do you think are the 3
most important/active/responsible stakeholders?
b) For a Mobile HIS to be used by paramedics, nurses and
doctors inside AND OUTSIDE of the hospital
environment, who/what do you think are the 3 most
important/active/responsible stakeholders?
5-6 minutes discussion in pairs or equivalent
configurations
Telecom and Informatics
8
Health Informatics, NTNU, October 13 2005
Concerns
Application Specific Functionality Concerns
Default in models for all views
Quality Related Functionality Concerns
Relevant concerns selected for target system and described as
separate models in relevant views
E.g. Communication, concurrency, configurability, distribution
transparency etc.
Specific IIS concerns:
Security
Telecom and Informatics
9
Health Informatics, NTNU, October 13 2005
Task No. 2
a) For a Health Information System (HIS) to be used by
doctors inside a hospital, who/what do you think are the 3
most important concerns?
b) For a Mobile HIS to be used by paramedics, nurses and
doctors inside AND OUTSIDE of the hospital
environment, who/what do you think are the 3 most
important concerns?
5-6 minutes discussion in pairs or equivalent
configurations
Telecom and Informatics
10
Health Informatics, NTNU, October 13 2005
Software and Architectural Patterns
“A pattern for software architecture describes a particular recurring
design problem that arises in specific design contexts, and presents a
well-proven generic scheme for its solution. The solution scheme is
specified by describing its constituent components, their
responsibilities and relationships, and the ways in which they
collaborate”
“An architectural pattern expresses a fundamental structural
organization schema for software systems. It provides a set of
predefined subsystems, specifies their responsibilities, and includes
rules and guidelines for organizing the relationships between them”
[Pattern-oriented software architecture, vol 1: Buschmann]
Telecom and Informatics
11
Health Informatics, NTNU, October 13 2005
Asset: Applicable Patterns
Adapter Forwarder-Receiver
Blackboard Reflection
Flyweight Master-Slave
Client-Server-Dispatcher Pipes and filters
Composite Proxy
Façade Publisher-Subscriber
Wrapper Façade
Telecom and Informatics
12
Health Informatics, NTNU, October 13 2005
Example pattern: Wrapper Facade
: Client : Wrapper : API Function : API Function
Facade A B
method 1( )
functionA( )
functionB( )
Telecom and Informatics
13
Health Informatics, NTNU, October 13 2005
Reference architecture, definition
A high-level, generic architecture which is
uses as the basis for development of
concrete system architectures, and to
compare architectures of existing systems
to each other.
Telecom and Informatics
14
Health Informatics, NTNU, October 13 2005
Reference architecture
Target System
Other parts of
User Interface (UI) Env. environment
inter-
facing
User Service (US) (EI) Legacy System 1
(LS1)
Business Service (BS) Legacy System 2
(LS2)
Resource Service (RS)
Interfaces
to system Legacy System n
environment (LSn)
Telecom and Informatics
15
Health Informatics, NTNU, October 13 2005
Typical IIS architecture
Query
“A mediator is a software
module that exploits encoded
knowledge about some sets or Mediator
subsets of data to create
information for a higher layer of
abstraction” [Wiederhold 92]
Mediator
Wrapper (Translator): converts
the underlying data objects from
the source to a common
information model Wrapper Wrapper
Source Source
Telecom and Informatics
16
Health Informatics, NTNU, October 13 2005
IIS - Reference architecture, mapping
User Environment Environment
Interface Client UI
Interfacing
User Client Tool
Service
Mediator
Business Wrapper Legacy
Mediator Façade
Service System
Adapter
Adapter
Resource
Service
Source Source
Telecom and Informatics
17
Health Informatics, NTNU, October 13 2005
Viewpoints
Viewpoint MAFIIA Viewpoints
a way of looking at a system Context
View Requirements
what you see when looking Component
from the chosen viewpoint. Distribution
Realisation
Telecom and Informatics
18
Health Informatics, NTNU, October 13 2005
Viewpoints
Context Viewpoint Requirements Viewpoint Component Viewpoint Distribution Viewpoint Realisation Viewpoint
<<create>> <<create>> <<create>> <<create>> <<create>>
Context view Requirements view Component view Distribution view Realisation View
1
1 1
1
1
1 1
1 1
1
Architectural Description (AD)
Telecom and Informatics
19
Health Informatics, NTNU, October 13 2005
Context viewpoint
Describe the environments to the target system in terms of
its business-related aspects, other involved technical
systems and the mapping of business aspects to the
target system.
Models
Business Aspects
Environment Systems
Business to System Mapping
Telecom and Informatics
20
Health Informatics, NTNU, October 13 2005
Case: FieldCare, Business Aspects Model
FieldCare Architecture
Transport Units
Emergency Rescue Team
Transport patient to hospital
Provide medical treatment at site of accident
Emergency situation
Treat patients in hospital Coordinate site of accident
Hospital Personnel (ECU)
Police
Telecom and Informatics
21
Health Informatics, NTNU, October 13 2005
Requirements viewpoint
Identify documentation of, or specify requirements related
to any concerns to the target system. Requirements shall
be testable and shall be used to verify that the target
system is able to perform its intended tasks.
Models:
Requirement
Target System Interface
Telecom and Informatics
22
Health Informatics, NTNU, October 13 2005
Case: FieldCare, Target System Interface
model
FieldCare Architecture
Emergency Care work Set up Network
<<extend>>
<<include>>
<<include>>
<<extend>> <<extend>>
Docment Treatment
<<extend>>
Forward medical information Coordinate medical work
<<extend>>
Replicate M edical Information Locally
<<extend>>
M edic
Update PIC
Give Treatment
M edical Coordinator
Owns PIC
Receives Treatment
Patient
Telecom and Informatics
23
Health Informatics, NTNU, October 13 2005
Component viewpoint
Describe the system in terms of its subsystems and
information objects, and document how subsystem
interaction and information processing is carried out in
order to provide the desired behavioural effect
Models:
System Information
System Decomposition
System Collaboration
Component and Interface Specification
Telecom and Informatics
24
Health Informatics, NTNU, October 13 2005
Case FieldCare: System information
model
Patient Data
Treatment : undefined
*
Is stored with
*
Treatment
PatientID : undefined
M edicID : undefined
Timestamp : undefined MedicalProcedure
Value : undefined
Is output from procedure Input : undefined
* Output : undefined
Is related to
Medic Data
M edicID : string
Roles : undefined
Name : string
Telecom and Informatics
25
Health Informatics, NTNU, October 13 2005
Case FieldCare: Decomposition model
GUI
M edical Engine M edical Procedure Defs
Session
FC Controller
Network
Replication Agent
PIC Adapter
Database
Telecom and Informatics
26
Health Informatics, NTNU, October 13 2005
Case FieldCare: Collaboration model I
DataFlow
M DA1
CM DA
DataFlow
DataFlow DataFlow
DataFlow
DataFlow
M DAn
Telecom and Informatics
27
Health Informatics, NTNU, October 13 2005
Case FieldCare: Collaboration model
II
Environment: Network: PIC Adapter: FC Controller: Replication Agent: Database: GUI: User 1:
Attach PIC
PIC Detected
Store Patient
Show Patient Details
Display
New Data Stored
Send data to all devices
Send data to all devices
Data
Telecom and Informatics
28
Health Informatics, NTNU, October 13 2005
Distribution viewpoint
Shall describe the logical distribution of system
components and document which components that must
be separated and which that cannot.
Models:
System Distribution
Role Distribution
Telecom and Informatics
29
Health Informatics, NTNU, October 13 2005
Case FieldCare: System distribution
model
FieldCare Unit
M edic PIC
GUI Can connect to
M edic Info
PIC Interface Medic Data
Session
Replication Agent
FC Controller
M edical Engine Database
Patient PIC
MedicalProcedure Treatment
PIC Interface
PIC Adapter
Can connect to Patient EPJ
M edical Procedure Defs
Patient Data
Network
Telecom and Informatics
30
Health Informatics, NTNU, October 13 2005
Realisation viewpoint
Shall describe the realisation of the target system in terms
of its subsystems The view will describe how to structure
subsystems. The view will describe how to structure
implementation and deployment the target system.
Models:
System Deployment
Technology Mapping
System Integration Test
Telecom and Informatics
31
Health Informatics, NTNU, October 13 2005
Case FieldCare: System deployment model
M DA1:
CM DA:
:GUI:
:GUI:
:Replication Agent:
:Session:
:Replication Agent: :Session:
:Database:
:FC Controller:
:Database:
:FC Controller:
:M edical Engine:
:PIC Adapter: :PIC Adapter:
:M edical Engine:
:M edical Prodedure Defs:
:Network:
:Network: :M edical Procedure Defs:
M edic PIC 3210:
Patient PIC 0123:
:PIC Interface:
:PIC Interface:
:M edica Data: :Patient Data:
Telecom and Informatics
32
Health Informatics, NTNU, October 13 2005
Process
Phases
Process activities Organisation along time
Inception
Inception Elaboration
Elaboration Construction
Construction Transition
Transition
Business analysis
Architectural design
Detailed design
Implementation
Test
Supporting activities
Project management
Work product management
preliminary iter. iter. iter. iter. iter
. iter. iter.
Iterations: iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
#m+1
Demonstrator
Demonstrator
Iteration Launch
Iteration Launch
Acceptance
Product Commit
Beta Test Launch
Iteration Launch
Demo / Delivery
Prototype
Meeting
Technical Audit
Concept Review
Review milestones:
Telecom and Informatics
33
Health Informatics, NTNU, October 13 2005
Process, viewpoints
Phases
View development Organisation along time
process Inception Elaboration Construction Transition
Inception Elaboration Construction Transition
Context view
Requirements view
Component view
Distribution view
Realisation view
preliminary iter. iter.
iter. iter. iter. .
iter iter. iter.
Iterations: iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
#m+1
Acceptance
meeting
Elaboration
Inception
review
review
Construction
review
Review milestones:
Telecom and Informatics
34
