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
IHE AIR is a profile which defines the specific types of objects an AI application should generate, to be conformant with imaging viewers. It defines, for example, a DICOM Segmentation object should be used for a segmentation - but it has additional values required for it to be compliant (including the notion of TID1500 and a 'root result'). It would be of great value to the community to have a sample MAP that produces an AIR-compliant result, which can be used to inspire / inform developers as well as application validators (like IHE Connectathon).
@IntegratorBrad For Comprehensive 3D SR as evidence, TID1500 (Measurement Report) is used as the root template, but with regard to DICOM Seg how is TID1500 related? Per Table 6.5.3-1, Seg IOD is separate and distinct from SR using TID1500. What's the complaint from IHE Connectathon validation for Seg object from the example app, apart from not having Tracking Identifiers which is for longitudinal results navigation?
IHE AIR is a profile which defines the specific types of objects an AI application should generate, to be conformant with imaging viewers. It defines, for example, a DICOM Segmentation object should be used for a segmentation - but it has additional values required for it to be compliant (including the notion of TID1500 and a 'root result'). It would be of great value to the community to have a sample MAP that produces an AIR-compliant result, which can be used to inspire / inform developers as well as application validators (like IHE Connectathon).
In addition, there should be a section on Standards, maybe in the introduction:
https://docs.monai.io/projects/monai-deploy-app-sdk/en/latest/introduction/index.html
... that provides some detail on how MONAI MAPs can be used to satisfy AIR Evidence Creator actor and transactions.
The text was updated successfully, but these errors were encountered: