Cancer Biomedical Informatics Grid Adverse Event Reporting System (caAERS)

1
Cancer Biomedical Informatics GridAdverse Event
Reporting System(caAERS)
                                                              

• City of Hope
• Duarte, California
• January 2006

2
caAERS Model Driven Development
Requirements Gathering and Validation Use case
models, activity models, and domain analysis
models are used to document and validate system
requirements.
BRIDG Model Harmonization Activity models, domain
analysis models, and database design models are
used to inform the BRIDG of caAERS static
information structures and dynamic behaviors.
HL7 Message Development Domain analysis models
and message development models are used to inform
HL7 information and interaction models and
message specifications.
caAERS Application Construction Database design
models, message development models, and activity
models are used to generate caAERS modules using
the caBIG System Development Kit.
3
Interrelated Modeling Activities
4
Interrelated Modeling Activities
5
caAERS Models
Domain analysis models Domain analysis models
provide documentation of the caAERS information
and data requirements.
Use case and activity models Use case and
activity models provide documentation of the
caAERS business process and application
behavioral requirements.
Database design models Database design models
provide documentation of the conceptual, logical,
and physical design of database structures
required to persist caAERS data.
Message design models Message design models
provide documentation of the information content
and structure of data passed as caAERS inbound
and outbound messages.
6
Interrelated caAERS Models
7
Purpose Driven caAERS Models
8
Use Case Model
9
Activity Model
10
State Machine Diagram
11
Interaction Model
12
Domain Analysis Models

• Conceptual DAM (CDAM)
• A class diagram of caAERS data requirements as
  depicted in the caAERS use case and activity
  models.
• Abstract DAM (ADAM)
• A subset of the HL7 Reference Information Model
  (RIM) determined by mapping the caAERS CDAM to
  the HL7 RIM.
• Logical DAM (LDAM)
• A RIM-derived class diagram of the caAERS data
  requirements derived from the caAERS CDAM and
  ADAM.

Conceptual Domain Analysis Model
Abstract Domain Analysis Model
Logical Domain Analysis Model
13
Conceptual Domain Analysis Model (CDAM)
14
Abstract Domain Analysis Model (ADAM)
15
Logical Domain Analysis Model (LDAM)
16
Domain Analysis Modeling Process
17

• caAERS RMIM (Refined Message Information Model)
• An HL7 RMIM based upon the caAERS Logical Domain
  Analysis Model.
• caAERS HMD (Hierarchical Message Definition)
• A serialized version of an HL7 RMIM or a EA
  class diagram of a caAERS message.
• caAERS XSD (XML Schema Definition)
• An XML schema specification of a caAERS message
  as generated by the HL7 or EA XML schema
  generator.

18
caAERS Refined Message Information Model (RMIM)
19
caAERS Refined Message Information Model (RMIM)
20
caAERS Hierarchical Message Definition (HMD)
21
caAERS Hierarchical Message Definition (HMD)
22
Enterprise Architect XML Schema Design Model
23
Generated Enterprise Architect XML Schema
Definition (XSD)
24
Database Design Models

• Conceptual Data Model (CDM)
• A class diagram of caAERS data requirements as
  depicted in the caAERS LDAM using SDK modeling
  rules
• Logical Data Model (LDM)
• An elaboration of the caAERS CDM used to expose
  significant caAERS semantic concepts.
• Physical Data Model (PDM)
• A transformation of the caAERS LDM class diagram
  into a set of database tables, columns, and
  primary/foreign keys.

Conceptual Data Model
Logical Data Model
Physical Data Model
25
Conceptual Data Model (CDM)
26
Logical Data Model (LDM)
27
Physical Data Model (PDM)
28
Database Definition Language (DDL)
CREATE TABLE StudySubject ( id INTEGER NOT
NULL, namePrefix VARCHAR(50), firstName
VARCHAR(50) NOT NULL, middleName
VARCHAR(50), lastName VARCHAR(50) NOT
NULL, nameSuffix VARCHAR(50), occupationTable
VARCHAR(50) DEFAULT Person.occupation, occupation
Code VARCHAR(10), emailAddress
VARCHAR(50), birthDate DATETIME, genderTable
VARCHAR(50) DEFAULT StudySubject.gender, genderCo
de VARCHAR(10), raceTable VARCHAR(50) DEFAULT
StudySubject.race, raceCode VARCHAR(10), ethnicG
roupTable VARCHAR(50) DEFAULT StudySubject.ethnicG
roup, ethnicGroupCode VARCHAR(10), deceaseDate
DATETIME, PRIMARY KEY (id), KEY
(ethnicGroupTable, ethnicGroupCode), KEY
(id), KEY (genderTable, genderCode), KEY
(occupationTable, occupationCode), KEY
(raceTable, raceCode) )
29
Information and Data Model Interrelationships
30
caAERS Models Driven Development

• Use Case Model
• Activity Model
• Interaction Model

• Conceptual DAM
• Abstract DAM
• Logical DAM

• caAERS RMIM
• caAERS HMD
• caAERS XSD

• Conceptual DM
• Logical DM
• Physical DM

31
Enterprise Architect Model Packages
32
Questions / Discussion / Feedback
33
Thank You

• Abdul-Malik Shakir
• Principal Consultant
• Shakir Consulting
• 1911 Foothill Blvd., Suite 148
• La Verne, CA 91750
• Office [phone] ? Mobile [phone]
• Email AbdulMalik_at_ShakirConsulting.com