25 Questions to Ask Before

Investing in an AI Platform

1. Does the solution provide the ability to accept/reject/adjust/validate AI results?

2. Does the solution provide the ability to re-run one or more algorithms based on real time user
feedback?

3. Does the solution provide a single unified web-based UX/UI that can be embedded into PACS
display ports or an EMR providing full accept/reject/adjust functionality using standard URL/API
integrations (including iFrame launch)?

4. Does the solution provide a single unified web-based UX/UI that can support multiple
algorithms with multiple outputs and many findings to be displayed according to end-user
preferences?

5. Does the solution support use across multiple disparate PACS and VNA systems collectively
and independently?

6. Does the solution UX/UI allow the end-user to choose what images and information are
persisted in the PACS/VNA archive to avoid unfettered AI results from being made part of the
patient record?

7. Does the solution support algorithms that do not need the unified UX/UI and instead create
outputs directly compatible with other clinical systems and user experiences?

8. Does the solution offer a database to persist algorithm outputs as well as user interaction data
to support third-party system integrations?

9. Does the solution offer a database to provide access to images, outputs and user feedback for
the purposes of algorithm training data curation?

10. Does the solution support ensemble engines whereby the outputs of one algorithm can serve
as inputs to one or many other algorithms?

11. Does the platform allow algorithms to be deployed and run entirely locally behind a firewall in
the data center with no ports open nor any outside access?

12. Does the platform allow algorithms to be run in the cloud on de-identified data requiring no
PHI to be transmitted?
 13. Does the platform support a hybrid mode whereby algorithms can be run both locally and in
the cloud?

14. Does the platform algorithm inferencing cloud perform inferencing for algorithms, or does it
require data to be sent to each algorithm developer’s cloud(s)?

15. Does the platform simplify any complex DICOM algorithm output objects such as RTSTRUCT,
DICOMSEG, NIFTII or DICOMGSPS (including DICOMGSPS Group) into simpler DICOM file
formats when and if required?

16. Does the platform support any scanner vendor and any modality type?

17. Does the platform run algorithms and display results that include non-DICOM image formats?

18. Does the platform run algorithms that are non-imaging based and process metadata only?

19. Does the platform support the running of user-created algorithm content?

20. Does the platform provide an algorithm onboarding and containerization portal for use by
customers’ internal data scientists and researchers?

21. Does the platform automatically label clinical outputs from non-regulatory-cleared sources as
not being allowed for clinical use?

22. Does the platform perform vendor qualification and regulatory validation of algorithm content
it makes available, whether for clinical or research use or sale?

23. Does the platform sales contract provide the ability to trial and purchase algorithms without
any additional contracting and without requiring algorithm-specific licensing terms and
conditions?

24. Does the platform support advanced visualization workflows by generating AI-based
volumetric findings which can simplify the physician starting point for 3D, such as anatomic
segmentation or atlas functions?

25. Does the platform allow the end-user to control what data is sent to clinical reporting solution
and can it be incorporated into the report elastically such that any number of algorithms
and findings can be included - in one or two clicks without the need to delete any unwanted
information?

U S 650 . 372 . 1 100 | E U + 49 ( 0) 69. 9510. 352. 0 | info @t erareco n. co m | w w w. t e r a r e c o n . c o m

TeraRecon 2020 All rights reserved | Reproduction, adaptation or translation of this document is prohibited without prior written permission of TeraRecon. 112719EA-X-E1