DICOM Upper Layer Protocol
E732155
DICOM Upper Layer Protocol is a network communication protocol that enables standardized exchange of medical imaging data between DICOM-compliant systems over TCP/IP.
All labels observed (2)
| Label | Occurrences |
|---|---|
| DICOM PS3.8 Network Communication Support for Message Exchange | 1 |
| DICOM Upper Layer Protocol canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418706 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DICOM Upper Layer Protocol Context triple: [DICOM Application Entity, communicatesUsing, DICOM Upper Layer Protocol]
-
A.
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.
-
B.
DICOM standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
C.
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.
-
D.
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.
-
E.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DICOM Upper Layer Protocol Target entity description: DICOM Upper Layer Protocol is a network communication protocol that enables standardized exchange of medical imaging data between DICOM-compliant systems over TCP/IP.
-
A.
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.
-
B.
DICOM standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
C.
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.
-
D.
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.
-
E.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM protocol component
ⓘ
network communication protocol ⓘ |
| abbreviation | UL ⓘ |
| conformsTo | OSI upper layer service concepts ⓘ |
| dataUnit | PDU ⓘ |
| defines |
A-ABORT primitive
NERFINISHED
ⓘ
A-ASSOCIATE accept primitive ⓘ A-ASSOCIATE reject primitive ⓘ A-ASSOCIATE request primitive ⓘ A-RELEASE request primitive ⓘ A-RELEASE response primitive ⓘ P-ABORT service for abnormal termination ⓘ P-DATA service for data transfer ⓘ association establishment between DICOM applications ⓘ association release between DICOM applications ⓘ |
| domain | medical imaging informatics ⓘ |
| ensures |
interoperability between heterogeneous imaging devices
ⓘ
reliable ordered delivery of DICOM messages ⓘ |
| notResponsibleFor | application-level DICOM command semantics ⓘ |
| operatesAtLayer | application layer ⓘ |
| partOf | DICOM standard NERFINISHED ⓘ |
| PDUType |
A-ABORT PDU
NERFINISHED
ⓘ
A-ASSOCIATE-AC PDU NERFINISHED ⓘ A-ASSOCIATE-RJ PDU NERFINISHED ⓘ A-ASSOCIATE-RQ PDU ⓘ A-RELEASE-RP PDU ⓘ A-RELEASE-RQ PDU ⓘ P-DATA-TF PDU NERFINISHED ⓘ |
| relationshipTo |
carries DICOM Message Service Element messages
ⓘ
sits above TCP in the protocol stack ⓘ |
| requires | establishment of a TCP connection before association ⓘ |
| runsOn | TCP/IP NERFINISHED ⓘ |
| scope | network communication between DICOM Application Entities ⓘ |
| specifiedIn | DICOM PS3.8 NERFINISHED ⓘ |
| standardizedBy |
American College of Radiology
NERFINISHED
ⓘ
National Electrical Manufacturers Association NERFINISHED ⓘ |
| supports |
multiple simultaneous presentation contexts
ⓘ
negotiation of abstract syntaxes ⓘ negotiation of presentation contexts ⓘ negotiation of transfer syntaxes ⓘ |
| transportProtocol | TCP NERFINISHED ⓘ |
| typicalPort | 104 ⓘ |
| usedBy |
DICOM Service Class Provider
NERFINISHED
ⓘ
DICOM Service Class User NERFINISHED ⓘ |
| usedFor |
communication between DICOM-compliant systems
ⓘ
exchange of medical imaging data ⓘ |
| usedIn |
modality-to-PACS communication
ⓘ
picture archiving and communication systems ⓘ radiology information systems ⓘ teleradiology systems ⓘ |
| uses | Presentation Data Units NERFINISHED ⓘ |
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.
Instruction
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.
Input
Subject: DICOM Upper Layer Protocol Description of subject: DICOM Upper Layer Protocol is a network communication protocol that enables standardized exchange of medical imaging data between DICOM-compliant systems over TCP/IP.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
DICOM PS3.8 Network Communication Support for Message Exchange