fix/migration 3p11 (#5370)
This commit is contained in:
1 parent
df0593aac9
commit
6a1838bf0d
391 files changed
+2322
-215
No files matched your search
@@ -0,0 +1,21 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
sidebar_label: Introduction
|
||||
title: Data Source Introduction
|
||||
summary: Introduces OHIF's data structure based on naturalized DICOM JSON format, providing an overview of common data sources available in OHIF and how custom data sources can be implemented.
|
||||
---
|
||||
|
||||
# Data Source
|
||||
|
||||
The internal data structure of OHIF’s metadata follows naturalized DICOM JSON, a
|
||||
format pioneered by `dcmjs`. In short DICOM metadata headers with DICOM Keywords
|
||||
instead of tags and sequences as arrays, for easy development and clear code.
|
||||
|
||||
Here in this section we will discuss couple of data sources that are commonly used
|
||||
and OHIF has provided the implementation for them.
|
||||
|
||||
## Custom Data Source
|
||||
Do you have a custom data source? or a custom data that you want to use in OHIF?
|
||||
You can easily write a data source to map your data to OHIF’s native format.
|
||||
|
||||
You can read more in the [Data Source Module](../../platform/extensions/modules/data-source.md)
|
||||
Reference in new issue
Block a user