Our EvitaXL has started emitting a space character within an 'ASCII HEX' setting code; i'll attribute it no value instead of failing ... even though technically the space character is not a valid hex digit.
Return data elements to the free list.
was emitting alarms at technical alerts whereas in the current iteration emitting all medibus alarms to the PatientAlert topic and all text messages to the TechnicalAlert topic.

This isn't a perfect fit.  There is probably a need for non-alert status information topic.  But defining a nomenclature for such a potpourri could be a challenge.
Adds more priority detail to the alarm messages to aid in further normalizing the schema between devices (based on full set of data available from each)
priorities indexed starting at 1 per the spec
More informative message when OpenSplice is not found on the host system
There are 31 priority levels; not 30
domain tends to be specified before device type
Convert alarm priorities to the decimal range 1-31 from the awkward quasi-ascii range '1'-'O'
Some gradle environments don't seem to include junit by default.
Accommodate periodic corrupted data from our EvitaXL (running experimental firmware).  Actually this raises a more fundamental question of where in the OpenICE data model we should be placing protocol errors like this?  And pursuing that could eventually spill over into an overall theory of management of the OpenICE system.
promote to 0.4.1
ProductionSpecification attribute is never actually included in the NOM_NOTI_MDS_CREAT
Use PART_NUMBER in lieu of MODEL.  Through a lookup table match PART_NUMBER to more commonly used terms for models (MX800, MP70).  Also adds an image of the MX800.  We should add more models to the lookup table and ensure that this strategy works across software revisions.
The EvitaXL now emits a leading space on the date/time field.  Modified the regex to accommodate but also started keeping track of some common cases in a junit test case to avoid regressions.
Copied over some nascent documentation of OpenICE types and topics from the 'numerics.html' page I had previously made.

Eventually would like to auto generate some HTML documentation from this commentary.