Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/orthanc-dicom-origin.rst @ 222:997b6c308e28

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added FAQ entry about the origin instance Metadata
author Benjamin Golinvaux <bgo@osimis.io>
date Mon, 04 Mar 2019 14:49:31 +0100
parents
children
comparison
equal deleted inserted replaced
221:26441131d725 222:997b6c308e28
1 .. highlight:: bash
2 .. _orthanc-dicom-origin:
3
4 How to find out where a DICOM instance originates from?
5 ========================================================
6
7 Information about the origin of the instances is stored as Metadata, which can be accessed using the REST API::
8
9
10 $ curl http://localhost:8042/instances/19816330-cb02e1cf-df3a8fe8-bf510623-ccefe9f5/metadata
11 [
12 "IndexInSeries",
13 "ReceptionDate",
14 "RemoteAET",
15 "Origin",
16 "TransferSyntax",
17 "SopClassUid",
18 "RemoteIP",
19 "CalledAET"
20 ]
21
22
23 The relevant metadata about the origin of an instance is:
24
25 - ``Origin``: Whether the instance was received from the REST API, the DICOM protocol, some plugin or some Lua script.
26 - ``RemoteAET``: The remote AET (for DICOM).
27 - ``RemoteIP`` (in Orthanc ≥ 1.4.0): The IP address of the remote server (for REST API and DICOM).
28 - ``CalledAET`` (in Orthanc ≥ 1.4.0): The called AET (for DICOM).
29 - ``HttpUsername`` (in Orthanc ≥ 1.4.0): The username that created the instance (for REST API).
30
31 Please note that adding ``?expand`` to the REST endpoint will result in expanding the actual Metadata values::
32
33 $ curl http://localhost:8042/instances/cab76369-429ce4d8-6ed415e7-7a3c9482-50f3b1b4/metadata?expand
34 {
35 "CalledAET" : "ORTHANCTMP1",
36 "IndexInSeries" : "1",
37 "Origin" : "DicomProtocol",
38 "ReceptionDate" : "20190225T143257",
39 "RemoteAET" : "ORTHANC",
40 "RemoteIP" : "127.0.0.1",
41 "SopClassUid" : "1.2.840.10008.5.1.4.1.1.1",
42 "TransferSyntax" : "1.2.840.10008.1.2"
43 }
44