FHIR Binary
E732175
FHIR Binary is a FHIR resource type used to represent and exchange raw binary content such as documents, images, or other files within healthcare interoperability workflows.
All labels observed (1)
| Label | Occurrences |
|---|---|
| FHIR Binary canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8418866 — 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: FHIR Binary Context triple: [IHE MHD, usesResourceType, FHIR Binary]
-
A.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
B.
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.
-
C.
FHIR R5 (preview)
FHIR R5 (preview) is the upcoming fifth major release of the HL7 Fast Healthcare Interoperability Resources standard, offering enhanced data models and interoperability features for exchanging healthcare information.
-
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.
Orthanc
Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
- 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: FHIR Binary Target entity description: FHIR Binary is a FHIR resource type used to represent and exchange raw binary content such as documents, images, or other files within healthcare interoperability workflows.
-
A.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
B.
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.
-
C.
FHIR R5 (preview)
FHIR R5 (preview) is the upcoming fifth major release of the HL7 Fast Healthcare Interoperability Resources standard, offering enhanced data models and interoperability features for exchanging healthcare information.
-
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.
Orthanc
Orthanc is an open-source, lightweight DICOM server and ecosystem designed for medical imaging storage, retrieval, and integration in healthcare and research environments.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
FHIR Binary resource
ⓘ
FHIR resource type ⓘ |
| canBeAccessedVia |
FHIR RESTful API
ⓘ
linked to:
FHIR
|
| canBeUsedWith | FHIR attachments and document workflows ⓘ |
| canRepresent |
CDA documents
ⓘ
DICOM images ⓘ PDF files ⓘ arbitrary binary data ⓘ documents ⓘ images ⓘ scanned documents ⓘ |
| contentTypeDatatype | code ⓘ |
| dataDatatype | base64Binary ⓘ |
| definedIn |
HL7 FHIR specification
ⓘ
linked to:
FHIR
|
| hasElement |
contentType
ⓘ
data ⓘ id ⓘ language ⓘ meta ⓘ securityContext ⓘ |
| hasFHIRResourceTypeCode | Binary ⓘ |
| hasSecurityConsideration | may contain PHI in raw form ⓘ |
| isNot | structured clinical content resource ⓘ |
| isSuitableFor | non-parseable content by FHIR servers ⓘ |
| isTypicallyNotSearchableBy | content ⓘ |
| isTypicallySearchableBy | metadata such as id or securityContext ⓘ |
| keyElement |
contentType
ⓘ
data ⓘ |
| oftenReferencedFrom |
DiagnosticReport
ⓘ
DocumentReference ⓘ Media ⓘ |
| oftenUsedFor | storing large files externally to main clinical resources ⓘ |
| partOf |
FHIR R4
ⓘ
FHIR R5 ⓘ
linked to:
FHIR R5 (preview)
|
| primaryPurpose | representation of raw binary content ⓘ |
| requires | appropriate access control ⓘ |
| securityContextDatatype | Reference ⓘ |
| securityContextTypicalTarget |
DocumentReference
ⓘ
Observation ⓘ Patient ⓘ |
| supports |
MIME type identification via contentType
ⓘ
base64-encoded payloads ⓘ |
| supportsInteraction |
create
ⓘ
delete ⓘ read ⓘ search ⓘ update ⓘ vread ⓘ |
| transportAgnostic | true ⓘ |
| usedFor | exchange of binary files in healthcare interoperability workflows ⓘ |
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: FHIR Binary Description of subject: FHIR Binary is a FHIR resource type used to represent and exchange raw binary content such as documents, images, or other files within healthcare interoperability workflows.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.