DICOM Application Entity
E198793
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.
All labels observed (2)
| Label | Occurrences |
|---|---|
| DICOM Application Entity canonical | 2 |
| DICOM AE | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1776564 — 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 Application Entity Context triple: [DICOM standard, defines, DICOM Application Entity]
-
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.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
-
C.
DCOM
DCOM (Distributed Component Object Model) is a Microsoft technology that extends COM to support communication among software components over a network, enabling distributed, component-based applications.
-
D.
MCICOM
MCICOM is the United States Marine Corps command responsible for overseeing, managing, and supporting Marine Corps installations worldwide.
-
E.
IEEE 11073 medical device communication standards
IEEE 11073 medical device communication standards are a family of international standards that define interoperable data exchange and integration between medical devices and healthcare information systems.
- 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 Application Entity Target entity description: 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.
-
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.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
-
C.
DCOM
DCOM (Distributed Component Object Model) is a Microsoft technology that extends COM to support communication among software components over a network, enabling distributed, component-based applications.
-
D.
MCICOM
MCICOM is the United States Marine Corps command responsible for overseeing, managing, and supporting Marine Corps installations worldwide.
-
E.
IEEE 11073 medical device communication standards
IEEE 11073 medical device communication standards are a family of international standards that define interoperable data exchange and integration between medical devices and healthcare information systems.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM concept
ⓘ
medical imaging communication entity ⓘ networked software component ⓘ |
| accepts | DICOM association ⓘ |
| communicatesOver | TCP/IP network ⓘ |
| communicatesUsing |
DICOM Message Service Element
ⓘ
DICOM Upper Layer Protocol ⓘ |
| configuredBy | DICOM configuration management ⓘ |
| definedByOrganization | DICOM Standards Committee ⓘ |
| definedInStandard |
DICOM standard
ⓘ
surface form:
DICOM
|
| describedInPart |
DICOM PS3.15 Security and System Management Profiles
ⓘ
DICOM PS3.7 Message Exchange ⓘ DICOM Upper Layer Protocol ⓘ
surface form:
DICOM PS3.8 Network Communication Support for Message Exchange
|
| exchangesDataType |
DICOM images
ⓘ
DICOM structured reports ⓘ DICOM waveforms ⓘ patient demographic data ⓘ |
| hasAbbreviation |
AE
ⓘ
DICOM Application Entity self-linksurface differs ⓘ
surface form:
DICOM AE
|
| hasConfigurationElement |
called AE Title
ⓘ
calling AE Title ⓘ maximum PDU size ⓘ supported presentation contexts ⓘ |
| hasProperty | unique AE Title within a DICOM network configuration ⓘ |
| identifiedBy |
AE Title
ⓘ
IP address ⓘ TCP port number ⓘ |
| initiates | DICOM association ⓘ |
| mayImplement | DICOM security profiles ⓘ |
| mayUse |
TLS
ⓘ
surface form:
Transport Layer Security
|
| participatesIn | DICOM association negotiation ⓘ |
| primaryFunction |
process DICOM messages
ⓘ
provide DICOM services ⓘ receive DICOM messages ⓘ send DICOM messages ⓘ |
| supportsRole |
Service Class Provider
ⓘ
Service Class User ⓘ |
| supportsServiceClass |
Modality Worklist Service Class
ⓘ
Print Management Service Class ⓘ Query/Retrieve Service Class ⓘ Storage Service Class ⓘ Verification Service Class ⓘ |
| supportsStandard | DICOM network services ⓘ |
| usedByDeviceType |
DICOM workstation
ⓘ
PACS server ⓘ imaging modality ⓘ radiology information system ⓘ |
| usedInDomain |
cardiology
ⓘ
medical imaging ⓘ oncology ⓘ radiology ⓘ |
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 Application Entity Description of subject: 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.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
DICOM AE
subject surface form:
DICOM Unique Identifier