210 likes | 510 Views
HL7 V3 Model Driven Software Development. René Spronk ( Ringholm bv , HL7 International RIMBAA Committee Chair) Charlie McCay (Ramsey Systems Ltd, HL7 International Technical Steering Committee Chair). Traditional Software Development. Gather requirements. Build.
E N D
HL7 V3 Model Driven Software Development René Spronk (Ringholmbv, HL7 International RIMBAA Committee Chair) Charlie McCay (Ramsey Systems Ltd, HL7 International Technical Steering Committee Chair)
Traditional Software Development Gather requirements Build Image credits: Johan den Haan, Mendix.nl
Model Driven Software Development • MDD, a.k.a. MDA, MDSE .. Model Generate Image credits: Johan den Haan, Mendix.nl
MDD for ImplementersRIMBAA Rene Spronk Rene.Spronk@ringholm.com
Use of V3 artefacts - RIMBAA RIMBAA
Information Models for MDD MIF Software application MIF MIF XSLT XML Schemas Software application
Code Generators • Code (class) generation • MIF - the code generator has to be aware of the structure of the MIF • Purpose-build code generator, e.g. Marc HI Everest toolkit for .net • UML/EMF (derived from the MIF) - the code generator has to know UML/EMF, including the v3 specific extensions • Standard cross-industry tools, with extension: OHT Eclipse tools (Java), MDHT tool for CDA (Java) • XML Schema • Standard cross-industry tools: e.g. JAXB
MDD - Application Generation Generic Software Components -Terminology -Data types MIF Software application Persistence e.g. UML/XMI RIM coreMIF
MDD for Application Developers • The RIM and RIM-based models have a value within an application, not just in a message or document • HL7 v3 offers “information object models” created by domain experts • Code generation tools, driven by HL7 v3 and other models, can be used to create software applications
MDD for Specification DevelopersDomain Specific Languagesfor Healthcare Charlie McCay charlie@ramseysystems.co.uk
Technology Outreach Report How does HL7 fit into mainstream tools? How do we simplify our specifications? Why do we have so much HL7 specific technical terms? Defining Languages is what HL7 does
Usable specifications • Must be easy for the specification users • Examples • Be short • Have testing tools • Be unambiguous • Use terms that are familiar • Work with current toolset • Covered by books from Waterstones / Amazon • Affordable
Specification Users User Interface Designer Report writers Interface Engineer User Community Profile Author Wire Format SemanticCoherence
Does it all need to be so complex? We are dealing with a difficult problem BUT • Tried to meet all specification users needs with one language • Major emphasis on Semantic Coherence • Too many acronyms and new terms INSTEAD • Plain English wherever possible • Give specification users what they want and need • Semantic Coherence will be reached in steps • Specification Compliance testing tools
Examples of DSLs • Configuration files • In-house import scripting languages • Middleware mapping languages • Healthcare data • CDA defines a language for clinical documents • RIM defines a language for Healthcare Information • Pharmacy DMIM defines a language • XML ITS defines one possible syntax for an HL7 language • HL7 Specifications • Visio, Schema, Table views are different forms of the language used by HL7 to define healthcare langauges
Conclusions & References • MDD is a new buzzword, HL7 v3 has effectively always been MDD in nature, and always defined Domain Specific Languages • RIMBAA/MDD • http://wiki.hl7.org/index.php?title=RIMBAA • DSL • http://wiki.hl7.org/index.php?title=ITS