search

usnistgov / hl7-igamt

10 stars 3 forks source link

[BUG] close co-constraints/dynamic mapping gaps #1608

Open carolinerosin opened 1 year ago

carolinerosin commented 1 year ago

Describe the bug

  1. When changing OBX-3 to value set, nothing is added to the OBX dynamic mapping (in the XML file)
  2. When adding another column to the IF part, it is something that is not supported by our XML format and not supported by validation
  3. In some cases, "second value" is added to mapping, but it is useless (because the datatype flavor is the same as the default one)

We need to close those gaps.

User Account all

URL all

To Reproduce Steps to reproduce the behavior:

  1. Play with co-constraints + look at XML

Expected behavior UI should only allow what is supported by xml/validation.

An idea would be to "pre-populate" OBX-5 datatype flavor with the value coming from dynamic mapping. User can only modify in specific cases, for example when the only IF column is the OBX-3 [code]

Screenshots This is not supported in XML/validation: image

image

This is supported, but useless in the XML (the default is good enough) image image

Additional context Add any other context about the problem here.