Transcript Model Automated eXchange (MAX)

Model Automated eXchange
(MAX)
System requirements
HL7 Plenary
September 13 2011
Project Driver
• Many HL7 Work Groups use a UML modeling tool
to produce Domain Analysis Models and Detailed
Clinical Models. There is a common need of the
Work Groups to import data into and export data
from the model tool repository. Enabling model
content import/export capabilities would
enhance the productivity of the modellers. The
intent of this project is to provide the maximum
capability, flexibility and extensibility of all the
options for model data access.
User needs
•
•
•
•
•
Not vendor dependent
Share workload
Roundtrip data
Remove cut and paste
Share data with public resources
– caDSR
• Traceability
Functional scope
Legend
MAX Core
Phase 1
Phase 2
VISIO interface
Translate to MAX
profile
Write to modeling tool
«include»
«include»
EA interface
Modeling tool
interface
Translate from MAX
profile
Read from modeling
tool
«include»
Write to transport
format
«include»
CSV interface
Transport format
interface
Database interface
«include»
«include»
«include»
Rational interface
«include»
«include»
Transform format
«include»
Write to database
«include»
Read from transport
format
XML interface
MIF interface
Read from database
caDSR interface
MAX core
• In order to transfer data
from one system to
another, the data must
be placed into a single
standard data format.
This format should
contain a set of UML
attributes as well as the
ability to add custom
attributes.
Translate from MAX
profile
Translate to MAX
profile
«include»
«include»
Transform format
Modeling tool interface
Read from modeling
tool
«include»
Write to modeling tool
«include»
Modeling tool
interface
EA interface
Rational interface
VISIO interface
• Each modeling tool that
will interface with MAX
will need to have a
mechanism to handle the
input and output of data
for that system. The
modeling tool interface
will be responsible for
translating the
information between the
vender proprietary
format and the MAX
profile.
Transport format interface
• MAX will be able to output
data to multiple transport
formats (CSV, XML,
delimited text), Each
transport format that is
identified to interface with
MAX will need to have a
mechanism to handle the
input and output of data for
that format. The modeling
tool interface will be
responsible for translating
the information between
the transport format and
the MAX profile.
Write to transport
format
Read from transport
format
«include»
«include»
Transport format
interface
XML interface
MIF interface
CSV interface
Database interface
Write to database
«include»
Read from database
«include»
Database interface
caDSR interface
• Each database that MAX
will interface with will
need to have a
mechanism to handle the
input and output of data
for that database. The
database interface will be
responsible for translating
the information between
the database format and
the MAX profile.
Process flow
• Declare desired subset - The user
will identify the set of model
attributes that they are
interested in as well as the
desired format for the end result.
• Export model - The entire model
content will be exposed in a
manner that is accessible to MAX.
• Extract desired subset for export MAX will filter out the model
attributes that were identified by
the user.
• Format elements to user desired
format - The model elements will
be formatted in the manner
requested by the user.
User
MAX
Modeling Tool
ActivityInitial
Declare desired subset
Export model
Model export
Desired subset
declaration
Extract desired subset for
export
Eported elements
«datastore»
Exported elements
Format element to user
desired format
ActivityFinal
«datastore»
Model data
Next steps
• October
– Share MAX documentation and solicit feedback
• November call
– Define MAX profile
• December call
– Share MAX profile with user community
• January WGM
– Approve MAX profile
Aknowledgements
•
•
•
•
•
Norman Daoust
Dianne Reeves
Baris Suzek
Anita Walden (for CIC)
Denise Warzel
http://wiki.hl7.org/index.php?title=MAX_-_Model_Automated_eXchange