DICOM Message Service Element
E732154
The DICOM Message Service Element is a communication protocol component in the DICOM standard that defines how medical imaging data and related information are exchanged between DICOM application entities over a network.
All labels observed (3)
| Label | Occurrences |
|---|---|
| DICOM Message Service Element canonical | 2 |
| DICOM service primitives | 1 |
| DIMSE | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418705 — 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 Message Service Element Context triple: [DICOM Application Entity, communicatesUsing, DICOM Message Service Element]
-
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.
DICOM Standards Committee
The DICOM Standards Committee is the international body responsible for developing and maintaining the DICOM standard for medical imaging interoperability.
- 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 Message Service Element Target entity description: The DICOM Message Service Element is a communication protocol component in the DICOM standard that defines how medical imaging data and related information are exchanged between DICOM application entities over a network.
-
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.
DICOM Standards Committee
The DICOM Standards Committee is the international body responsible for developing and maintaining the DICOM standard for medical imaging interoperability.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM network service
ⓘ
DICOM upper layer service ⓘ communication protocol component ⓘ |
| abstracts | network transport details from DICOM services ⓘ |
| appliesTo |
DICOM networked SOP Classes
ⓘ
linked to:
DICOM Service-Object Pair Class
|
| conformsTo | OSI application layer concepts ⓘ |
| controls | message exchange within a DICOM association ⓘ |
| defines |
DICOM service parameters
ⓘ
DICOM service primitives ⓘ
linked to:
DICOM Message Service Element
rules for exchanging DICOM messages between application entities ⓘ semantics of DICOM message exchange ⓘ |
| enables |
interoperable exchange of medical images
ⓘ
interoperable exchange of related clinical information ⓘ |
| ensures | consistent behavior of DICOM network services ⓘ |
| governs |
request and response message flows
ⓘ
status reporting in DICOM services ⓘ |
| hasAbbreviation |
DIMSE
ⓘ
linked to:
DICOM Message Service Element
|
| hasComponent |
service-provider
ⓘ
service-user ⓘ |
| layeredAbove |
DICOM Upper Layer Service for TCP/IP
ⓘ
linked to:
DICOM Upper Layer Protocol
|
| operatesOver |
DICOM Upper Layer Protocol
ⓘ
TCP/IP network ⓘ |
| partOf |
DICOM network communication model
ⓘ
linked to:
DICOM PS3.7 Message Exchange
DICOM standard ⓘ |
| relatedTo | DICOM association ⓘ |
| specifiedIn | DICOM PS3.7 Message Exchange ⓘ |
| specifies |
message structure for DICOM commands
ⓘ
message structure for DICOM data sets ⓘ |
| supports |
C-ECHO service
ⓘ
C-FIND service ⓘ C-GET service ⓘ C-MOVE service ⓘ C-STORE service ⓘ DICOM query/retrieve operations ⓘ DICOM storage operations ⓘ DICOM verification operations ⓘ N-ACTION service ⓘ N-CREATE service ⓘ N-EVENT-REPORT service ⓘ N-GET service ⓘ N-SET service ⓘ |
| usedBy | DICOM application entity ⓘ |
| usedIn |
DICOM image archives
ⓘ
PACS systems ⓘ modality workstations ⓘ radiology information systems ⓘ |
| uses |
DIMSE-C services
ⓘ
DIMSE-N services ⓘ |
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 Message Service Element Description of subject: The DICOM Message Service Element is a communication protocol component in the DICOM standard that defines how medical imaging data and related information are exchanged between DICOM application entities over a network.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: DICOM Message Service Element
linked to: DICOM Message Service Element