HL7 Configurator View – User Experience

[Christopher Loyd]

This may be more of a product suggestion, but I’m asking for a logical interpretation as to why this is the way it is.

Within the HL7 Configurator when working with new/existing variants.  The tabs for viewing the defined parts of the message are as follows: Fields, Segments, Messages

With Messages being the higher tier of this hierarchical organization, while fields being the lower end – I find it particularly odd that the initial screen would be pointed at the Fields section.  It feels as though I’m having to read a book backwards, or work backwards as the first thing I’m going to need to do with the variant itself is pick what type of message I’m going to want to be working with changing, then picking the segment based around the message, and finally the field based around the segment of the message.

Instead of the tabs having an initial work ethic of Fields > Segments > Messages

It should exist as Messages > Segments > Fields

—-

This is a relatively small annoyance to myself but one that makes me question it every time I open it.  Be aware, I haven’t been working with Cloverleaf or Interfaces in general for very long (around 2 years), so there me a logical explanation on this.

Topic

[Michael Hertel]

Lets say you want to add a Zsegment to an A08 message.

First you have to define the field,

Secondly you define the segment and add the field to it,

Thirdly you change the ADT^A08 to add the Zsegment.

Field>Segment>Message

[Author]

Replies