Embed Size (px)
Citation preview
HL7 UK 2003 (c) Abies Ltd
Modelling Clinical Information Using UML
Tim BensonAbies Ltd
HL7 UK 2003 (c) Abies Ltd
Overview
Show how UML class diagrams add value to the HL7 v3 development process
Focus is on detailed Requirements specification and data element definitions (Glossary)
HL7 UK 2003 (c) Abies Ltd
The Problem HL7 v3 is a foreign language to clinicians HL7 RMIMs are specialised tools for developing
healthcare message XML schemas Not suited for capturing requirements
Formal class names based on structural attributes Small number of common attribute names based on
the RIM Pre-defined Data Types and Vocabulary
HL7 UK 2003 (c) Abies Ltd
The Solution
Specify message requirements in detail using: Visual data modelling (UML class diagrams) Glossary - detailed definition of every data
item in context Then map to HL7 RMIM
HL7 UK 2003 (c) Abies Ltd
Iterative Development HL7 is concerned
with the whole process - not just drafting documents
HL7 UK 2003 (c) Abies Ltd
Phases
HL7 UK 2003 (c) Abies Ltd
HL7 Message Development Framework (MDF) 1999
Example
Restrict
Restrict
Restrict
RIM
D-MIM
R-MIM
HMD
MessageType
Storyboard
StoryboardExample
ApplicationRole
TriggerEvent
Interaction
Instantiate
Sender Receiver
Triggers
Content
References
HL7 UK 2003 (c) Abies Ltd
What is a model?
Two sorts of model: To describe the real world
• Can never be “right” To design and build things
• Specification
Always a simplification
HL7 UK 2003 (c) Abies Ltd
Models and Diagrams
Model is all information in a project Model may include Glossary Model is much more than a collection of
diagrams Each diagram is just one view on a Model Most models contain dozens of diagrams
HL7 UK 2003 (c) Abies Ltd
Real World Models
Enterprisemodel
Abstractmodel
Situationmodel
Scope
Abstraction
HL7 UK 2003 (c) Abies Ltd
Specification Models
Logicalmodel
Referencemodel
Implementationmodel
Scope
Abstraction
HL7 UK 2003 (c) Abies Ltd
OMG MOF (meta object facility)
M3 meta-metamodel M2 meta-model, meta-metadata
(languages) M1 model, meta-data (standards) M0 data (systems)
HL7 UK 2003 (c) Abies Ltd
MatrixBase
standards
(M3)UML XML
HL7 architecture
(M2)Vocabulary RIM DataTypes
Specification
(M1)
Requirement
Specification
RMIM
HMDXML
SchemaTesting
Use (M0) Operation
HL7 UK 2003 (c) Abies Ltd
UML
Unified Modelling Language Mandated in e-GIF OMG standard UML 1.1 1997 Version 1.4 2000 UML 2.0 2003 MDA Model Driven Architecture XMI (XML Metadata Interchange)
HL7 UK 2003 (c) Abies Ltd
UML Diagrams
12 Diagram Types Class diagram Activity diagram
Sequence diagram State-chart diagram Use case diagram
HL7 UK 2003 (c) Abies Ltd
UML Notation
Classes and Attributes Association (Composition and
Aggregation) Specialisation Multiplicities (optionality)
HL7 UK 2003 (c) Abies Ltd
Composition
Composition
Statement
includes
1..*1..*
includes
HL7 UK 2003 (c) Abies Ltd
Aggregation
Composition
Statement
includes
1..*1..*
includes
Folder
0..*0..*
HL7 UK 2003 (c) Abies Ltd
Specialisation
Composition
Statement
includes
1..*1..*
includes
Folder
0..*0..*
Document
EncounterRecord
HL7 UK 2003 (c) Abies Ltd
Navigation
SubjectOfCare
HealthCareParty
Compositionconcerns
created bycreated by
concerns
HL7 UK 2003 (c) Abies Ltd
Healthcare Party
HealthCareParty
HealthCareProfessionalHealthCareOrganisationComputerSystem
Person
HL7 UK 2003 (c) Abies Ltd
Attributes
HealthCareParty
HealthCareProfessional
+registrationID
+hcpType
HealthCareOrganisation
+organisationName
+organisationID
+organisationType
ComputerSystem
Person
+personName
HL7 UK 2003 (c) Abies Ltd
Patients and Healthcare Parties
HealthCareParty
HealthCareProfessionalHealthCareOrganisation atComputerSystem
Person
Party
Address
ElectronicAddress has0..*
has
0..*
SubjectOfCare
Patient
is
1..*
under care of
RelatedPerson
has
0..*
has
0..*
is
1..*
0..*
has
0..*has
atunder care of
HL7 UK 2003 (c) Abies Ltd
Healthcare Document Structure
HealthCareDocument
Composition
CopyDestination
may have
0..*
SubjectOfCareconcerns
Addressee
Author
written by
Patientis
1..*
Person
HealthCareParty
HealthCareProfessional
HealthCareOrganisation
at
ComputerSystem
Statement
includes
1..*
written by
concerns1..*
is
1..*
includes
0..*
may have at
HL7 UK 2003 (c) Abies Ltd
Clinical Information ComplexesComposition
ClinicalInfoItem
Statement
includes
1..*
ClinicalInfoComplex
contains
1..*
may have
0..*
1..*
contains may have
0..*
includes
1..*
HL7 UK 2003 (c) Abies Ltd
Headings and Problem Lists
Composition
Statement
includes
1..*
HealthTopic
is label for
0..*
includes
1..*0..*
is label for
HL7 UK 2003 (c) Abies Ltd
Clinical Statements
Composition
ClinicalInfoItem
Statement
includes
1..*
ClinicalInfoComplex
contains
1..*
1
may have
0..*
HealthTopicis label for
0..*
includes
1..*
may have
0..*
is label for
0..*1
1..*
contains
HL7 UK 2003 (c) Abies Ltd
Clinical Information ItemsClinicalInfoItem
Observation MedicationItemRequestItem
Procedure
PlanItem
AnalysableObject
refers torefers to
Specimen StudyProduct
refers torefers to
AdminItem
HL7 UK 2003 (c) Abies Ltd
Conclusions
Health Information is complex, but not impossibly complex
This paper has illustrated a few high level patterns
UML and XML provide complementary sets of tools
