feat: Added documentation for OHIF-v3 (#2450)
* Added docs with new screenshots * Added doc to architecture * Added documentations to various extension modules * Added more documentation to modes * Added docs to managers * Added docs for services * Fixed deployment docs * Added white labelling documentation * Added i18n docs and measurement export
This commit is contained in:
1 parent
1bf651e763
commit
5643f8f6d2
142 files changed
+5251
-1523
No files matched your search
@@ -0,0 +1,38 @@
|
||||
# Mode: Validity
|
||||
|
||||
- [Mode: Validity](#mode-validity)
|
||||
- [Overview](#overview)
|
||||
- [isValidMode](#isvalidmode)
|
||||
|
||||
## Overview
|
||||
There are two mechanism for checking the validity of a mode for a study.
|
||||
|
||||
- `isValidMode`: which is called on a selected study in the workList.
|
||||
- `validTags`
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## isValidMode
|
||||
This hook can be used to define a function that return a `boolean` which decided the
|
||||
validity of the mode based on `StudyInstanceUID` and `modalities` that are in the study.
|
||||
|
||||
For instance, for pet-ct mode, both `PT` and 'CT' modalities should be available inside the study.
|
||||
|
||||
```js
|
||||
export default function mode() {
|
||||
return {
|
||||
id: '',
|
||||
displayName: '',
|
||||
isValidMode: ({ modalities, StudyInstanceUID }) => {
|
||||
const modalities_list = modalities.split('\\');
|
||||
const validMode = ['CT', 'PT'].every(modality => modalities_list.includes(modality));
|
||||
return validMode;
|
||||
},
|
||||
/*
|
||||
...
|
||||
*/
|
||||
}
|
||||
}
|
||||
```
|
||||
Reference in new issue
Block a user