Draft:List of Orthodontic Interoperable Software

This is a list of medical software or devices which are designed to be used with orthodontic data and collects or manipulates data that could be of interest to another software. This list focuses on the level of interoperability (the ability for the software to be able to connect with another software) that a specific software or device has.

The intent of this list is to:


 * 1) help doctors decide which platform would best suite their needs
 * 2) help software vendors publicize their level or interest in interoperability

Explanation of Columns

 * Developer: the company producing the software product
 * Product: the name of the software product
 * v: version
 * description: Definition of the product as defined by the developer/producer
 * APIs: if proprietary APIs are available to doctors, and what kind (rw, ro, imaging, appts, ...)
 * Ingest DICOM: File (from filesystem), PACS (from network), partial (ex: image ingestion using this route will allow some software functionality, not all clinical DICOM tags are recognized or used, bulk ingestion not allowed, only single image/patient, ...), complete (image ingestion using this route will allow full software functionality, all clinical DICOM tags are recognized or used, bulk ingestion (all images with all clinical data in one go).)
 * Export DICOM: File, PACS, partial, complete (see Ingest DICOM)
 * Ingest HL7/FHIR
 * Export HL7/FHIR
 * standard: medical standards implemented (DICOM, FHIR, HL7, SNOMED, ...)
 * implementation: level of implementation, amount of data that can be exchanged using public standards (complete: all; advanced: more than 50%, some: <50%, none: 0%, proprietary: a way to connect is available, but it is not based on public standards).
 * i14y friendly: if company is will to collaborate to move i14y forward (e.g. allow release of bridges on open-ortho)
 * updated: last time information was updated.
 * reference: contact person or link to reference which can backup the statements.

Questionnaire

 * 1) The answers to the following questions to each vendor are used to populate the table above.
 * 2) In order to make the information above verifiable, the source of each answer should contain a reference. If no reference is available, the reference column should state "Unverified".
 * 3) If an interview was conducted to obtain, then ideally the interviewee should be willing to disclose their name or department, if a reference to a publication or website is not available.

Q00 General
Questions 01 - 09 are general questions.

Q01 - What is the name of your software?

 * Company which developed it
 * Software product name
 * Software product version and release year

Q02 - What is the reference or source of this information?

 * URL, citation, department name, person or whatever other information needed in order to verify this information.
 * Alternatively: UNVERIFIED

Q10 DICOM
Questions Q11 - Q29 are dedicated DICOM questions.

Q11 - Is your software able to ingest or import images using the DICOM format?

 * Yes: The DICOM format is supported and recognized by the software
 * No: The DICOM format is not supported or recognized by the software
 * Partially: The DICOM format is only in part supported and recognized by the software (e.g.: reading only from filesystem, reading only from network, reading only limited metadata tags, ...)

Q12 - Is your software able to ingest or import images using the DICOM format from the file system (.dcm files, DICOMDIR, ...) ?

 * Yes: the software is able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.
 * No: the software is not able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.

Q13 - Is your software able to ingest or import images using the DICOM format from the network (DIMSE, WADO) ?

 * Yes: the software is able to read, ingest, import or otherwise work with images from the network in at least one of DICOM's supported formats (DIMSE, WADO, or other).
 * No: the software is not able to read, ingest, import or otherwise work with images from the network in at least one of DICOM's supported formats.

Q14 - Is your software able to ingest or import images using the DICOM format in bulk?

 * Yes: the software is able to ingest or import an entire database of images (many patients, with many studies, series and images of vamny modalities each)
 * No: the software is not able to ingest or import an entire database of images (many patients, with many studies, series and images of vamny modalities each)
 * Partially: as yes above, but only for a single modality (Photos (VL), X-Rays (DX,CT,PX), ...) at once.

Q15 - Is your software able to export, save or push images using the DICOM format?

 * Yes: The DICOM format is supported and recognized by the software
 * No: The DICOM format is not supported or recognized by the software
 * Partially: The DICOM format is only in part supported and recognized by the software (e.g.: reading only from filesystem, reading only from network, reading only limited metadata tags, ...)

Q16 - Is your software able to export images using the DICOM format from the file system (.dcm files, DICOMDIR, ...) ?

 * Yes: the software is able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.
 * No: the software is not able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.

Q17 - Is your software able to export images using the DICOM format from the network (DIMSE, WADO) ?

 * Yes: the software is able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.
 * No: the software is not able to read, ingest, import or otherwise work with images from the filesystem in at least one of DICOM's supported formats.

Q18 - Is your software able to export images using the DICOM format in bulk?

 * Yes: the software is able to ingest or import an entire database of images (many patients, with many studies, series and images of vamny modalities each)
 * No: the software is not able to ingest or import an entire database of images (many patients, with many studies, series and images of vamny modalities each)
 * Partially: as yes above, but only for a single modality (Photos (VL), X-Rays (DX,CT,PX), ...) at once.

Q19 - Does your software have a published DICOM conformance statement?

 * Yes: add URL of DICOM Conformance Statement
 * No

Q30 - HL7/FHIR (Q30-Q49)
Question numbers Q31-Q49 are dedicated HL7/FHIR Questions.

Add similar question as above, more relevant to HL7/FHIR