HL7 Tooling Challenge
HL7 is holding a contest to encourage the development of HL7 tools. Will your team be the one to develop the solution and take home the prize?
The 2014 Tooling challenge is sponsored by Sparx Systems.
May 2, 2014 - Deadline to declare intent to participate
July 1, 2014 - Submission deadline
September 16, 2014 - During the HL7 Plenary and Working Group Meeting
Thanks to Sparx Systems for sponsoring this challenge
The challenge for 2014 is to:
Evaluate and define in detail the design of a method for using an off-the-shelf (OTS) UML tool for maintaining HL7 V3 artifacts. The design to be provided should allow a developer, following that design, to create a design tool that would meet HL7's needs.
The goal is to produce a design specification for a tool that can be used to create RIM-derived information models. The specification should include an HL7-profile in which each class of the HL7 Reference Information Model (RIM) becomes a stereotype that can be "drag-and-drop"(ped) into the new model. We anticipate that this will require defining an updated HL7-UML profile that will be part of the design. As with the prior Tooling Challenge, the technical foundation for HL7 information models is based on the HL7 Model Interchange Format (MIF).
To qualify for the prize, a submitter must include within the design specification, the following capabilities. The specified solution:
Must enable the resulting tool: to accept a model expressed in MIF; allow modifications thereto; and to express the result in MIF. Notes:
- If required, the design may propose changes or extensions to the HL7 Model Interchange Format (MIF) on which this effort is based.
- The Profile might be generated by transforming the HL7 RIM, expressed in MIF.
Must accommodate replacement of the HL7 RMIM designer in Visio (see documentation on HL7 Wiki.)
- Representation of HL7 profile extensions in UML are discussed and displayed in a Hot Topic on the HL7 Wiki at RMIM_Diagram_Representation
- Must include a functional decomposition of the capabilities as part of the design specification.
- Must describe development of an attribute selection and constraint dialog like that used in the HL7 RMIM Designer and in the SMD tool
- Must show how fixed property values from the RIM (like "isDocumentCharacteristic") would be encoded in the updated profile.
- Must include an updated UML profile that can be applied to Enterprise Architect such that EA can produce class models that represent the semantics described in the UML profile.