DICOMweb STOW-RS
E697185
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DICOMweb STOW-RS canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T7933280 — 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: DICOMweb STOW-RS Context triple: [Cloud Healthcare API, hasFeature, DICOMweb STOW-RS]
-
A.
Orthanc
Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
-
B.
Orthanc
Orthanc is the black, indestructible tower of Isengard in J.R.R. Tolkien’s Middle-earth, serving as Saruman’s stronghold and seat of power.
-
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 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.
-
E.
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.
- 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: DICOMweb STOW-RS Target entity description: 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.
-
A.
Orthanc
Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
-
B.
Orthanc
Orthanc is the black, indestructible tower of Isengard in J.R.R. Tolkien’s Middle-earth, serving as Saruman’s stronghold and seat of power.
-
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 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.
-
E.
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.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM storage service
ⓘ
DICOMweb service ⓘ web-based DICOM service ⓘ |
| abbreviationOf | Store Over the Web using RESTful Services ⓘ |
| belongsToDomain |
healthcare interoperability
ⓘ
medical imaging ⓘ |
| definedIn | DICOM standard NERFINISHED ⓘ |
| enables |
cloud-based storage of DICOM studies
ⓘ
integration of imaging devices with web services ⓘ upload of imaging data from web clients ⓘ |
| fullName | Store Over the Web using RESTful Services ⓘ |
| goal | interoperable web-based storage of DICOM data ⓘ |
| hasOperationName | STOW-RS NERFINISHED ⓘ |
| isComplementedBy |
DICOMweb QIDO-RS
NERFINISHED
ⓘ
DICOMweb WADO-RS NERFINISHED ⓘ |
| isStandardizedBy | DICOM Standards Committee NERFINISHED ⓘ |
| isUsedBy |
PACS systems
NERFINISHED
ⓘ
VNA systems ⓘ clinical applications ⓘ medical imaging viewers ⓘ |
| partOf | DICOMweb NERFINISHED ⓘ |
| requires |
DICOM-compliant server
ⓘ
HTTP client ⓘ |
| supportsMediaType |
application/dicom
ⓘ
application/dicom+json ⓘ application/dicom+xml ⓘ multipart/related ⓘ |
| supportsOperation |
storage of DICOM instances
ⓘ
storage of medical imaging studies ⓘ storage of related clinical data ⓘ |
| supportsResourceLevel |
instance
ⓘ
series ⓘ study ⓘ |
| supportsSecurityMechanism |
HTTP authentication
ⓘ
TLS over HTTP ⓘ |
| supportsWorkflow |
image acquisition to archive
ⓘ
image sharing between systems ⓘ upload from mobile or web apps ⓘ |
| transports |
DICOM instances
ⓘ
DICOM metadata ⓘ DICOM objects ⓘ pixel data ⓘ |
| usesArchitectureStyle | REST NERFINISHED ⓘ |
| usesIdentifier |
DICOM SOP Instance UID
NERFINISHED
ⓘ
DICOM Series Instance UID NERFINISHED ⓘ DICOM Study Instance UID ⓘ |
| usesProtocol | HTTP 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: DICOMweb STOW-RS Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.