1 / 12

Model Automated eXchange (MAX)

Model Automated eXchange (MAX). System requirements HL7 Plenary September 13 2011. Project Driver.

karenhamilton
Download Presentation

Model Automated eXchange (MAX)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Model Automated eXchange(MAX) System requirements HL7 Plenary September 13 2011

  2. 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.

  3. User needs • Not vendor dependent • Share workload • Roundtrip data • Remove cut and paste • Share data with public resources • caDSR • Traceability

  4. Functional scope

  5. 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.

  6. Modeling tool 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.

  7. 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.

  8. Database 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.

  9. 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.

  10. 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

  11. Aknowledgements • Norman Daoust • Dianne Reeves • Baris Suzek • Anita Walden (for CIC) • Denise Warzel

  12. http://wiki.hl7.org/index.php?title=MAX_-_Model_Automated_eXchangehttp://wiki.hl7.org/index.php?title=MAX_-_Model_Automated_eXchange

More Related