DICOM Transfer Syntax
E732166
DICOM Transfer Syntax is a specification within the DICOM standard that defines how medical imaging data is encoded, compressed, and exchanged between systems to ensure interoperability.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DICOM Transfer Syntax canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418765 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: DICOM Transfer Syntax Context triple: [DICOM Unique Identifier, usedToIdentify, DICOM Transfer Syntax]
-
A.
DICOM standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
B.
DICOM Part 10: Media Storage and File Format
DICOM Part 10: Media Storage and File Format is the section of the DICOM standard that defines how medical images and related data are encapsulated, structured, and stored in files for exchange and archiving across different systems.
-
C.
DICOM Unique Identifier (UID)
DICOM Unique Identifier (UID) is a globally unique numeric string used in medical imaging to unambiguously identify objects such as studies, series, images, and other DICOM entities.
-
D.
DICOM Application Entity
A DICOM Application Entity is a networked software or device component in medical imaging systems that sends, receives, and processes DICOM messages and services for exchanging clinical data.
-
E.
DICOMweb STOW-RS
DICOMweb STOW-RS is a web-based DICOM service that enables clients to store medical imaging studies and related data over HTTP using RESTful APIs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: DICOM Transfer Syntax Target entity description: DICOM Transfer Syntax is a specification within the DICOM standard that defines how medical imaging data is encoded, compressed, and exchanged between systems to ensure interoperability.
-
A.
DICOM standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
B.
DICOM Part 10: Media Storage and File Format
DICOM Part 10: Media Storage and File Format is the section of the DICOM standard that defines how medical images and related data are encapsulated, structured, and stored in files for exchange and archiving across different systems.
-
C.
DICOM Unique Identifier (UID)
DICOM Unique Identifier (UID) is a globally unique numeric string used in medical imaging to unambiguously identify objects such as studies, series, images, and other DICOM entities.
-
D.
DICOM Application Entity
A DICOM Application Entity is a networked software or device component in medical imaging systems that sends, receives, and processes DICOM messages and services for exchanging clinical data.
-
E.
DICOMweb STOW-RS
DICOMweb STOW-RS is a web-based DICOM service that enables clients to store medical imaging studies and related data over HTTP using RESTful APIs.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM concept
ⓘ
data interchange specification ⓘ |
| appliesTo |
DICOM attributes
ⓘ
DICOM data set ⓘ DICOM pixel data ⓘ |
| constrains |
encoding of DICOM attributes
ⓘ
encoding of pixel data stream ⓘ |
| definedIn | DICOM PS3.5 NERFINISHED ⓘ |
| defines |
byte ordering
ⓘ
compression scheme ⓘ encapsulation of compressed pixel data ⓘ framing of pixel data ⓘ pixel data encoding ⓘ value representation encoding ⓘ |
| enables |
interoperable image printing
ⓘ
interoperable image storage ⓘ interoperable image viewing ⓘ |
| hasCategory |
compressed transfer syntax
ⓘ
encapsulated transfer syntax ⓘ uncompressed transfer syntax ⓘ |
| hasExample |
Explicit VR Big Endian
NERFINISHED
ⓘ
Explicit VR Little Endian NERFINISHED ⓘ Implicit VR Little Endian NERFINISHED ⓘ JPEG 2000 Image Compression NERFINISHED ⓘ JPEG Lossless, Nonhierarchical, First-Order Prediction NERFINISHED ⓘ MPEG-2 Main Profile / Main Level NERFINISHED ⓘ RLE Lossless NERFINISHED ⓘ |
| hasProperty |
big endian byte ordering
ⓘ
explicit VR ⓘ implicit VR ⓘ little endian byte ordering ⓘ |
| hasPurpose |
define encoding of DICOM data for interchange
ⓘ
ensure interoperability between DICOM systems ⓘ |
| identifiedBy | Transfer Syntax UID NERFINISHED ⓘ |
| negotiatedBetween |
DICOM SCP
NERFINISHED
ⓘ
DICOM SCU NERFINISHED ⓘ |
| negotiatedVia | DICOM A-ASSOCIATE request ⓘ |
| partOf | DICOM standard ⓘ |
| relatedTo |
DICOM Presentation Context
NERFINISHED
ⓘ
DICOM SOP Class NERFINISHED ⓘ |
| supports |
JPEG 2000 compression
ⓘ
JPEG-based compression ⓘ MPEG-based video compression ⓘ RLE compression ⓘ lossless compression ⓘ lossy compression ⓘ |
| usedFor |
DICOM file storage
ⓘ
media interchange ⓘ network transmission of DICOM objects ⓘ |
| usedIn | DICOM association negotiation ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: DICOM Transfer Syntax Description of subject: DICOM Transfer Syntax is a specification within the DICOM standard that defines how medical imaging data is encoded, compressed, and exchanged between systems to ensure interoperability.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.