Enable the capability of automatically creating XUMs from any RBM (including profiles), but declare only one XUM as normative. This XUM will define the ‘global’ V3 wire format.
Encourage the use of ‘business names’ annotations to RBMs to provide a graphical view that links RBMs with terms used in requirements analysis models
Issues related to the inclusion or exclusion of fixed and default values in the instance are still under debate.
Further investigation is still required to complete the analysis of the best set of detailed proposals to ‘package’. One of the reasons for this is that benefits to implementers vary depending on the approach they take for message processing.
During this investigation, two main ways to process V3 instances were identified (by active V3 implementers), which may be categorized as “specific message processing” and “reference model processing”. From the various proposals described at this intermediate stage, various sets have been assembled that serve either one of these better, and these sets have been compared against the original project goals. From these, a single proposal seems to provide an opportunity for moving forwards in terms of testing activities.
In addition, a number of developments within this project have raised the opportunity for some technical convergence between CEN 13606 and HL7 V3. This is an important outcome for the NHS and will be pursued further.
Further testing will include the use of a RIM-based serialisation with allowance for a very specific model serialisation where appropriate. We would like to have preliminary discussions at the Boca Raton HL7 meetings to help prepare a suitable HL7 project proposal in order to foster wider collaboration with the HL7 community in this work.