DICOM PS3.7 Message Exchange
E732161
DICOM PS3.7 Message Exchange is the part of the DICOM standard that defines how medical imaging systems structure, manage, and communicate messages to exchange clinical data reliably between application entities.
All labels observed (3)
| Label | Occurrences |
|---|---|
| DICOM C-GET | 1 |
| DICOM C-MOVE | 1 |
| DICOM PS3.7 Message Exchange canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418727 — 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 PS3.7 Message Exchange Context triple: [DICOM Application Entity, describedInPart, DICOM PS3.7 Message Exchange]
-
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.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
D.
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.
-
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DICOM PS3.7 Message Exchange Target entity description: DICOM PS3.7 Message Exchange is the part of the DICOM standard that defines how medical imaging systems structure, manage, and communicate messages to exchange clinical data reliably between application entities.
-
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.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
D.
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.
-
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 standard part
ⓘ
technical specification ⓘ |
| aimsTo |
ensure interoperable communication of clinical data
ⓘ
support reliable exchange of medical imaging information ⓘ |
| appliesTo |
DICOM service class notifications
NERFINISHED
ⓘ
DICOM service class operations ⓘ network communication between DICOM application entities ⓘ |
| concerns | exchange of clinical data between application entities ⓘ |
| coordinatesWith |
DICOM PS3.3 Information Object Definitions
NERFINISHED
ⓘ
DICOM PS3.4 Service Class Specifications NERFINISHED ⓘ |
| defines |
DICOM command set structure
ⓘ
DICOM data set encapsulation in messages ⓘ DICOM message service elements behavior ⓘ DICOM message structure ⓘ message exchange protocol between DICOM application entities ⓘ rules for association establishment between application entities ⓘ rules for association release between application entities ⓘ rules for error handling at the message level ⓘ rules for message identification ⓘ rules for message prioritization ⓘ rules for message sequencing ⓘ |
| domain | medical imaging informatics ⓘ |
| governedBy | DICOM Standards Committee NERFINISHED ⓘ |
| hasAbbreviation | DICOM PS3.7 NERFINISHED ⓘ |
| hasTitle | Digital Imaging and Communications in Medicine (DICOM) Part 7: Message Exchange NERFINISHED ⓘ |
| language | English ⓘ |
| partOf | DICOM standard NERFINISHED ⓘ |
| reliesOn | DICOM PS3.8 Network Communication Support for Message Exchange NERFINISHED ⓘ |
| specifies |
message flow for C-ECHO operations
ⓘ
message flow for C-FIND operations ⓘ message flow for C-GET operations ⓘ message flow for C-MOVE operations ⓘ message flow for C-STORE operations ⓘ message flow for N-ACTION operations ⓘ message flow for N-CREATE operations ⓘ message flow for N-DELETE operations ⓘ message flow for N-EVENT-REPORT operations ⓘ message flow for N-GET operations ⓘ message flow for N-SET operations ⓘ requirements for reliable message delivery between application entities ⓘ synchronous and asynchronous message exchange behavior ⓘ use of command sets and data sets within a single DICOM message ⓘ use of message IDs and message ID being responded to ⓘ use of priority in DICOM commands ⓘ use of status codes in command responses ⓘ |
| usedIn |
Picture Archiving and Communication Systems
NERFINISHED
ⓘ
medical imaging systems ⓘ modality workstations ⓘ radiology information systems ⓘ |
| uses | DICOM Upper Layer Service 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 PS3.7 Message Exchange Description of subject: DICOM PS3.7 Message Exchange is the part of the DICOM standard that defines how medical imaging systems structure, manage, and communicate messages to exchange clinical data reliably between application entities.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
DICOM C-MOVE
this entity surface form:
DICOM C-GET