ABCD
1
Retired = Stale technology. Existing implementations are valid. The profile is no longer maintained by IHE. Profile documentation remains published but labeled.Could be applied to TI or FT profiles. Profile documentation remains published but labeled.
Deprecated = Obsolete technology. Do not implement this. The profile is removed from the TF publication; remains in the archive. Could be applied to TI or FT profiles.
2
See also ---->
Connectathon Summary of RAD profiles
3
DECISION: TI Supp or profileRAD Tech notesLink to Assessment page
4
FT candidate in 2025 (not done)AIR2025-01-20 CP-RAD-494, 500 (511, 512 are COmpleted ). Plan for checklist assessment at april F2F
2024-11: Result tree option not tested; desire by RAD Tech to promote this profile to FT in 2025; Andrei will take the lead on the FT checklist
2023-11: too new; Tested first time in Sept 2022 joint CAT and in EU2023
5
AIRAI
6
TIAIW-I2024-11: keep TI; not enough implementation but experience has confirmed that UPS-RS is a good technology for orchestration; this profile would benefit from promotion including things like Brad's video, some lessons learned from AI demo implementations, Kevin's proposed 'hello world' demo tool
2023-11: too new; minimally tested at Sept 2022 joint CAT & not since
7
TICAM2024-11: No testing of CAM in Japan in 2024; Steve reported that there is a CAM sample in the Share-a-zone
2023-11: too new; never tested at a NA or EU CAT; find out whether this was tested in Japan; it was promoted by. IHE-J in 2023
2022-11: IHE-J is trying to coordinate testing for CAM at a future CAT TO DO: Lynn to contact Salt; need to publicize this if it's planned. Bayer *may* be interested in CAM.
8
Deprecate candidate in 2025 (not done)CDS-OAT2023-11: The US regulatory requirement for this has been indefinitely deferred. See: https://www.cms.gov/medicare/quality/appropriate-use-criteria-program TO DO: Ask Brian Bialecki and TEri for a recommendation
2022-02 and 2022-11: The most recent update (HIT.gov driven) has not been tested. Per Kinson, there are implementations that use the profile as a reference, at least in part, but who may not have been tested at an IHE CAT. TO DO: Find an advocate to do Final Text assessment. Could Teri identify a person?? See https://www.bing.com/ck/a?!&&p=24347d39167ef7c7JmltdHM9MTY2Nzc3OTIwMCZpZ3VpZD0xODI5OTA3ZS1lZmRkLTZmODctMzJlOC04MTljZWU3NTZlMWUmaW5zaWQ9NTMxMQ&ptn=3&hsh=3&fclid=1829907e-efdd-6f87-32e8-819cee756e1e&psq=hl7+cds-oat&u=a1aHR0cHM6Ly9jb25mbHVlbmNlLmhsNy5vcmcvZG93bmxvYWQvYXR0YWNobWVudHMvNDA3MzIwMTYvQVVDJTIwQmlyZHMlMjBvZiUyMGElMjBGZWF0aGVyJTIwSmFudWFyeSUyMDIwMTklMjAtJTIwRklOQUwucHB0eD92ZXJzaW9uPTEmbW9kaWZpY2F0aW9uRGF0ZT0xNTQ5NTMyNjc3ODg4JmFwaT12Mg&ntb=1
9
FT candidate in 2025 (not done)DIFF2025-01: Wim is willing to do an assessment for Final Text for the April F2F
2022-02 - Per Wim: The technology is used, even though the profile not be claimed by the product. The viewing requirements are most valuable. Leave TI for now.		https://wiki.ihe.net/index.php/DIFF_FT_Evaluation
10
TIEBIW2024: defer promotion due to updates for POCUS
2023-11: Leave TI for now. ACEP POCUS team is now active so that might promote adoption and perhaps updates to the profile
2022-02: TO DO: Open CPs need to be resolved next.
11
Retire candidate in 2025 (not done)FUS2024-11: See 2022; consider multi-energy CT; repeatable fusion is no longer a driver. Wim will take the lead on the Retirement checklist.
2023-11: See 2022
2022-02: TO DO: Wim will review to make a recommendation. Antje advises to look at IHE-RO work to see if they did something similar
12
TIIDEP2024-11: Still never tested; an XCA-I environment is a potentially better Q/R solution but does not include the reconciliation specs in IDEP. TO DO:
ask Teri/Jonathan to inquire with the customer is still using this solution
2023-11: Never tested at a CAT
13
TIIMR2024-11: we hope to test it in Toronto
2023-11: too new; never tested
14
TI
IOCM Extensions
2022-02 - IOCM-related behavior has not been widely adopted in the XDS-I use cases. Keep TI for now.
15
TIIRA2024-11: Tested in Trieste; still too new for promotion; underlying FHIRcast is not yet final enough; John P reported expanding vendor interest; Andrei reported add'l participants in the RSNA demo using FHIRcast
2023-11: Too new
16
FT candidate IRWF. b2024-11: Need advocate to for FT assessment
2023-11: Need advocate to for FT assessment
17
TIMAP2024-11: Kevin reports AAPM committee interest in protocol sharing
2023-11: not yet tested at a CAT. 2022 DICOM XA protocols published and planar X-ray in progress.
18
TIMIMA2024-11: see 2023 notes
2023-12: TO DO: Andrei will assess whether IDEP in combination with SWF.b gives equivalent funtionality, or surpasses, what is in MIMA. 2022-02: Pending work to make this compatible for SWF.b. SWF.b Enterprise Identity Option duplicates some of the MIMA requirements; work needed to disentagle needed requirements and redocument
19
Deprecate candidate in 2025 (not done)PAWF2024-11: See 2023 notes; Kevin owns this
2023-12: The transactions in this profile point to sections in DICOM that are now retired/deprecated. Note that the transactions are the basis of updates with the newer UPS-based transaction. TO DO: Kevin will take a look and make a recommendation on next steps. The focus of the assessment with be whether deprecating this supplement leaves orphans that might be referenced in other profiles.
20
TIPOWR2024-11: too new
21
Deprecate candidate in 2025 (not done)RWF (FT)2024-11: Antje will do the deprecate/retirement assessment
2022-02: Candidate for deprecation due to outdated technology
22
Deprecate candidate in 2025 (not done)PWF (FT)2024-11: Antje will do the deprecate/retirement assessment
2022-02: Candidate for deprecation due to outdated technology
23
Retire candidate in 2025 (not done)
PDI Extensions
2024-11: Ask Antje to be a champion
2022-02: This is a candidate for the Archive/Retired - ie no longer maintained (i.e. TI), but it is not deprecated.
24
TIRAM2024-11: too new
25
TIRD2024-11: Leave TI
2023-12 - Leave TI for now.
26
TIRRR-WF2024-11: See 2023; we are watching on how UPS-RS is adopted.
2023-12: same assessment as in 2022-02; our current work in the reporting area is moving away from DICOM-based technology. Kevin noted that we should not retire this until we can point to a standards-based technology that could replace proprietary solutions
2022-02: The technology approach (UPS) is ok, but reporting workflow tends to be done with proprietary solutions in RAD today. Also, transactions are reused in AIW-I. Keep TI for now.
27
TISOLE2024-11: Updating this profile is a work-item level of effort. Someone needs to care enough about this to move it forward; SOLE was originally written to be a RAD dept timestamp; additional uses have been identified.
.2023-12: Was part of the AIIP demo in prior years but not in 2023. Need to reconsider the purpose of the profile and examine the use cases. Sean suggested to re-examine use cases in the context of AIW. Andrei questioned the premise real-time logging. Re-engage with the users on use cases. TO DO: Discuss in Feb to determine next steps.
2022-02: Leave TI. It is being massively rewritten via CPs. We may need to republish SOLE for Public Comment given the extent of the changes: TO DO: Lynn will talk to Andrei about how the CP process can be modified to trigger CP-->workitem conversion
28
XC-WADO
29
FT candidate in 2025 (not done)XDR-I2024-11: Can kinson do the assessment this year.
2022-02: Final Text candidate: TO DO: Need an advocate to do the assessment.
2022-11: Kinson will do FT assessment
30
DeprecateXRR-WD2022-02: Deprecate as technology not to be applied to the use case. No uptake. TO DO: Need to do the assessment on whether deprecation is the right approach.
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100