You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
DICOM messages sometimes include a modality in the field used for identity by TapirX. For example, the XA1020422 is a X-Ray Angiography device.
Describe the solution you'd like
TapirX could check if the identity field starts with one of the modality strings and add a field to the output. Field name could be category.
Describe alternatives you've considered
Post-process the output of tapirx with a script
Post-process the output of tapirx at a REST API endpoint
EDIT: now that I think more about it, these alternatives might be better.
Additional context
Here are some examples from the wild (exact numbers are modified).
WS1234311
XA1458615
US1776988
DX2130302
The text was updated successfully, but these errors were encountered:
I don't know if DICOM identifiers are always in the same format. I only have one example to work with.
Of course, the map lookup is easy. The design decision is: is it worth adding a field the Asset object to represent category? Then, plumbing that through to the CSV output, REST API output, etc.
Is your feature request related to a problem? Please describe.
DICOM messages sometimes include a modality in the field used for
identity
by TapirX. For example, theXA1020422
is a X-Ray Angiography device.Describe the solution you'd like
TapirX could check if the identity field starts with one of the modality strings and add a field to the output. Field name could be
category
.Describe alternatives you've considered
tapirx
with a scripttapirx
at a REST API endpointEDIT: now that I think more about it, these alternatives might be better.
Additional context
Here are some examples from the wild (exact numbers are modified).
WS1234311
XA1458615
US1776988
DX2130302
The text was updated successfully, but these errors were encountered: