Orthanc
E299654
Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
All labels observed (4)
| Label | Occurrences |
|---|---|
| Orthanc canonical | 2 |
| Orthanc DICOM server | 1 |
| Orthanc Explorer 2 | 1 |
| Orthanc REST API | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2805384 — 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.
Target entity: Orthanc Context triple: [Sébastien Jodogne, knownFor, Orthanc]
-
A.
OpenMRS
OpenMRS is an open-source medical record system platform widely used in resource-constrained settings to improve healthcare delivery and data management.
-
B.
Cloud Healthcare API
Cloud Healthcare API is a Google Cloud service that enables secure storage, management, and exchange of healthcare data using standard formats like HL7, FHIR, and DICOM.
-
C.
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.
-
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.
Flatiron Health
Flatiron Health is a healthcare technology company that specializes in using real-world oncology data and software to improve cancer care and research.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Orthanc Target entity description: Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
-
A.
OpenMRS
OpenMRS is an open-source medical record system platform widely used in resource-constrained settings to improve healthcare delivery and data management.
-
B.
Cloud Healthcare API
Cloud Healthcare API is a Google Cloud service that enables secure storage, management, and exchange of healthcare data using standard formats like HL7, FHIR, and DICOM.
-
C.
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.
-
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.
Flatiron Health
Flatiron Health is a healthcare technology company that specializes in using real-world oncology data and software to improve cancer care and research.
- F. None of above. chosen
Statements (66)
| Predicate | Object |
|---|---|
| instanceOf |
DICOM server
ⓘ
PACS system ⓘ medical imaging software ⓘ open-source software ⓘ |
| countryOfOrigin | Belgium ⓘ |
| deploymentModel |
cloud
ⓘ
on-premises ⓘ |
| designedFor |
easy integration
ⓘ
interoperability with existing PACS ⓘ lightweight deployment ⓘ |
| developedBy |
Orthanc community
ⓘ
Sébastien Jodogne ⓘ |
| hasComponent |
Orthanc
self-linksurface differs
ⓘ
surface form:
Orthanc REST API
Orthanc core server ⓘ Orthanc plugins ⓘ Orthanc web viewer ⓘ |
| hasRepository | https://github.com/orthanc-server/orthanc ⓘ |
| hasWebsite | https://www.orthanc-server.com/ ⓘ |
| operatingSystem |
Linux
ⓘ
Windows ⓘ macOS ⓘ |
| programmingLanguage | C++ ⓘ |
| softwareLicense | GPL-3.0-or-later ⓘ |
| supportsFeature |
DICOM anonymization
ⓘ
DICOM de-identification ⓘ DICOM modality worklist integration via plugins ⓘ DICOM query/retrieve ⓘ DICOM routing ⓘ DICOMweb ⓘ
surface form:
DICOMweb QIDO-RS
DICOMweb STOW-RS ⓘ DICOMweb ⓘ
surface form:
DICOMweb WADO-RS
RESTful API access ⓘ database backends via plugins ⓘ highly configurable routing rules ⓘ integration with hospital information systems ⓘ integration with research workflows ⓘ medical image retrieval ⓘ medical image storage ⓘ plugin architecture ⓘ scripting via Lua ⓘ web-based user interface ⓘ |
| supportsPlugin |
DICOMweb plugin
ⓘ
MySQL/MariaDB plugin ⓘ Orthanc self-linksurface differs ⓘ
surface form:
Orthanc Explorer 2
Orthanc authorization plugins ⓘ Orthanc indexer plugins ⓘ PostgreSQL plugin ⓘ Stone of Orthanc viewer ⓘ Web viewer plugin ⓘ |
| supportsProtocol |
DICOM C-FIND
ⓘ
DICOM PS3.7 Message Exchange ⓘ
surface form:
DICOM C-GET
DICOM PS3.7 Message Exchange ⓘ
surface form:
DICOM C-MOVE
DICOM C-STORE ⓘ HTTP ⓘ HTTPS ⓘ |
| supportsStandard |
DICOM standard
ⓘ
surface form:
DICOM
DICOMweb ⓘ |
| targetUser |
healthcare institutions
ⓘ
medical imaging developers ⓘ radiology departments ⓘ research laboratories ⓘ universities ⓘ |
| useCase |
PACS gateway
ⓘ
PACS replacement ⓘ integration testing platform for DICOM ⓘ research image archive ⓘ |
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.
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.
Subject: Orthanc Description of subject: Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.