Mercurial > hg > orthanc-stone
comparison README @ 4:00ff2cd06d13
dicomweb
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Mon, 17 Oct 2016 08:37:54 +0200 |
parents | 2dbe613f6c93 |
children | 4cf45e539cd9 |
comparison
equal
deleted
inserted
replaced
3:490347621f42 | 4:00ff2cd06d13 |
---|---|
23 VNA (vendor neutral archive, i.e. DICOM server). As a consequence, | 23 VNA (vendor neutral archive, i.e. DICOM server). As a consequence, |
24 Stone will smoothly interface with Orthanc out of the | 24 Stone will smoothly interface with Orthanc out of the |
25 box. Interestingly, Stone does not contain any DICOM toolkit: It | 25 box. Interestingly, Stone does not contain any DICOM toolkit: It |
26 entirely relies on the REST API of Orthanc to parse/decode DICOM | 26 entirely relies on the REST API of Orthanc to parse/decode DICOM |
27 images. However, thanks to the object-oriented architecture of Stone, | 27 images. However, thanks to the object-oriented architecture of Stone, |
28 it is possible to avoid this dependency upon Orthanc. | 28 it is possible to avoid this dependency upon Orthanc, e.g. to download |
29 DICOM datasets using DICOMweb. | |
29 | 30 |
30 | 31 |
31 Comparison | 32 Comparison |
32 ---------- | 33 ---------- |
33 | 34 |