DICOM Service-Object Pair Class
E732167
The DICOM Service-Object Pair Class is a standardized definition in the DICOM medical imaging protocol that specifies how particular types of medical images or related data are structured and exchanged between systems.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DICOM Service-Object Pair Class canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418766 — 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 Service-Object Pair Class Context triple: [DICOM Unique Identifier, usedToIdentify, DICOM Service-Object Pair Class]
-
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 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.
-
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 standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
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 Service-Object Pair Class Target entity description: The DICOM Service-Object Pair Class is a standardized definition in the DICOM medical imaging protocol that specifies how particular types of medical images or related data are structured and exchanged between systems.
-
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 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.
-
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 standard
The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
-
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 (50)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM concept
ⓘ
information object definition ⓘ service class specification ⓘ |
| abbreviation | SOP Class NERFINISHED ⓘ |
| alsoKnownAs |
DICOM SOP Class
NERFINISHED
ⓘ
SOP Class NERFINISHED ⓘ |
| appliesTo |
DICOM file storage
ⓘ
networked DICOM communication ⓘ |
| constrains |
cardinality of DICOM attributes
ⓘ
set of DICOM attributes allowed for an object ⓘ usage of DICOM attributes ⓘ |
| definedIn | Digital Imaging and Communications in Medicine NERFINISHED ⓘ |
| defines |
behavior of DICOM services for a given object
ⓘ
semantics of DICOM objects ⓘ structure of DICOM objects ⓘ |
| enables | consistent interpretation of medical images across systems ⓘ |
| example |
CT Image Storage SOP Class
NERFINISHED
ⓘ
Grayscale Softcopy Presentation State Storage SOP Class NERFINISHED ⓘ MR Image Storage SOP Class NERFINISHED ⓘ Modality Worklist Information Model – FIND SOP Class NERFINISHED ⓘ Secondary Capture Image Storage SOP Class NERFINISHED ⓘ Ultrasound Image Storage SOP Class NERFINISHED ⓘ Verification SOP Class NERFINISHED ⓘ |
| hasComponent |
DICOM information object
ⓘ
DICOM service ⓘ |
| hasProperty |
binds a DICOM service to an information object definition
ⓘ
enables interoperability between imaging systems ⓘ standardized by NEMA and other DICOM stakeholders ⓘ uniquely identified by a SOP Class UID ⓘ |
| partOf | DICOM standard NERFINISHED ⓘ |
| relatedTo |
DICOM Information Object Definition
NERFINISHED
ⓘ
DICOM Service Class ⓘ |
| specifies |
encoding rules for a given information object
ⓘ
how particular types of medical images are exchanged ⓘ how related medical data are exchanged ⓘ set of DICOM services applicable to an information object ⓘ |
| usedFor |
image printing
ⓘ
image query and retrieval ⓘ image storage ⓘ modality performed procedure step communication ⓘ presentation state exchange ⓘ radiation therapy data exchange ⓘ structured reporting ⓘ waveform data exchange ⓘ worklist management ⓘ |
| usedIn |
DICOM network communication
ⓘ
PACS NERFINISHED ⓘ medical imaging ⓘ picture archiving and communication systems ⓘ radiology information systems ⓘ |
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 Service-Object Pair Class Description of subject: The DICOM Service-Object Pair Class is a standardized definition in the DICOM medical imaging protocol that specifies how particular types of medical images or related data are structured and exchanged between systems.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
DICOM Unique Identifier