Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEA] Samples for AIR Evidence Creator + documentation #350

Open
IntegratorBrad opened this issue Sep 19, 2022 · 1 comment
Open

[FEA] Samples for AIR Evidence Creator + documentation #350

IntegratorBrad opened this issue Sep 19, 2022 · 1 comment
Labels
enhancement New feature or request
Projects

Comments

@IntegratorBrad
Copy link

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.

@IntegratorBrad IntegratorBrad added the enhancement New feature or request label Sep 19, 2022
@MMelQin MMelQin added this to To do in v1.0.0 via automation Sep 28, 2022
@MMelQin
Copy link
Collaborator

MMelQin commented Sep 29, 2022

@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?

@dbericat dbericat removed this from To do in v1.0.0 Oct 12, 2022
@dbericat dbericat added this to Needs Triage in Backlog via automation Oct 12, 2022
@MMelQin MMelQin moved this from Needs Triage to High priority in Backlog Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Backlog
High priority
Development

No branches or pull requests

2 participants